Troubleshoot collection and advertising tags

1. Check the domain in the console and complete verification.
2. Check the live page for one Button script, then inspect failed network requests, consent conditions, blockers and CSP errors.
3. Check that you are viewing the correct site and time period. Allow for processing before comparing reports.
4. Reproduce a fresh visit. Record the URL, time and observed error if collection still does not appear.

Check which script variant is installed. The invisible=true variant intentionally hides the twirling space button. Confirm collection using Network requests and fresh measured events rather than the button's visibility.

Check for mode=redirect in the script URL or a Site Protect plugin installation. Redirecting to the main page when the Button cookie is missing is the purpose of this mode. Use the standard or invisible script if you only intended to collect traffic evidence.

• Compare the installation variants

Check whether the path is configured for Smart Bidding Training, protection is enabled, and the plan allows protection. With protection off, Smart Bidding Training loads configured tags for all access tiers.

Look for an independent loader in page code, GTM, ecommerce apps or plugins. A duplicate can bypass the intended filtering. Check the percentage bypass and ad-click-only options as well as which path is the most specific match.

On a protected path, an untrusted visit may correctly receive no tags. Automated browser testing can encounter this behavior. Also check configured IDs, consent state, ad-click-only loading, CSP and the live page’s network requests.

If existing event code fails when a loader is absent, review its stubs or guards. Restoring the previous tag setup may be necessary while you resolve an integration issue.

Configuration history records saved settings separately from files sent to the site. Review both when investigating a change. Publication records show what was written; they do not establish exactly when each browser applied it.

If you disable protection on a Smart Bidding Training path, Button loads its configured tags for everyone on that path. Switching to Analytics only is different: it does not provide that managed tag-loading behavior.

Include the affected site and page, time and timezone, installation method, relevant configuration version and a description of the expected versus observed behavior. Remove credentials and unrelated personal data from screenshots or logs.

• Contact support
• Return to installation