Before a campaign reaches live visitors, check three things: the right people will match it, every action actually renders, and it won’t collide with your other campaigns. The QA step (Preview & QA) of each campaign brings all of that into one place. Everything here reflects preview / staging sessions — not live audience data — so you can experiment freely without touching production metrics.
Campaign summary & preview
The top restates what the campaign will do — a plain-language targeting readout (“All visitors”, or your include/exclude rules) and what it’s presenting (each action, its type, and where it renders). Sanity-check this before testing anything.
- QA Simulator — opens your site with the campaign applied and explains, element by element, why each action does or doesn’t show. The best tool when something isn’t appearing.
- Preview link — opens the page with the campaign live for you and copies a shareable link.
- Email link — send that same preview link to someone else.
- What to preview — the whole campaign, or a single action.
Audience forecast — who would match
See how many recent sessions would and would not match your targeting, how many pages match, and the share of site traffic. Use Test rules on my session to check the rules against your own visit, or Test rules on live visitors to spot-check real sessions — a fast way to catch targeting that’s too narrow (or too broad).
Overlaps & conflicts
Before launch, check what else is competing for the same visitors and slots:
- Audience overlaps — other audiences that also match your visitors.
- Action overlaps — other actions firing for the same visitors (watch for two popups at once).
- Placeholder overlaps — other campaigns rendering into the same placeholder. This is flagged as a real conflict because two campaigns can’t own the same slot.
Action delivery
The Action Delivery panel shows what actually happened in recent preview/staging sessions — the shown → viewed funnel and any failures. Click a state to see the sessions behind it, and for errors, a concrete example. If an action was executed but never shown, this is where you’ll see it.
Publish safely: staging, then live
Two publish buttons sit at the top of every campaign:
- Publish to staging — the campaign goes live only for visitors arriving from a staging IP. Real traffic is untouched. This is how you test end-to-end on the real site without risk.
- Publish to live — release to your real audience.
- Save as draft keeps changes without publishing, and the version selector lets you compare and roll back.
More ways to test
- Preview a single action — set What to preview to one action to isolate it.
- Browser console — advanced users can inspect what Personyze evaluated for the current session in the browser’s dev console.
- Live activity — after publishing, watch real-time visitor activity to confirm the campaign fires in the wild.
Still not working?
If a campaign passes QA but something’s still off on the live site, start with the focused troubleshooting guides: