Settings

/dashboard/<siteId>/settings has four sections, shown as a row of pills across the top and addressable with ?section=general, install, plan or danger. Only one section is on screen at a time; switching keeps your scroll position.

General

Site details, what to leave out, and the public dashboard.

Field	Effect
Name	The label in the site switcher. Cosmetic
Timezone	Where every day, week and month boundary is cut. Does not affect the visitor id or the billing month, both are UTC
Currency	Which currency the Revenue screen opens on, and which currency a revenue event must be in to be added to a visit’s own revenue column
Excluded IPs	One per line or comma-separated. Exact string match against the client address, no CIDR, no wildcards, and IPv4 and IPv6 are separate entries
Excluded paths	Globs, one per line. `` within a segment, `*` across segments

Both exclusion lists take effect within a minute: the collector caches the site row for 60 seconds. Neither removes data already collected. See Bots & exclusions.

Public dashboard

One switch: Publish public dashboard. On, a read-only overview appears at /share/<shareId>; off, nothing about the site is reachable without signing in. Toggling it twice mints a new id and kills the old link.

See Sharing.

Install

The snippet, the tracking API, and the keys that read your data back.

Tracking snippet

Ready to copy, with your site key and the collector URL filled in:

<script defer
  data-site="pk_live_xxxxxxxx"
  data-api="https://ingest.tracing.tools"
  src="https://ingest.tracing.tools/t.js"></script>

The same tag collects Core Web Vitals by default. Under it: the site key, the timezone and the currency at a glance.

Tracking API

tracing("signup_completed", { plan: "pro" })
tracing.revenue(49.00, "USD", { plan: "pro" })
tracing.identify({ email: "a@b.c", plan: "pro" })
tracing.pageview()

<button data-tracing-event="cta_click" data-tracing-event-position="hero">

Framework-specific versions live in Installation guides.

API keys

Create a key, and the plaintext is shown once:

tk_live_…

Only a SHA-256 digest is stored, so a leaked database gives nobody a working key, and nobody, support included, can recover a key you did not copy. The list shows the name, the last four characters, when it was created and when it was last used.

Keys are account-wide, not per site: a key can read every site on the account. Revoking is immediate.

curl -s -H "Authorization: Bearer tk_live_…"   "https://tracing.tools/api/v1/sites"

See Authentication.

Plan & usage

Four cards, in the order the questions get asked.

What you are on — plan, price, interval, status, renewal or end date, trial days left, and the buttons to change or cancel.
Usage this month — every event collected across every site on the account, counted in UTC, with a projection to month end and the busiest sites so a spike has a name.
What the plan includes — the feature list, and one line about what happens past the included events.
Invoices — receipts, with hosted and PDF links.

See Plans & limits and Usage & overage.

Danger zone

Three irreversible actions.

Rotate the site key

Mints a new pk_live_…. The old snippet stops reporting as soon as the collector’s one-minute site cache expires, so update every page that embeds the old key before you rotate, or accept a gap.

Data already collected under the old key stays — it is keyed on the site, not on the key.

Reset data

Deletes every session, event, property and trait for the site. The site, its key, its settings, its goals and its saved funnels survive. There is no undo and no confirmation dialog.

Delete the site

Type the domain to confirm. The site disappears from the dashboard, its key stops resolving, and the tracker on your pages starts getting 404 from the collector.

Account settings

/dashboard/account covers the things that are not per site: profile, billing email and account deletion. Account deletion goes through the authentication provider.