Site settings
Every site-level option: reporting timezone, exclusions, captured query parameters, affiliate paths, bot traffic, appearance and deleting a site.
Each site's Settings page holds everything that shapes what gets counted and how it is reported. Reach it from the gear at the foot of the site's navigation rail. Only organization owners and admins can change settings, and changes save themselves a moment after you stop typing. There is no Save button to miss.
General
| Setting | What it does |
|---|---|
| Reporting timezone | All charts, date ranges and daily buckets use this timezone. Set it to where your audience or team lives; it defaults to UTC. |
| Appearance | A color scheme for this site. It applies to everyone who views the site in Numative, shared dashboards included, and overrides the organization and personal schemes. |
Privacy and exclusions
These apply to Numative tracking.
| Setting | What it does |
|---|---|
| Respect Do Not Track / GPC | Off by default (the tracker is cookieless either way). On, visits from browsers sending DNT or Global Privacy Control are not recorded at all. |
| Keep query strings | Off, URLs are grouped by path. On, ?query params are kept as part of the page URL, which turns one page into as many rows as it has parameter combinations. |
| Capture query parameters | The finer instrument for the same problem. Name individual parameters, one per line, and each is stored as a property on the pageview: the page stays one row while the value becomes something you can break reports down by. An allowlist on purpose, since query strings routinely carry email addresses and reset tokens. Up to 12 per site. See Enhanced measurements. |
| Affiliate link paths | The paths your cloaked affiliate links redirect through (/go/*). Clicks on them are reported separately under Interactions rather than counted as visits to a page on your own site. |
| Include bot traffic | Bots are always detected and tagged but excluded from reports by default. On, they are counted, and you can still separate them with the Bots & AI crawlers filter. |
| Additional domains | Events are accepted for your domain and all its subdomains automatically. List other domains the same site is served on; events from unlisted domains are ignored. |
| Excluded paths | One per line. A trailing * matches a prefix: /admin/* excludes everything under /admin/. Excluded visits are never stored. |
| Excluded IP addresses | One per line, as a single address or a CIDR range. This is how you stop counting your own visits. Numative shows the address you are browsing from with a button to exclude it in one click. |
| Ignored paths for change tracking | One per line, * allowed. Pages matching these are still counted in analytics, but are never crawled and never generate change events. Use it for churny paths like paginated archives and tag pages. Pages behind a login are detected and left alone automatically, so there is no need to list those. |
Excluding your own visits
An IP rule is network-scoped, so one entry covers every browser, browser profile and device behind that connection, and it is enforced on our side rather than by a flag in your browser that clearing site data would wipe. It applies to pageviews, custom events, errors and speed data alike.
| Entry | Covers |
|---|---|
203.0.113.7 | That exact address. |
203.0.113.0/24 | A whole office network, without listing each address. |
2001:db8:1234:5678::/64 | An IPv6 network. Offer this rather than a single IPv6 address: operating systems rotate the second half of an IPv6 address for privacy, so an exact address stops matching within days. |
- A home connection's address can change when the router reconnects. If your own visits reappear, open Settings and click the button again.
- Mobile data is a different network, so a phone off wifi is not covered by your home rule.
- An entry that is not a valid address or range is flagged in Settings rather than saved as a rule that quietly matches nothing.
This is separate from Respect Do Not Track, which is the visitor-facing opt-out: see Privacy.
Visibility
Public dashboard shares a read-only view of the site's stats, either through a private link or fully public at a clean URL with your domain. Covered in Public dashboards.
Public visitor counts publishes just this site's visitor counts at a keyless URL, so you can show "12 reading now" or "48,120 visitors this year" on your own pages, and generates the snippet to paste. Beside it, anyone may ask for sets how much history that URL will answer for: live only (the default), the last 30 days, the last year, or any period. Its own switch, separate from the public dashboard, because it publishes counts rather than the site. See the badge documentation.
Also on the Settings page
- Data sources: Numative tracking and Google Analytics can both back one site. Turn on either or both, and pick which the dashboard opens on; the switcher in the site header moves between them. Turning one off deletes nothing.
- Tracking snippet: the ready-to-copy script tag for this site (see Install the snippet).
- Count blocked visitors: a custom tracking domain or a paste-ready reverse-proxy config, so ad-blocked visitors are still counted (see Count blocked visitors).
- AI crawler tracking: the server-side feed setup and ingest key (see Bots & AI crawlers).
- Google connections: Google Analytics and Search Console.