Tracking test mode

From Getting started or Site Settings, open Tracking test mode. A website owner or administrator can start a private session lasting 15 minutes. Open its website link in a separate tab, navigate and perform the action you want to diagnose.

The current tracker detects the token in the URL fragment, removes the fragment and keeps the session in that tab's session storage. The token is stored as a hash on the server. Do not share the link. First-party proxies must also forward /pf-test.min.js.

What you can verify#

• Whether requests arrive for the configured domain.
• Consent, Do Not Track and excluded-path decisions.
• Page paths and event names, including delegated no-code events.
• Which active goals match each accepted diagnostic event.

Diagnostic acceptance validates these setup rules. It does not predict production traffic classification, deduplication or rate limits.

Only diagnostic event names, paths, decisions and matching goal names are stored, separately from analytics. Query strings, referrers and client identities are not retained. A session accepts at most 500 events, and the page shows the latest 50.

Test events never create visitors, conversions, rollups, integrations or tracking-health evidence. A revoked or expired token is rejected and never falls through to normal ingestion. End the session and close its tab when finished: that tab stays isolated after expiry. A new session replaces your previous session for that website; old diagnostic records are cleared on replacement or explicit end, and expired sessions are pruned when a new test starts.

If no events arrive, confirm that the current tracker and optional test module load, your proxy forwards both, and the browser's blocker or Content Security Policy allows them. A test session cannot validate a missing script.