Site-Wide Tracking

By default, Split Test Pro only records events on pages with running experiments. Site-wide tracking is an opt-in workspace setting that records anonymous page views and goal events across your whole site — not just pages with experiments. It powers program metrics without GA4 and improves feasibility estimates for surfaces you haven’t tested.

You’ll find it in Settings → Site-wide tracking (workspace owners only; included in Pro and Agency; off by default).

What It’s For

• Program metrics without GA4. Your Global Goals north-star series needs site-level data. On HTML sites without GA4, site-wide tracking is how those numbers exist at all.
• Feasibility for untested surfaces. The plan generator’s projections need traffic estimates per surface. Surfaces you’ve never tested show “Traffic unknown” on the Testing Overview — site-wide data fills them in.

What’s Recorded

Deliberately little:

• Page path only — never query strings or fragments; they’re stripped in the script and again server-side. No PII, no full URLs.
• Goal and order events — the same conversion goals your experiments already use, so the north-star series matches how experiments measure.
• A sample, not everyone. Only a deterministic sample of visitors is recorded at your configured sampling rate — 100%, 25%, or 10%. Guidance from the settings page: under 50k sessions/mo use 100% · 50–250k: 25% · over 250k: 10%.
• Server-enforced caps. The server enforces the sample and a daily volume cap independently of the script. If your traffic exceeds the daily cap, recording pauses until tomorrow and the app suggests a lower sampling rate.

Consent and Privacy

Site-wide events respect the exact same privacy gates as experiment analytics:

• HTML sites: Do Not Track, Global Privacy Control, and the SplitTestPro.optOut() API all block site-wide events.
• Shopify: site-wide events are only ever emitted by the consent-gated Web Pixel — Shopify won’t run it without analytics consent.

You remain responsible for disclosing site-wide analytics in your privacy policy and wiring your consent manager — enabling this extends event collection from experiment pages to your whole site. The full picture, including cookie-banner integration patterns, is in Privacy and Consent.

Sampling Changes and Turning It Off

• Changing sampling starts a new metrics series — comparisons never mix sampling rates, so your Global Goals baseline resets to the new series.
• Effect timing: on HTML, changes take effect on the next page load; on Shopify, via your web pixel within a few minutes.
• Turning it off stops collection on the next config fetch or pixel refresh — and the server stops accepting site-wide events shortly after opt-out regardless of cached scripts.

Next Steps

• Where the numbers surface: Global Goals
• The projections they sharpen: Testing Overview
• Your disclosure obligations in detail: Privacy and Consent