AUDIENCE

Test the audience
that matters.

Not every variant should hit everyone. Target by device, geography, visitor type, or URL, in the same prompt you use to describe the change. Segments stay attached to the experiment record for audit and reporting.

Plain EN
Audience in the prompt
Segments
Saved for reuse
Audit
Who saw what

Precision without a SQL query

Growth teams should not need an analyst to run a mobile-only pricing test.

TARGETING

Device, geo, and visitor rules

Limit tests to mobile, a single country, returning visitors, or traffic from a campaign URL. Rules are visible before launch so compliance and brand teams know exactly who is in the split.

SEGMENTS

Reuse audiences across tests

Save segment definitions your team uses often (enterprise trial traffic, logged-out homepage visitors, checkout starters), and attach them to new experiments in one click.

REPORTING

Segment-aware results

Lift is calculated on the audience in the test, not diluted by traffic that never should have seen the variant. Report outcomes with the segment name leadership recognizes.

Why targeting belongs in experimentation

Relevant tests

Checkout tests on checkout visitors, not blog readers.

Market-specific

Copy and offers differ by region; tests should too.

Campaign alignment

Measure the landing experience paid traffic actually sees.

Prompt-native

Say who it is for when you describe what to change.

Related capabilities

Prompt-Built Tests

Describe a change in plain language and it becomes a live experiment.

See how tests start

Experiments

Create, QA, launch, and monitor tests from one workspace.

See the workflow

Run the right test for the right visitors.

Get in touch

Questions, enterprise, or a walkthrough: we'll reply shortly.

Prompt it. Test it.
Ship the winner.

Start building with RunPivot today.