QA Campaigns

Quality Assurance for Campaigns Before publishing personalization campaigns to your live audience, it's crucial to thoroughly test them. Personyze provides powerful QA tools to ensure your campaigns appear and function…

Testing and QA for Campaigns

Before a personalization campaign reaches your live audience, you should verify three things: the right people will match it, every action actually renders on the page, and it won’t collide with your other live campaigns. The Preview & QA tab of each campaign brings all of these checks into one place. The panels on this tab reflect recent preview / test sessions — not live audience data — so you can experiment freely without touching production metrics.

Campaign Summary

The top of the Preview & QA tab restates what the campaign will do, so you can sanity-check it before testing anything:

Your campaign is targeting — a plain-language readout of the audience conditions, including every include/exclude rule (for example, “New visitors” combined with URL-based exclusions). If a rule looks wrong here, fix it in the Audience settings before going further.
Presenting — how many actions the campaign will run when it matches.
Pending changes — if the campaign is already live and you’ve edited it since launch, this banner lists the staged edits (audience rule changed, actions added, schedule updated, and so on). Staged changes only take effect when you re-launch the campaign, so what visitors currently see may differ from what you’re previewing.

Campaign Preview Options

Get Shareable Preview Links

A preview link is a unique URL that forces the campaign’s content to display for whoever opens it — even if the audience rules are not met. This makes it ideal for internal review or for sharing with stakeholders who wouldn’t naturally match the targeting. Enter the URL of a page on your site (recently used URLs appear in the dropdown), click Get link, and share the generated link.

Because preview links bypass audience rules, they answer the question “does the content look right?” — not “will the right people see it?” Use the Simulator or the audience forecast for that.

Personyze Preview & QA tab showing the campaign summary, pending changes, shareable preview links, and simulator options — The Preview & QA tab: campaign summary with targeting readout and pending changes (top), and the two preview options — shareable preview links (left) and the Simulator (right). The dropdown suggests recently used page URLs.

Open the Site in Preview Mode Using the Simulator

The Simulator opens your site in a preview session where you can adjust visitor variables to simulate matches and trigger actions — for example, simulate visits from different countries, devices, or times of day to preview page variations. It also shows the visitor data Personyze has collected, so you can inspect exactly what information the targeting decisions are based on.

To launch it, enter a page URL under “Open site in preview mode using simulator” and click Open. For a full walkthrough of the Simulator panels, see Personyze QA Simulator.

The Personyze Simulator open on a live site, with the simulator panel, visitor variables, and matched campaigns highlighted — The Simulator running on your site: the side panel (right) lets you change visitor variables while the page updates to show which campaigns match and what content they render.

The Simulator panel is organized into tabs that answer different QA questions:

The Simulator Session tab showing the visitor data Personyze has collected, with annotations — Session tab: every variable Personyze knows about the simulated visitor — location, device, behavior, and custom data. Edit any value to simulate a different visitor.

The Simulator Targetings tab showing which audience rules matched and which did not, with annotations — Targetings tab: each audience rule evaluated against the current simulated session — matched rules in green, unmatched in red — so you can see exactly why a campaign does or doesn’t fire.

Overlaps & Conflicts

This section shows where the campaign intersects with your other live campaigns, before those intersections become production surprises. It is collapsed by default — open a row for details.

Audience overlaps — other audiences that also match the visitors your campaign targets, with the overlap percentage and which live campaigns use them. A high overlap means other campaigns may be competing for the same people.
Action overlaps — actions from other campaigns that fire for the same visitors, potentially competing on the same page (for example, two popups targeting the same segment).
Placeholder overlaps — other campaigns using the same action placeholders as yours. When two campaigns target the same placeholder, the higher-priority campaign wins the slot. Each placeholder row shows your priority versus the competing campaigns’, so you can tell in advance whether your action may lose its slot.

Preview Results

Both panels here reflect the last 90 minutes of preview / test traffic — not your live audience or all-time totals.

Audience Forecast

The forecast estimates what share of recent traffic would match the campaign if it were live right now. You’ll see the match percentage, counts of sessions that would and wouldn’t match, how many pages would match, and how many of the sessions came from your own IP. You can also test the rules against live visitors or against your own session only, to confirm the logic behaves as expected for a real person — you.

Action Delivery

This panel verifies that each action in the campaign actually executed during recent test sessions:

Shown — the action rendered successfully (its placeholder was found on the page).
Error — the action could not render, most often because the placeholder element wasn’t found. Click the error state to see the affected sessions and an example.
Clicked — a visitor clicked the action.

The Simulator Content tab listing each campaign action with its delivery status — Content tab: every action the campaign attempted on the current page with its delivery status — confirming each one actually rendered where it should.

If an action shows errors, check that the placeholder selector exists on the target page and that no other campaign with higher priority is claiming the slot (see Placeholder overlaps above).

Additional QA Techniques

Testing Mode

Testing mode lets you and your team see a campaign on the live site while it stays invisible to real visitors. Two things to understand:

You enter test mode automatically. Whenever you save a campaign, Personyze remembers the IP address you saved it from — it keeps the three most recent unique IPs used to save campaigns, and visitors from those IPs are automatically placed in test mode. So after saving, you’re already a tester; no extra step needed.
The left-menu indicator shows your state. When your session is in test mode, the indicator icon in the Personyze left menu turns yellow. Click it to open the test mode menu, where you can Enter testing or Exit testing, see your current testing IP, or register a different IP manually (enter it, or click Use my IP, then Save).

To keep a whole campaign in testing (not just your session), open the Save dropdown at the top of the campaign editor and choose Testing mode instead of Launch — the campaign then displays only to sessions from registered testing IPs, never to your live audience.

The campaign Save dropdown showing the Launch, Testing mode, and Draft options — Saving a campaign in Testing mode: the Save dropdown offers Launch (live for real visitors), Testing mode (visible only from testing IPs), and Draft (saved without launching).

For more detail, see Personyze Test Mode in Console.

Preview Individual Actions

You can preview each personalization action independently, without a full test session: click the Preview button next to any action you’ve created to view it directly.

Inspect Data with the Browser Console

To verify campaign data in real time, add this parameter to any URL on your site to enable console logging:

?_S_T=testing

Alternatively, run this command in your browser console:

_S_T.te(1)

The console output shows exactly what data Personyze has gathered about the visitor and which personalization actions it executed — useful when a campaign matches (or fails to match) and you want to see why.

Personyze test mode data logged in the browser console — Console output in test mode: the visitor data Personyze has gathered and the personalization actions it executed on the page.