A campaign is live but you don’t see it on the site. Almost always it’s one of four things: the tracker, the targeting, the trigger, or a collision. Work down this list.
First: is it actually published?
Check the campaign’s status. If it’s in staging, only visitors from a staging IP see it — Publish to live to release it. A draft shows to no one.
Then open the QA link
Press Preview on the campaign and pick “QA — see what a visitor gets, and why”. Your own site opens with a QA bar pinned to the bottom that names every action in the campaign and says what happened to each — shown, or the reason it was not. Nothing is forced, so what it reports is exactly what a visitor gets. From that bar you can also run a held-back action anyway, force the campaign on, and reload as a brand-new visitor. It usually answers the question in one click.
Where it names a delivery rule but not which one, the QA Simulator in the campaign’s Preview & QA tab goes deeper: it evaluates your targeting rule by rule and lets you be somebody else. Also check:
- Tracker firing? If not, nothing shows — see tracker not firing.
- Do you match? Use Test rules on my session in the Audience Forecast. If you don’t match, the targeting is narrower than you think — a common culprit is a URL rule, device rule, or “new visitor” condition.
- Is the trigger met? Exit-intent, scroll, delay, or click triggers won’t fire until the condition happens.
- Frequency capping — if it’s set to show once per session/visitor and you’ve already seen it, it won’t show again. Test in a fresh session.
- Placeholder present? Inline actions render into a placeholder — if the element/selector isn’t on the page, there’s nowhere to render.
- Collision — check Overlaps & conflicts; another campaign may own the same placeholder, or a higher-priority action may be winning.