Personalization

Audiences

Create returning visitor, mobile user, campaign traffic and cart visitor audiences.

Last updated: May 22, 20268-14 minBeginner to intermediate
Start free See pricingMethodology

The right variant for the right audience

Personalization lets teams show a more relevant experience based on user intent, source, device, location or customer attributes instead of showing everyone the same message. Testvoy keeps this manageable with reusable audiences, UTM personalization, behavioral targeting and segment-level reporting.

Different CTA for returning visitors

More direct offer for Google Ads traffic

Shorter form for mobile users

Local message for TR users

Special banner for cart visitors

Audience routing
AudienceVariantReport
Choose a segment, map it to a variant and read results by segment.

Keep personalization measurable

Personalization campaigns should not be display rules only; they should produce a result report. If teams cannot see which segment responded to which variant, personalization becomes a hard-to-defend assumption.

  • Is the audience reusable?
  • Are UTM parameters correct?
  • Are device/geo rules too narrow?
  • Is each segment large enough?
  • Can the campaign result be read in reporting?

Example personalization campaign

Example: show a more direct offer to Google Ads traffic and a trust-focused message to organic traffic. Define two audiences in the campaign, choose different hero copy for each and read results with segment-level reporting.

  1. 01

    Audience 1: utm_source equals google

  2. 02

    Audience 2: utm_source is empty or organic

  3. 03

    Google Ads variant: short offer and direct CTA

  4. 04

    Organic variant: trust, methodology and report example

  5. 05

    Goal: signup_completed

  6. 06

    Read report by audience

Example audience routing
Google Ads traffic -> Variant: Direct offer
Returning visitors -> Variant: Shorter signup CTA
Mobile users -> Variant: Compact hero
TR visitors -> Variant: Local pricing message

Practical scenario

A growth team changes CTA copy on the pricing page, connects signup_started and signup_completed goals, then reads Google Ads and returning visitor segments separately. If the result is promising, they share a report link with the client or leadership.

Common mistakes

Most mistakes come from wrong project keys, overly broad selectors, missing goals, staging/prod mixups, early decisions on small samples or skipping mobile QA.

Naming an experiment 'test'

Launching without a goal

Deciding on total CVR only

Sending screenshots instead of shareable reports

Frequently asked questions

Who is Audiences for?

Marketing, growth, product and developer teams can use the same guide at different depths.

Do I need a developer?

Not for basic visual changes and report reading; SDK, custom events, custom JS or enterprise security benefit from technical support.

How do I know it worked?

Verifier, recent events, preview, QA checklist and report warnings show setup and experiment health.

What is the common mistake?

Wrong project keys, missing goals, fragile selectors, early decisions on small samples and skipped mobile QA are common.

Docs

Try this guide in the app

Finish setup, create your first experiment and read the report with cleaner data in Testvoy.