OptinMonster persists campaigns in the omapp_campaigns option, with each campaign's id, type, and slug stored alongside its display rules. Page-level assignments live in omapp_output_settings, which records which campaigns are scheduled to display on which pages or post types, with trigger types like exit-intent, time-on-page, scroll-depth, and inactivity.

A landing page that fronts a lightbox campaign or a slide-in is usually all about the campaign. The headline copy, the visual, and the conversion math all live in the campaign rather than in the WordPress page content. So default OG generators looking at post_content see almost no signal: the campaign is in OptinMonster's option store, not in the page body.

SleekPixel reads omapp_output_settings for the active campaigns scheduled on the current page, looks up each campaign in omapp_campaigns for type and trigger, and renders a per-campaign OG image. The share now names the campaign, badges the type (Lightbox, Floating Bar, Slide-in, Inline, Gamified), and stamps the trigger so the link signals the live promotion behind the page.

OptinMonster landing pages are not really about the WordPress page. The headline copy, the visual, the offer, and the conversion mechanics all live in the OptinMonster campaign, while WordPress just hosts the URL. So when a visitor shares the URL, the default OG image strips out everything that actually matters about the page and replaces it with the site logo.

A SleekPixel card that names the campaign, badges the campaign type, and stamps the trigger restores all of that. The fields already exist in the OptinMonster option store. The plugin writes the campaign metadata on every save and updates it on every AB-test promotion.

SleekPixel reads what the plugin already writes and turns every campaign update into a regenerated card. For a marketing team running ten active campaigns over a quarter, that is hundreds of refreshed previews that always match the offer currently live behind the page.