Sites refer to the domains we want to apply to locations when setting up an experience. The site is usually the domain associated with your testing however you may want to assign sites to pre-prod or staging environments to allow you to QA in a controlled environment. You may also want to group multiple domains into one site to use for a broader location.
Accessing the site manager
You can access the site manager screen from the navigation.
When you land on the site manager screen it will show you all your created sites, how many locations are using them and when they were created or last modified.
Creating a new site
To create a new site use the 'Create' button in the top right which will open the site creation fly-out.
This opens the site creation fly-out.
New site
In this section we need to give our site a name. It might be that this is for a staging site and we can add that info here as well as adding a description for others to know which site this relates to.
If you are delivering experiences across multiple domains this is also a place where we can specify this.
Domain details
In the domain details we will be adding the domains associated with how we want to define the site itself. This can be single domain or multiple domains depending on what it is you need and where you want to deliver experiences.
Once you have added the first domain, the option to add further ones will become available.
Cookie domain
In the context of A/B testing, the Cookie Domain setting determines where tracking cookies are valid — specifically, which parts of your website can access and share the same user session and variation data.
What it means:
When you set a cookie domain like
.my-url.com, it applies to:my-url.comwww.my-url.comshop.my-url.comblog.my-url.comand any other subdomains
This ensures consistent test experience across all those subdomains.
Why it matters:
If you’re running a test that spans multiple subdomains, you want users to stay in the same variation when they navigate across them.
Without setting a shared cookie domain, a user might:
See Variation A on
www.my-url.comThen be treated as a new visitor and see Variation B on
shop.my-url.com
This could break test accuracy.
No need to edit this field manually unless you have a very specific cross-domain setup. It's usually set automatically to ensure reliable tracking across your entire site structure.
Once you have completed the above fields you can click 'Save' and the site will be available to use.
Updating a site
You have the ability to update sites if you need to change the configuration. You can do this the same way as creating a new one however you will select the edit icon from the site manager screen and make your changes before saving.
Be aware, sites are assigned to locations, not tests or targets. So any update to the site will apply to all of the locations using the site and within your project. If you clone your test for example, the site update will apply to all of the clones too as they are in that same location and project.
Sites can be shared by projects. E.g. you could have a site called "checkout flow", and 10 locations all using that same site. Any update to the site will again apply to all locations and projects that use it.
For more info on projects see this article.
For more info on locations see this article.
Within the edit screen you can see which locations are currently using that site so you will know the impact of making any changes.
