TraceGeneral settings
Install snippet, cookieless mode, allowed domains, proxy, timezone, site name and deleting a site.
Settings → General is the first tab of a site's settings. It covers how the site is tracked and identified.
Install the tracking script
The snippet that collects your analytics. Pick your platform — Script, Shopify or WordPress — and the instructions update to match; copy the snippet with the copy button. See Install the tracking script for details.
Every snippet is tied to the site through data-website-id and data-domain — that's how Trace knows which site an incoming event belongs to.
Verify installation opens the dashboard and checks your live site for the script. See Check it's working.
Cookieless / privacy mode
A switch below the snippet, off by default. It changes how Trace tells visitors apart:
- Off (default): each browser gets a random visitor ID, kept in a first-party cookie for a year, so the same visitor is recognised across days and visits.
- On: Trace ignores the browser's visitor ID and instead derives one from the visitor's IP address, browser, your site and the current date (UTC). The same visitor is still one visitor within a day, but a new day always means a new ID, even for a returning visitor.
The trade-off: visitor counts across several days run a little higher than reality, since a returning visitor on day 2 looks new. Same-day numbers (visits, bounce rate, pages per visit) aren't affected.
Before you rely on cookieless mode
- The tracking script still sets its first-party cookies (visitor and session IDs) in this mode; only how visitors are counted changes. Check your consent requirements with that in mind.
- Revenue attribution matches Stripe payments to the visitor ID from the browser cookie, so with cookieless mode on, revenue can't be attributed to visitors.
Domain
Your site's main domain, for example example.com. All of its subdomains are tracked automatically. Trace checks the domain against the origin of every tracking request; traffic from anywhere else is rejected, unless it's covered by additional domains below.
You can change the domain at any time. Historical data stays exactly as it was — data belongs to the site, not its domain, so a rename never loses or resets past stats. After saving, Trace re-checks the installation on the new domain. Make sure the snippet is live there, or new data will stop arriving.
Additional domains
Extra domains allowed to send events for the same site — useful for a staging environment, a checkout hosted elsewhere, or an embedded widget. Add them one at a time with Add; remove any with Remove. Their subdomains are allowed too.
Allow all domains is the blunt version: turn it on and Trace accepts events for this site from any domain. Use it only when you can't predict every domain in advance (for example a widget your customers embed on their own sites). Otherwise list the domains, since allowing everything also means anyone could send fake events into your dashboard.
This list controls which domains may send data. To keep a visitor's identity when they move between your own domains, also list them in the script's data-allowed-hostnames attribute (see Script options).
Managed proxy
Record the subdomain you've set up to serve the tracking script from your own domain (for example analytics.example.com). First-party requests are far less likely to be blocked by ad blockers.
Nothing on Trace's side needs to change: the script always sends data back to the origin that served it. Your proxy needs to forward /script.js and /api/collect (plus /replay.js and /api/replay/* if you use session replay), and pass on the visitor's IP and browser headers — see Using a first-party proxy.
Timezone
Defines what "today", "this week" and every other date grouping mean in your reports. Set it to the timezone your business operates in — a "Last 7 days" report uses day boundaries in this timezone, not UTC. The weekly summary email uses it too.
Website name
The label used in the sidebar, the workspace list, shared reports and email subjects. Changing it doesn't affect tracking, domains or stats.
Delete site
Permanently deletes the site, its goals, funnels and settings; its dashboard stops working for everyone. You confirm by typing the domain. This can't be undone, and only workspace admins and owners can do it.
Who can change these settings
Most settings tabs need the Editor role or above; Goals and Funnels need Member or above. Lower roles see the settings read-only. See Team & roles.
FAQ
I changed my domain — is my old data gone?
No. Data belongs to the site, not its domain name, so nothing is lost or reset.
Why did my events stop coming in after I changed the domain?
Trace only accepts events from the domains configured here. If your site is still served from the old domain (or one you haven't added), update the domain to match where the script really runs, or add the old one under Additional domains.
Should I turn on "Allow all domains"?
Only if you can't list your domains ahead of time. For a normal site plus a staging environment, add both domains individually instead.