Targeting

Decide where and for whom
a test runs.

Pages, audiences, schedule and traffic share, for each test.

  1. 01Pages by path
  2. 02Audiences with AND/OR
  3. 03Schedule and environments

The building blocks

The settings
at a glance.

Few settings, each one explained.

Pages by path

Exact path, path starts with, or all pages. Only the path is compared, no domain, no ?query, no #anchor.

Device and language

Mobile only, desktop only, or only visitors with a particular browser language.

Campaign and referrer

Rules on query parameters such as utm_source and on the domain the visitor arrived from.

AND or OR

Several conditions must all apply, or one is enough. You decide per experiment.

Schedule and environments

Set a start and an end, and decide whether a test runs only on staging or live.

Traffic share

Not every test has to run 50/50. A risky idea gets 10% first, and more later.

Staying clean

Overlaps are checked
at launch.

If two tests change the same page, neither measures its own effect. abdriven spots this and does not start the second test there.

  • Overlaps are checked at launch, not discovered later in the results.
  • The preview bypasses audiences and schedules, so you see your variation even when you do not fit the target yourself.
  • The traffic split check reports when the actual distribution deviates from the planned one.
  • A winner kept live retains pages, audiences and environments, only the schedule no longer applies.

Afterwards

Results by device,
source and visitor type.

Targeting decides who takes part. Segments show afterwards who the variation worked for, without you having to set anything up in advance.

  • Broken down by device, traffic source, and new versus returning.
  • Recorded once at first contact, with no identifier alongside.
  • Meant as exploration: cells with fewer than 100 visitors per arm are not compared at all.
  • A segment finding is a hypothesis for the next test, not a result in itself.

FAQ

Targeting

Can I target by country?

No, that would mean evaluating the IP address, which abdriven deliberately does not process. For most cases, browser language and campaign parameters are enough.

What happens to visitors who do not fit the target?

They see the normal page and are not counted. They appear neither in the result nor in your booked traffic volume.

Can I ramp a test up slowly?

Yes, through the traffic share. Just bear in mind that a small share takes correspondingly longer to reach the planned sample size.

Test your website
with abdriven.