Skip to main content

​
What a site is

A site in Traceten corresponds to a single domain. Each site has its own:
  • Tracking snippet with a unique site key
  • Traffic data and event feed
API keys are managed separately, at the account level, and can optionally be scoped to a single site. See API keys.

​
Creating a site

1

Open Add site

Open the site switcher at the top of any dashboard page and choose Add site at the bottom. Only workspace admins can add a site.
2

Enter your domain

Enter your domain without the protocol or path. For example: example.com, not https://example.com/.Use the root domain, not a subdomain, unless you want to track the subdomain separately. A display name is optional; leave it empty to show the domain.Cookie domain is optional, and we strongly recommend setting it: enter your registered domain (for example example.com) so one visitor is recognised across your subdomains. It must be your site’s domain or a parent of it. See Subdomains and cross-domain.
3

Install the snippet

Click Create site. Traceten sets the site up and opens its install page, with your site key already in the snippet. Follow the steps there to add the snippet to your site.

​
Finding and switching sites

The site switcher at the top of every page is how you change the site you are looking at. Settings → Sites lists every site in your workspace with its install status; click one to make it the current site and open its Overview. Sites in the sidebar opens the pages of the current site: Install, Settings and Events. Change the site with the switcher and you stay on the same page for the new site. Conversions for every site are on the Conversions page.

​
Multiple sites

You can track multiple domains under one account. Each domain needs its own site and site key. Do not use the same key across multiple domains, or attribution data will be mixed together. Common setups:
  • example.com and docs.example.com as separate sites
  • Production and staging as separate sites with different keys
  • Several distinct products or brands, each on its own domain, under one account
Every site is fully isolated: its own snippet key, its own traffic and event feed. Data never crosses between sites. Dashboard links name their site. A page that shows one site carries ?site= in its address, so a link you copy opens the same site for a teammate in your workspace, whichever site their dashboard opened on last. Your plan sets how many live sites you can have: 1 on Starter, 7 on Growth and 30 on Pro. Sites pending deletion do not count. At the limit, Add site shows an Upgrade plan link instead of the form. EU data residency is not available. See Data residency.

​
Revenue attribution is per site, with its own Stripe account

Revenue integrations are pinned to a single site, not shared across your account. When you connect Stripe (or Shopify), you connect it to one specific site, and each site connects its own, separate Stripe account.
  • One Stripe account per site. A site attributes revenue from the Stripe account connected to that site. To attribute revenue on three sites, connect three Stripe accounts, one to each site.
  • A Stripe account can be connected to only one site. The same Stripe account cannot be connected to two different sites in Traceten. If your sites all charge through a single Stripe account, they cannot each carry their own revenue attribution from it; give each site the Stripe account that bills its customers.
  • Attribution joins on the exact site. A payment from a site’s Stripe account is matched to sessions on that same site. Revenue never leaks between sites, even when they belong to the same Traceten account.
This is why multi-brand and multi-product accounts work cleanly: each site sees only the revenue from its own Stripe account, attributed only to its own AI traffic. To connect a site’s Stripe account, open Settings → Integrations, choose the site at the top of the page, pick Stripe, and paste that account’s restricted API key. The page names the site every connection on it belongs to. See Stripe revenue attribution for the connect flow. Each site’s display currency, the currency its revenue totals are shown in, is under that site’s Settings → Revenue.

​
Rotating an API key

If an API key is compromised or lost, revoke it from Settings → API keys and create a new one. The old key stops working immediately. Update any integrations that used it. See API keys.

​
Deleting a site

Deleting a site is a two-stage process. Requesting it stops tracking straight away; nothing is erased for 30 days, so you can undo it. To delete a site: make it the current site, choose Sites → Settings in the sidebar, scroll to the Danger zone, and click Delete site. You’ll be asked to confirm by typing the site’s domain. A fixed confirmation phrase can’t tell one of your sites from another, so we ask for the one you mean. Immediately, when you confirm:
  • Collection stops. Pageviews, conversions, identity calls and crawler reports for this site are all refused at the edge, so a snippet still installed on your pages adds nothing new. Orders arriving from a connected Stripe or Shopify account also stop being attributed to it.
  • The site disappears from your dashboard, the site switcher and your list of sites.
  • The site stops counting toward your plan’s site limit, so you can add a replacement right away.
Remove the snippet from your pages. Deleting the site stops us accepting its data, but it does not remove the script tag from your site. Take it out before or shortly after the erasure runs: once the site record is gone we can no longer tie anything it sends back to your account.
After 30 days, all of the site’s data is permanently erased: sessions, events, conversions, revenue attribution, crawler activity, its chart notes, its API keys, its integrations and its webhook endpoints. That includes the webhook endpoint Traceten created on your own Stripe account for this site. We delete it there too, so nothing we made is left behind. This cannot be undone. To restore it, go to Settings → Sites. A site awaiting deletion appears under Pending deletion with the date its data will be erased and a Restore button. Restoring resumes collection, and everything recorded before the deletion is still there.
Restoring does not backfill the window. Nothing was collected while the site was pending deletion, so its sessions, conversions and revenue show a gap covering that period, including any Stripe or Shopify orders that arrived during it, which are permanently unattributed. Restoring is also refused once the erasure date has passed.
Restoring counts against your plan’s site limit. If you deleted a site and added a replacement, restoring may put you over the limit. Delete another site or upgrade your plan first.
Deleting one site does not affect your other sites or your account. To close your whole account, see Account deletion. Data deletion requests for individual visitors can be submitted via the data deletion API.