Engage can run a campaign on any page on any site, including a static HTML page, a landing page builder or a site that has nothing to do with WordPress.
Turning it on:
- Open the campaign in the builder and go to the Display tab.
- Switch on Allow this campaign to be embedded on other sites. It is off by default, so you decide exactly which campaigns are exposed.
- Publish the campaign. The snippet only works for a published campaign.
- Click Copy snippet.
The snippet is a single script tag. It carries three things: the URL of the embed loader on your WordPress site, your site address, and the campaign ID. Paste it into the page where you want the campaign to appear.
What the embedded campaign does:
It fetches the campaign from your WordPress site over a public REST route, loads the same stylesheet and the same renderer the plugin uses on your own site, and draws the campaign exactly as it looks at home. Tracking and opt-ins post back to your WordPress site, so views, clicks and conversions all count in your dashboard and every lead still lands on your Leads tab.
Frequency capping still applies, per visitor, on the page it is embedded on. If you put several embeds on the same page they are collected together and the runtime is loaded once.
What is protected:
Only campaigns you explicitly switched embedding on for are served. Anything else returns a refusal rather than leaking the campaign. Fetching a campaign does not record an impression: the view is only counted when the campaign actually appears, so pre-fetching can never inflate your numbers.
If you host the embed on a different domain, that is expected. The REST routes answer with the cross origin headers a browser needs, scoped to the plugin's own routes only.