Thrive Leads stores opt-in lead groups as the tve_lead_group custom post type. Each lead group has children custom post types per form variation: tve_lead_2step_lightbox, tve_lead_shortcode, tve_lead_widget, and others. Display rules, including trigger types like exit-intent or scroll-depth, are stored as postmeta on the group entry, with conversion stats kept in tve_leads_conversion_stats.

A landing page that is fronted by a Thrive Leads ribbon and screen-filler combination is largely about that opt-in. The headline that converts visitors lives in the Thrive Leads form, not in the WordPress page body. So default OG generators looking at post_content see only the surrounding page copy and miss the actual hook.

SleekPixel reads which Thrive Leads groups are configured to display on the current page, loads the group's child form variations and trigger postmeta, then renders a per-group OG image. The share names the lead group, badges the form types in play, and stamps the trigger so the link previews the opt-in mechanics rather than the surrounding theme.

Thrive Leads-fronted landing pages depend on the opt-in for nearly all their conversion value. The screen filler, the ribbon, the slide-in, and the exit-intent lightbox combine into the actual experience visitors react to, while the surrounding WordPress page is the host. A default OG image that says only the site name strips that experience out of the share.

A SleekPixel card that names the lead group, badges the form types in the group, and stamps the trigger mechanics restores it. None of this requires new fields to maintain. Thrive Leads already stores the group name, the form variations, and the trigger metadata.

SleekPixel reads what the plugin already writes and turns every group save and AB-test promotion into a regenerated card. For a marketing team that runs Thrive Leads across thirty landing pages, that is dozens of automatically refreshed social previews keeping the share story accurate to the opt-in actually live behind every URL.