Fix website embeds, landing pages and custom-domain display
Separate campaign state, page publication, script loading and DNS/HTTPS problems.
2 min read
Screenshots show the real application in an isolated demo environment with fictional example data. Setup notices and controls may differ by environment, plan and role. Click an image to view it full-size, and always use the values generated in your own workspace.
An embed is blank
- 1Verify the generated code references the correct published campaign.
- 2Load the public website outside the builder’s editor.
- 3Check whether the builder removed script tags or requires a separate code-injection area.
- 4Review HTTPS, Content Security Policy, consent settings and browser blockers with your website administrator.
- 5Test the campaign’s public page to distinguish a host-page problem from campaign availability.
The landing page shows old content
Save updates the draft; publish updates the public version. Open the editor’s draft preview to check the saved draft, then publish when ready and inspect the actual public page. A website/CDN cache can be a separate additional layer; do not confuse it with the saved/published distinction.
A click goes to the wrong page
Review saved live and closed URLs and the campaign’s actual current state. Inspect any redirect chain that might drop identity parameters. Check that a smart link is not configured as its own destination. An expired campaign can correctly use the closed destination even when an older cached image looks live.
A custom domain fails
Compare the exact TXT and CNAME records to the domain screen, confirm the configured stable hosting target and test public HTTPS. Ownership verification alone does not configure hosting or install SSL. If a signed-in account receives an access denial on a branded domain, also check membership in that workspace.