Page routing
Send one URL to different pages. A rule either picks a page when the request matches its conditions, or splits traffic across variants. Routing is keyed by the page name in the URL and outranks it, so a route can name a page that does not exist and still serve something.
Routes
One per URL page name, as it appears in the address. It does not have to be a page that exists: routing outranks the page name, so a route can be a landing URL of its own with every rule pointing somewhere else.
Page name in the URL
editing
Rules
Tried in order, and the first that matches decides. A rule with no conditions never matches; a split with none applies to everyone.
split test
personalization
editing
Order
Type
Send to page
Condition match
Conditions
What the request must look like for this page to be shown. A rule with no conditions never matches. Headers and country are only known when someone arrives on the URL, never on in-app navigation.
Who is allowed into this test. Leave it empty to include everyone who reaches this URL. These do not choose which variant someone gets -- the weights below do that. Headers and country are only known when someone arrives on the URL, never on in-app navigation.
for the rule being edited above
Source
Field
Operator
Value
Variants
The arms traffic is split across. A visitor is drawn into one on their first visit and stays there. Weights are relative, and a missing weight counts as one. Every visitor is drawn, whatever they answered about cookies; only those who agreed to measurement are counted in the results.
for the rule being edited above
Page
Weight
Results
Views are how many times each arm was served as part of this test. Pick what counts as success and its column fills in beside them.
This app is not measuring anything yet, so there is nothing to show. Turn Enabled on under Analytics, and give it some traffic.
Period
Counts as success
Page
Views
Success
Counts are of events, not people, and a visitor who declined cookies takes part in the test but is not measured -- so these compare the arms against each other, not against total traffic.
Nothing here that fits? A control records a click once you give it an Analytics label. For something exact -- an order placed, a form finished -- add a Track Analytics Event step to whatever runs when it happens and name it yourself. The name appears in this list the first time one is recorded.