Skip to content

Site ID

Throughout the documentation, you’ll see references to the Site ID. Support generates this value during the initial integration stage. Your technical team will use this value when incorporating add-on features. This value will appear at the top of your dashboard and in your reports.


Sometimes you might here us using the term “apikey”. This is synonymous with “Site ID”. All customers have at least one Site ID/apikey, but not all customers have access to the API. The API is a premium add-on feature that also requires an API Secret that is not visible to customers without API access.


Typically the production Site ID consists of the Domain name, e.g., As for Sandbox Site ID’s they often take one of two forms:

  • if you only have a single production dashboard
  • sandbox.publisher-name if you have multiple production dashboards
The structure of a url. The Site ID is usually the same as the Domain name.


Consolidated tracking automatically tracks the subdomains that belong to a given Site ID. So if you have content at then you would still use as the Site ID that you specify in the tracking code.

You would still be able to find your content performance in your dashboard through a variety of ways:

Split tracking

Suppose your site has two, or more, subdomains that each have their own audience and content strategy. It’s important to you that these be treated as separate entities. In that case we can assign unique Site IDs. You would then have multiple dashboards — each with its own users. And while the dashboards may be split, you can join them together with the Network Rollup or Site Group views.


While you would have enhanced navigation and control with split tracking, you would also face a couple of limitations.

  • Overlay does not track across Site IDs.
  • API results will be siloed within each Site ID (if purchased).


In the same way that we automatically track subdomains, we also automatically track subdirectories. Another similarity is that you could split subdirectories into their own dashboards if that is a requirement. We would format subdirectories as follows: would yield the Site ID of The same advantages and disadvantages of split tracking apply.

Changing domains

With time, you may decide to rebrand your site and choose a new second-level domain (SLD). An important thing to know is that does not track cross-domain by default. So what are you to do? First, read this primer on migrations. Second, consider these two options:

Hold on to your data

If you would like to be able to use your historical data (most people do) for trend analysis, comparison mode, and more, then this is the option for you. All you would need to do is tell us your new domain name and we will allow list this to your old Site ID. So, when your new sites starts sending pageviews claiming it to be your old site, we’ll know it’s legitimate and intentional.

A fresh start

If you want to forget the past and never look at your old Site ID, that’s okay too. We’ll issue a new ID and you’ll send your page views there.

Last updated: May 24, 2024