Troubleshooting
Tracking is blocked or allowed unexpectedly
Trace the visitor preference, category mapping, published script map, and native consent integration.
Last reviewed September 12, 2026
Unexpected blocking usually comes from a wrong category mapping, an unpublished change, a stale configuration, or confusion between URL blocking and a platform’s native consent signal. Capture the exact visitor state and request, then follow the mapping and publication chain before relaxing enforcement.
Trace the decision
- 1.
Capture the exact state
Record the URL, browser, GPC state, saved preferences, selected category, request or cookie, initiator, and time.
- 2.
Check the identifier and source
Open the Privacy Inventory and confirm the identifier’s effective category, source resource, and any manual override.
- 3.
Check publication
Confirm the mapping is in the latest CDN configuration and that the site is not reading a cached older version.
- 4.
Check native signal targets
Google, Meta, Microsoft, and LinkedIn tracker URLs may be deliberately allowed when their integration is enabled; verify the corresponding platform signal instead.
- 5.
Check unmapped activity
Unmapped resources are allowed by default. Expand discovery coverage and classify the resource before expecting category-based blocking.
- 6.
Restore the website if needed
Use Passive behavior or disable the banner while correcting a classification that breaks an essential function, then retest before reactivation.