Targeting and Personalization

Personyze targeting campaigns show different content, layouts, or offers to specific visitor segments using 70+ real-time signals. Walk through the flow — build the audience with the live forecast and…

A targeting campaign in Personyze shows different content, layouts, offers, or entire experiences to specific segments of your visitors — anyone from “returning customers on the pricing page” to “cart abandoners who added a discounted item” to “high-intent visitors from a specific paid campaign.” The platform tracks 70+ real-time signals about every visitor and evaluates your audience rules on the fly, so a matching visitor sees the personalized experience the moment they qualify.

Every targeting campaign follows the same flow: Target (define the audience), Content (design what they see), A/B testing (optional — compare multiple variations), and then the Performance report once it’s live. Every step is inside the same campaign editor.

The campaign lifecycle: build the audience, design the content, optionally A/B test, QA it, then launch and measure.

Step 1 — Target: build the audience

The Visitor Targeting screen is where you define who the campaign applies to. Rules combine 70+ real-time visitor attributes into an expression that Personyze evaluates on every page view.

Adding rules: start empty, then pick the signals you need

A new campaign’s audience starts empty — it would match every visitor until you narrow it. You build the audience by clicking Add targeting rule and choosing from the rule categories in the picker. Each category you add becomes a rule group on the screen; a campaign only shows the groups you’ve actually added, in whatever combination you need.

The Add-targeting-rule picker, grouped into Visitor context, Behavior, and Integrations, with tabs to filter. — Click “Add targeting rule” to open the picker. Each category you choose adds a rule group to the audience. Click to enlarge.

The picker organizes rules under three tabs — Visitor context, Behavior, and Integrations — so you can jump straight to the kind of signal you want. Every rule answers a different question about the visitor:

Visitor context & attributes — who and where the visitor is, right now:

Pages Visited — match on the full URL, a path, or a query parameter; scope it to the current page or anywhere in the session.
Countries / Cities — geo-location down to city level from the visitor’s IP.
User / CRM / ABM data — known-visitor profile fields synced from your CRM or CDP (lifecycle stage, plan tier, lifetime value, industry, and custom fields).
Device & System — device type (mobile, tablet, desktop), operating system, and browser.
Visitor Type — new vs. returning, plus session count.
User Lists — match against a spreadsheet/CSV of users you upload.
Date & Time — a date range, day of week, or hour of day (useful for launches, sales windows, and business hours).
IP Addresses — specific IPs or CIDR ranges (handy for internal QA or named accounts).
Weather — the visitor’s local conditions by IP or GPS.

Behavior & engagement — what the visitor has actually done, this session or over time:

E-commerce — products they’ve viewed, added to cart, or purchased.
Product Interactions — counts across products (distinct, same, or total).
Last Product Interaction — their most recent shown / cart / purchase event, for “pick up where you left off” targeting.
Content Interaction — article views, favorites, and subscriptions.
Session Attributes — cookies, JavaScript variables, and form values captured on the page — your own client-side data.
Time on Site — total time in the current session.
Landing Page — the first page of the session.
Traffic Source — referrer, search engine, or campaign the visit came from.

Integrations — signals pulled live from connected tools. Known-visitor data flows in through our integrations with HubSpot, Salesforce, Pardot, Zoho, Tealium, Segment, and Zeotap; for anonymous B2B visitors, ABM providers can infer company name and firmographics so you can target by account before anyone fills out a form.

Each rule supports include/exclude per condition. Parentheses nest logic; rule groups combine with AND, OR, or XOR. A rule can be as simple as “is on the pricing page” or as sophisticated as “has viewed the pricing page in the last 14 days AND is on a paid plan AND has NOT opened a support ticket in the last 7 days.”

An example configured audience

Here’s what the screen looks like once several rule groups have been added and configured. This is one example — not a default or a required set — combining session, CRM, geo, device, pages-visited, and visitor-type rules:

Example Personyze Visitor Targeting screen with several configured rule groups numbered and described. — An example audience with several rule groups added and configured — your own campaign will contain whatever groups you choose. Click to enlarge.

Personyze page and session targeting rules with the current-page vs. during-session scope selector. — Page & session rules decide who qualifies based on what a visitor is doing. The scope selector on each rule — “On current page” vs. “Anywhere in this session” — is the key: the first checks only the page they’re on now, the second checks their whole visit. Click to enlarge.

AI Targeting Assistant

If you already know the audience you want in plain English, describe it to the AI assistant and it generates a matching rule set. You review, edit, and refine before saving — it’s a starting point, not a black box.

For example, typing “returning US visitors who viewed the pricing page but didn’t sign up in the last 30 days” produces a rule set like: Visitor Type is returning AND Countries is United States AND Pages Visited contains /pricing (in this session) AND NOT a sign-up event in the last 30 days — each as an editable rule group you can adjust.

The assistant has two modes, shown on the bar: Append adds the generated rules to whatever you already have, while Replace swaps in a fresh rule set. Use Append to layer on an extra condition, Replace to start over from a description.

The live audience forecast

As you edit rules, the forecast updates continuously, showing how much of a rolling sample of your recent traffic would match versus would not match. But the counters are only the summary — the real value is opening the forecast to see the actual visitors behind the numbers.

Expand it and you get two lists: the visitors who would match your current rules and the ones who would not. Click into any visitor to see their full detail — the pages they viewed, their session and device, their CRM/profile attributes, and exactly which of your rules they passed or failed. That’s how you confirm you’re targeting the right people, not just the right number of them: you can spot a visitor who slipped into the audience by accident, or a visitor you expected to match who didn’t, and trace it straight to the rule responsible.

Used this way, the forecast prevents the two most common audience mistakes before the campaign ever goes live:

Too narrow — a compound rule set that matches only a handful of visitors. The campaign runs but nobody sees it. An empty would-match list makes this obvious immediately, instead of weeks later.
Too broad — a rule you thought was specific that actually matches half your traffic. Reading the would-match list surfaces visitors who clearly don’t belong, so you can tighten the rules before launch.
Right count, wrong people — the number looks healthy but the audience is the wrong crowd. Only inspecting individual visitors catches this, and it’s the mistake the counters alone can never reveal.

The forecast also has a live-traffic mode — “Test rules on live visitors.” Instead of a rolling sample, Personyze evaluates your rule set against visitors arriving in real time and shows which ones would qualify, without saving anything. You can open a single live session and see it checked rule-by-rule, or scan the whole list of recent sessions flagged as matching or not — a final sanity check before you publish.

“Test rules on live visitors” checks your rules against real recent sessions. Opening one session shows it rule-by-rule — which conditions matched and which didn’t — so you can see exactly why a visitor would or wouldn’t qualify. Click to enlarge.

The session list view shows recent live sessions flagged as matching or not matching, so you can confirm your targeting is catching the right visitors before launch. Click to enlarge.

Group priority for overlapping audiences

When two campaigns can match the same visitor, an audience group decides which one wins. Add the overlapping audiences to a shared group and give each a priority (lower number = higher precedence). The group’s conflict-resolution rule then picks the winner for a shared visitor — higher priority first, with ties broken by “first occurred” or “last occurred” — so a visitor who qualifies for both sees only the intended content.

When audiences overlap, the Audience groups modal lets you group the conflicting campaigns and set priority and decision order, so a visitor sees only the intended one. — The Audience groups modal: (1) your groups and “+ New group”; (2) the conflict-resolution rule (priority order, then first/last occurred); and (3) the audiences attached to the group. Click to enlarge.

Audience persistence & frequency cap

Audience persistence controls how long a visitor stays in the audience after they match. Options range from “just this page view” (re-evaluate on every page) to “this session” to “for N hours” to “for N sessions” to “permanently once matched.” For most acquisition campaigns you want per-session persistence; for retention or loyalty campaigns you often want persistent membership so the experience follows the visitor across future sessions.

Audience persistence controls how long a matched visitor stays in the audience — re-checked on every page (default), once per session, after N pages or sessions, or permanently — alongside the frequency cap. Click to enlarge.

Frequency cap limits how often the campaign is allowed to show to a single visitor. Per-session caps prevent the same popup from firing twice in one visit. Per-visitor lifetime caps prevent a returning visitor from seeing the same message every time they come back. You can also remove the cap for content that should run every time (a persistent header banner, for example).

Full rule-by-rule reference: Targeting Rules in Personyze.

Step 2 — Content: design what your audience sees

Once the audience is defined, the Content step is where you decide what those visitors actually see. Content in Personyze is built from actions — and a single campaign can hold as many as you need. A header bar, a personalized recommendation widget, a countdown timer, and an exit-intent popup can all live in the same campaign, each firing for the same audience. Every action carries its own configuration, delivery health, and click-through tracking.

Adding an action is a two-part choice: what type of action it is (which decides the editor you work in), and how it behaves (placement, trigger, timing). The rest of this step walks through the action types, starting with the two you’ll reach for most.

The Content step before A/B testing: your campaign’s actions are listed, with an “Activate A/B testing” bar to split traffic across variations. — The A/B test lives right in the Content step: (1) choose A/B or Multivariate; (2) drag the traffic-split bar to allocate each group’s share; (3) the green “+” adds a new variation group; (4) each group header is one version; and (5) “Add action” drops actions into a group. Click to enlarge.

Move actions between groups. You don’t have to rebuild a variation from scratch — grab an action by its drag handle (the “≡” at the top-right of the card) and drop it into another group’s Add action zone. Hovering a card also shows quick controls to Edit, Detach, or Preview it. This makes it easy to start from the campaign’s base content and tweak just one element per variation.

Dragging an action card from one A/B group to another. — Reuse actions across variations by dragging them: (1) grab a card by its drag handle; (2) the hover toolbar lets you Edit, Detach, or Preview; and (3) drop it into another group’s “Add action” zone. Click to enlarge.

The Content screen (above) is the campaign’s control room. The main list holds every action, each with a status pill (Live / Draft / Test), its delivery health, and the last time it fired, plus quick controls to edit, duplicate, or remove it. The right-hand rail keeps the last 90 minutes of activity, the campaign’s primary conversion goal, and shortcuts to version history and the full performance report always in view. To add an action, you pick its type — which is where the two main editors come in.

The action type you pick determines the editor you work in. Two cover most campaigns — the Live Editor and the Popup, Banner & HTML Builder — with a set of specialized action types for everything else.

Live Editor (WYSIWYG)

The Live Editor is Personyze’s most-used content tool: it opens your actual live site inside the editor and lets you edit any element on the page — text, style, layout, images, links, buttons — with click-to-edit precision. Changes are captured as a variation that Personyze injects for your audience only; the underlying site code isn’t touched.

The same content can carry different versions by case. With Split Cases, a single action holds a Default version plus extra cases — each shown only when its condition is met (most often the visitor’s location, but also device, audience, language, or a CRM / feed value). You switch between cases and edit each one right in the WYSIWYG editor (the Popup & Banner editor works the same way).

The real Personyze Variations (audience-based) modal with an If-visitor-is condition and Then-content-is value. — Inside Split Cases: each case has an “If visitor is…” condition (attribute / operator / value, with “+ Add rule”) and a “Then content is…” value. “+ Add case” adds more variations. Click to enlarge.

What the Live Editor covers:

Navigate vs. Edit modes — Edit mode makes every element clickable so you can pick something to change; Navigate mode disables editing so you can click links and interact with the page as a real visitor. Press Esc to return to Edit.
Basics panel — edit text (with a rich-text editor for bold/italic/lists/links), change styling (color, font, size, background), duplicate or delete an element, or drop into raw HTML source when needed.
Layout panel — move & resize by dragging corners, adjust spacing (margin/padding), change alignment for flex & grid layouts, hide/show per device breakpoint, preview responsive breakpoints, or reposition with z-index and pinning.
Insert panel — drop in new elements: images (upload or URL), links, buttons, reusable blocks, videos (YouTube / Vimeo / MP4), or raw custom HTML snippets.
Behavior panel — attach behavior to any element: run custom JavaScript on click, scroll to an anchor, delay or hover-triggered actions, count clicks toward the action’s stats, register the element as a conversion goal, or fire a custom event with a name and payload.
AI-assisted editing — for any selected element, ask the AI for style suggestions (“Match brand accent,” “Modern sans look,” “More contrast,” “Softer, rounded”) or text rewrites (“Make it punchier,” “Shorter,” “Benefit-focused,” “More urgent,” “Match brand voice”). The AI proposes changes you review, apply, or discard.
Page-level AI — for wholesale rewrites, describe the goal (“Rewrite this whole page for enterprise buyers”) and the AI proposes an integrated set of changes across the page.
Variation history — every element tracks how many variations have been created and lets you switch between them for comparison.

Popup, Banner & HTML Builder

When you want to put a new element on the page — a popup, a sticky header/footer bar, a floating bubble, a slide-in notification, a message box, an embedded in-page banner, or a fully custom HTML block — use the Popup, Banner & HTML Builder. It ships with production-ready templates for each format and supports live personalization tokens (e.g., “Hi Alex — your search for ‘noise-cancelling headphones’ deserves 20% off”) that resolve at render time from the visitor’s profile, session, or CRM data.

Despite the name, this builder isn’t limited to overlays that float on top of the page. Every content item can be pinned to a placeholder — a CSS selector you point at any element on your site. Set a placeholder and the content is injected at that spot, and it can replace the existing content there rather than only adding alongside it. That makes the same builder useful both for classic overlays (a popup, a corner toast) and for swapping in-page content (a hero banner, a promo strip, a block inside a product page) without touching your site’s code.

Edit any action with AI

Any action — a popup, banner, WYSIWYG edit, or block of HTML — can be edited with AI instead of by hand. Click Edit action with AI, describe the change in plain English, and Personyze rewrites the action’s HTML for you to review and apply.

The Edit-this-action-with-AI panel with a prompt box and Apply AI changes. — Open **Edit action with AI** and describe the change — the AI sees the current HTML and rewrites it. Examples: *“Make the background purple,” “Shorten the timer to 1 hour,” “Change CTA to Save now.”* Click to enlarge.

The AI can:

Restyle — colors, fonts, spacing, layout, button styles (“match our brand accent,” “more contrast,” “modern sans look”).
Rewrite copy — headlines, body, CTAs (“make it punchier,” “benefit-focused,” “more urgent,” “match brand voice”).
Change the creative — swap or adjust images, timers, coupon codes, and other template elements.
Insert personalization — add Personyze variables like the visitor’s first name, city, or a searched keyword so the action fills in per visitor.

The AI proposes the change; you review, apply, or discard — nothing goes live until you accept it.

The builder walks through three stages:

1 · Template. Start from a format-specific template, filterable by type: Bar (slim sticky top/bottom bar, or a rich bar with image & CTA), Embedded Banner (inline in a specific page slot), Message Box (inline messaging with CTAs), Popup (modal overlay — signup / lead form, or countdown promo), Notification (slide-in corner toast), Floating (floating bubble / launcher), and Custom HTML / Blank (raw markup). Any template can embed a product-recommendation widget powered by your catalog (Bought Together, Countdown, Grid, Slider, and more), and there’s an “Edit this action with AI” option to generate or restyle it from a prompt.

2 · Customize look & feel. Adjust the design — layout, colors, fonts, imagery, buttons, and responsive behavior across base / hover states and phone / tablet / desktop breakpoints — and drop in personalization tokens that resolve per visitor.

3 · Placement, trigger & frequency. This stage decides where, when, and how often the content shows:

Placement — for overlays, choose a screen position (top/bottom, left/center/right, or centered). For in-page content, set a placeholder selector to inject into — or replace — an element on the page. Personyze also lists every other content item already using that same placeholder, so you can see what competes for the slot.
Trigger — what makes it appear: as soon as the page loads, after a delay, after the visitor is idle for a while, after scrolling to a point, when they scroll back to the top, when text is copied, on predicted leave intent (exit intent), on a custom JS event, or from a click-to-open launcher.
Frequency & close behavior — frequency caps keep it from feeling like spam: show a close (×) button and, if closed, suppress it for N sessions; hide it after the visitor has closed it a set number of times; or hide it after they’ve clicked it a set number of times.

Full guide: Popup & Banner Action Guide.

Other action types

Personyze also supports these action types, each with its own dedicated guide:

Product Recommendations — dedicated recommendation widgets (Bought Together, Also Viewed, Trending, Personalized by browsing history, Category-based, and more) powered by your product catalog feed.
Countdown Timer — add urgency with a live countdown to a specific date/time, a per-visitor session countdown, or a rolling window.
Redirect to URL — send matching visitors to a different URL entirely. Useful for A/B testing landing pages or routing paid traffic to a segment-specific page.
JavaScript Action — run arbitrary JavaScript when the audience matches. Used for anything the built-in action types don’t cover — talking to a third-party API, mutating page state, firing tracking events, or wiring up something custom.
Email actions — personalized email sends including cart abandonment, re-targeting, and campaign-driven sends, with recommendations embedded at open-time.
Web Push Notifications — reach visitors who’ve granted push permissions with time-of-day or event-triggered notifications.

Step 3 — A/B testing (optional)

A campaign with a single variation just serves that content to the whole audience. But any campaign can be turned into an A/B test by adding two or more variations, splitting traffic across them, and letting the results decide the winner. It’s the fastest way to prove whether a change actually moves your goal instead of guessing.

Setting up the test

Turn on Test Versions in the campaign’s Content step and the single content area becomes a set of variations to compare. Each variation is a version of the content — Group A, Group B, and so on — with the original site (“Site original”) kept as an untouched baseline you can hold traffic back to.

With A/B testing on, traffic is split across groups (A/B/C plus the original). Each group holds its own actions, and you set the split and how users are assigned. — The A/B test controls: (1) test type — A/B or Multivariate; (2) the traffic-split bar, dragged to allocate each variation’s share; (3) how visitors are assigned; and (4) the Goal & auto-pick bar. Click to enlarge.

Allocate traffic with the split bar. The colored bar at the top of the test is interactive: drag the handles between segments to change how much of the audience each variation receives (for example A 45% / B 40% / original 15%). The percentages always add up to 100%, and holding some traffic on the original is what lets you measure lift against doing nothing. Use “+” to add another variation and the × on a group to remove one; new variations start empty for you to fill.

Choose how visitors are assigned. “Assign by” decides how a visitor is bucketed — Rotate users spreads them across variations, while keeping a visitor in the same variation across sessions makes the experience consistent for returning visitors.

The Assign-by dropdown with all rotation modes. — The “Assign by” dropdown decides how visitors are bucketed into variations, plus a shared control cohort across campaigns. Click to enlarge.

Rotate users — different users see different versions, and each user stays on the same one. The classic A/B test.
Visits — the same person can see different variants on each visit. Good for banners and creative.
Random — every page view picks a variation at random, with no user or visit consistency.
Control users / Control visits — hold out a shared control cohort across campaigns (e.g. a 10% group that never sees personalization), to measure the total lift of your whole program.

Set the goal and decision rule. Pick the KPI the test optimizes for (clicks, a conversion goal, or revenue) and decide whether Personyze should auto-pick the winner once it’s conclusive, or leave it manual so you make the call. The decision strategy panel controls how sure Personyze must be before declaring a winner.

The Goal & auto-pick “Decision strategy” panel: pick the goal, choose how sure Personyze must be (confidence / sessions / duration), watch readiness to decide, and set what happens when a winner is found. — The Decision strategy panel: (1) primary goal; (2) auto-pick winner on/off; (3) a decision preset (Cautious / Balanced / Fast / Custom) that sets the confidence, sessions, and duration thresholds; (4) readiness-to-decide progress; and (5) who gets notified when a winner is picked. Click to enlarge.

Resetting test data. If you make a meaningful change mid-flight — new variations, a different split, or an edited action — the results collected so far no longer describe what’s running now. Reset the test data so measurement restarts cleanly from the change, rather than mixing old and new numbers.

Multivariate: test several elements at once

An A/B test compares whole variations against each other. Multivariate tests individual elements in combination. Instead of one list of variations, you create groups — each group is one thing you’re varying (say, card order, or the annual-plan copy) — and add the alternative actions inside each group by dragging them in. A visitor sees one action from each group, and Personyze automatically combines the groups into every possible variant.

A multivariate test with two groups — “Card order (desktop)” and “Annual plan copy” — each holding several action variations. — A multivariate test: (1) the Multivariate toggle; (2) campaign content shown to everyone; (3) the rule that a visitor sees one action from each group; and groups (4) and (5), each varying one element — Personyze combines them into every variant. Click to enlarge.

Because it measures each element’s individual impact and how elements interact, multivariate is the right choice when you want to know which specific change drove the result — at the cost of needing more traffic, since every combination has to accumulate enough data.

Reading the results

The results dashboard is built to answer one question first — which variation won, and can I trust it?

The A/B test results overview. — The results dashboard is built to answer one question first — which variation won, and can I trust it? Click to enlarge.

The A/B results dashboard with control, variations, winner, and daily trend. — The results dashboard for the primary goal: a **Control group (holdout)** as the true baseline, each variation’s conversion rate with confidence and 95% CI, a **WINNER** badge on the leading variation, and a daily conversion-rate trend. Tabs at top switch between goals (trial signups, CTA clicks, demo requests). Click to enlarge.

Performance-by-segment breakdown of an A/B test. — **Performance by segment** shows where each variation wins — split by device, country, city, URL, or browser. The winning cell per row is highlighted, and each segment gets its own leader and confidence, since a variation can win overall but lose on mobile. Click to enlarge.

Winner recommendation — when a variation reaches statistical significance on the goal, Personyze surfaces it at the top and offers to promote it in one click (in the example above, promoting Variation B on the strength of its social-proof treatment).
Delivery-health alerts — the dashboard flags problems that would invalidate a result, such as a variation that under-delivered because a selector was missing on some pages. A “winner” built on broken delivery isn’t a real winner, and this stops you from acting on one.
Summary KPIs — Visitors, Impressions, Delivered, Clicks, and Conversion rate for the whole test, with each variation compared side by side.
Per-goal breakdown — if the campaign tracks several goals (say Trial signups, CTA clicks, and Demo requests), each is reported per variation, because a variation can win on one goal while losing on another.
Daily performance & trend — how each variation performs day by day and how the conversion-rate gap is trending, so you can tell a stable lead from one that’s still swinging and avoid calling the test too early.
Engagement detail — deeper interaction metrics beyond the headline conversion, for understanding why a variation is winning.

Full guide: A/B Testing.

Save modes: Test vs. Live

How you save a campaign decides who can see it. There are two modes, and the difference matters:

Personyze save modes: Save as draft, Publish for test, Publish to live. — The save bar offers three modes — Draft, Test (only you), and Live (real visitors). Click to enlarge.

Test mode — the campaign runs only for you (and anyone previewing it), never for real visitors. This is where every campaign should live while you build and check it. You can save to Test as many times as you like without touching production traffic.
Live mode — the campaign is active for real visitors who match the audience. Switching to Live is the deliberate act of publishing; switching back to Draft / Disable takes it offline again without deleting it.

The normal flow is: build → Save to Test → QA it → Switch to Live when it’s right. Because Test and Live are separate states, you can keep refining a live campaign in Test and only push changes to production when you’re happy.

QA before launch

The QA step opens with a campaign summary and an audience forecast, so you can sanity-check the whole setup at a glance before previewing it on a real page.

The QA step: campaign summary, preview options, and audience forecast. — The QA step at a glance: on the left, a plain-English **campaign summary** (exactly who you’re targeting and what’s presented) and **preview options** — get a shareable preview link, or open your site in the Simulator. On the right, the **audience forecast**: the share of recent traffic that would match, pages and sessions that qualify, and shortcuts to test the rules on live visitors or on your own session. Click to enlarge.

Campaign summary — reads back your targeting in plain English (include/exclude rules and the AND/NOT logic) and how many actions will present, so a mistake in the rules is obvious before launch.
Get shareable preview links — a link that shows the chosen content even to people who don’t match the audience rules, for sign-off from teammates or clients.
Open site in preview mode using the Simulator — launches your real site with the campaign injected, where you can adjust user variables to simulate matches and trigger actions (covered below).
Audience forecast — the match rate against a rolling sample of recent traffic, with counts for “would match” vs. “would not,” pages and sessions that qualify, and one-click Test rules on live visitors or on my session.

Before a campaign reaches real visitors, QA it with the QA Simulator. When you start QA, Personyze opens a small dialog asking for the page URL you want to preview on — you paste in the address of the page where the campaign should appear (your pricing page, a product page, the homepage), and Personyze opens that real page with the campaign injected, exactly as a matching visitor would see it.

The QA Simulator with campaign panels beside a live preview of the target page. — The QA Simulator: (1) pick the campaign and environment (Test or Prod); (2) enter the page URL to preview on; (3) a matched / not-matched badge for the current simulated visitor; (4) **My session data** — impersonate a visitor by user ID, session, and CRM/custom attributes; (5) **Targetings** — the rule-by-rule match result; (6) **Campaign content** — the actions and whether each executed; and (7) the live preview of the real page with the campaign injected. Click to enlarge.

From there you can:

Preview on any page — test the campaign on the specific URLs it targets, not just an abstract preview, so you catch selector and placement issues on the actual page structure.
Impersonate a visitor profile — simulate any combination of audience attributes (returning vs. new, a CRM segment, a geo, a device) and confirm the campaign shows — or correctly stays hidden — for each one.
Check the rendered result — placement, timing/trigger, personalization tokens resolving from the profile, and how it interacts with any other campaign competing for the same visitor — all without affecting live traffic.

QA Simulator session-data panel for impersonating a visitor. — Impersonate a visitor in the QA Simulator: (1) switch identity with a new user ID; (2) control the session (start, number, mode); and (3) override CRM / custom attributes — account type, industry, lifecycle stage, plan, LTV, and more — to test attribute-based audiences. Click to enlarge.

QA Simulator targetings panel showing rule-by-rule match results. — The targetings check evaluates the campaign’s rules against the simulated visitor: (1) the overall result; (2) a rule group that matches; and (3) one that doesn’t — so the audience doesn’t qualify. Click to enlarge.

QA in Test mode first, fix anything the simulator surfaces, then switch the campaign to Live.

Manage a campaign: duplicate, versions & delete

Once saved, a campaign lives in your campaign list, where every campaign shows its status and live metrics (impressions, CTR, conversion rate, revenue). Expand any row for a quick overview, or use the row’s actions to edit, pause, duplicate, or open its performance report.

The Personyze campaign list showing saved campaigns with their status and live metrics, an expanded overview, and per-row actions. — Saved campaigns appear in the campaign list with status and live metrics; expand a row for its overview and quick actions. Click to enlarge.

Every campaign has a “⋮” menu in the top bar with four housekeeping actions: Preview (open the live experience exactly as a visitor would see it), Version history (browse previous saved versions and restore one), Duplicate campaign (make an editable copy), and Delete campaign (permanently remove it).

The campaign overflow menu: Preview, Version history, Duplicate campaign, and Delete campaign. — The campaign’s “⋮” menu holds Preview (see the live experience as a visitor), Version history (browse and restore previous versions), Duplicate campaign (make an editable copy), and Delete campaign. Click to enlarge.

When a campaign works, you rarely build the next one from scratch. Duplicate the campaign to get an exact copy — audience rules, content actions, and settings all carried over — as a new campaign in Test mode. It’s the fastest way to:

Reuse a proven setup — clone a winning campaign and change just the audience (e.g. run the same offer for a different country or segment).
Try a bigger change safely — duplicate, experiment on the copy, and leave the original running untouched.
Template your work — keep a well-built campaign as a starting point you duplicate whenever you need the same structure.

The duplicate always starts in Test mode, so cloning never accidentally pushes a second campaign live.

Measure performance

Once the campaign is live, the campaign performance dashboard shows aggregate performance against the primary goal and every action: how many visitors saw the campaign, which actions they clicked, how each action performed vs. the prior period, and where traffic is coming from.

Personyze Campaign Performance dashboard measuring the campaign against its goal. — The campaign performance dashboard. Click to enlarge.

What the performance view shows:

Visits over time — daily volume of visitors in the audience, so you can spot delivery gaps, traffic-source shifts, or day-of-week patterns.
Actions clicked — click-through per action inside the campaign, ranked from best- to worst-performing. Actions with low CTR are called out as candidates to redesign or remove.
Action performance & conversions — conversion attribution per action against the campaign’s primary goal, compared to the prior reporting period.
Comparison to prior period — every KPI is shown vs. the same length of time immediately before, so you can see whether performance is trending up, flat, or declining.

Drill into individual visitors

Aggregate numbers show what’s happening; the user report shows who it’s happening to. Every visitor who interacted with the campaign is listed with their full session context — the pages they visited, actions they saw, what they clicked, and what they bought (or didn’t).

Personyze Campaign User Report: metric cards and the list of individual visitors behind a metric, for drilling into each visitor. — Pick a metric to list the exact visitors behind it, then open any visitor for full detail. Click to enlarge.

Clicking a visitor opens their full report — identity, activity, location, CRM profile fields, and interests. Click to enlarge.

What the user report is useful for:

Qualitative patterns — read individual visitor sessions to see what real users experienced. Aggregate numbers hide the story; individual sessions reveal it.
Diagnosing under-delivery — when a campaign should be reaching more visitors than it is, drilling into specific sessions often reveals the cause (an audience rule too strict, an action selector missing on some pages, a trigger not firing on mobile).
Sales / CS follow-up — for B2B use cases, filter the report to a specific known account or CRM contact to see exactly what marketing content that person has been exposed to.
Internal IDs — if you’re passing a CRM ID or user ID as a Personyze internal identifier, the report links visitor sessions across devices and stitches them into a single user timeline.

Before you launch: a quick checklist

Run through this before switching a campaign to Live:

Audience defined? The forecast shows a sensible would-match count — not zero, not half your traffic — and spot-checking individual visitors confirms they’re the right people.
Content correct? Every action previews the way you expect, and any Split Cases resolve to the right variation per audience.
Overlaps handled? If this campaign can collide with another, the audiences share a group with priorities set.
QA passed? You ran the QA Simulator in Test mode and fixed anything it surfaced.
Saved to the right mode? Test while you’re still verifying; switch to Live only when it’s ready for real visitors.

Once live, watch the performance dashboard and drill into individual visitors to confirm the campaign is doing what you intended.

Targeting Rules in Personyze — every audience rule type with examples
Resolve Audience Overlaps and Conflicts
Page Groups — reusable groupings of URLs for audience & content rules
Personyze QA Simulator
A/B Testing
Setting Custom Goals Tracking