Documentation / Build and launch
Audience and allocation
Choose who enters the experiment and which stable identity assigns a variant.
Step by step
- Set the page prefix and traffic share in the draft. Use Settings for supported UTM, device, language and referrer filters. Review their combined scope before launch.
- Cookie identity is the default. A logged-in user ID requires a valid window property path. IP allocation is available only with direct delivery; User-Agent may group many visitors together.
- Use allocation salt intentionally. Reusing it can align assignments across tests with matching shares, but does not create a registered joint analysis.
A campaign landing page: limit the test to the intended UTM audience and check both campaign and ordinary visits. UTM matching can keep a consenting visitor in the audience until the tab closes.
How to verify
Test an eligible and ineligible visit. Language refers to the configured browser-language targeting, not a guarantee about page translation. Device type and identity source change what your sample represents.