Skip to content
Browse documentation

Verifying your installation

Verification checks that tracking reports from your website. The standard browser tag resolves the website from its hostname rather than an embedded site key. Confirm actual events arrive before evaluating traffic. Verification is separate from ad-account connection and protection settings.

On this page

AdProtektor cannot evaluate a visit it does not receive. Verify the installation and inspect actual event arrival before judging traffic or protection outcomes.

How to verify

  1. Install the snippet

    See Installing the tracking script.

  2. Publish your site

    Site builders and Tag Manager both require an explicit publish before changes go live.

  3. Visit your own site

    Open the site in a normal browser tab. That page view is what verification waits for.

  4. Check the dashboard

    Open Settings → Install code and check the verification status. Confirm events from the selected website appear in the dashboard.

When verification does not pass

Work through these in order. They are roughly ordered by how often they turn out to be the cause.

  1. The change was never published. Tag Manager containers, Webflow projects and most site builders stage changes until you publish. This is the most common cause by a wide margin.
  2. The snippet is on one page, not all pages. Check a landing page your ads actually point at, not just the home page.
  3. An ad-blocker is blocking it in your own browser. Try a different browser or a private window with extensions disabled.
  4. The website or keyed integration is mismatched. Check that the selected website matches the hostname where the standard tag runs. For WordPress or another integration that requires a key, check its configured key against that website’s dashboard instructions. The standard browser tag contains no key to replace.
  5. A caching layer is serving the old page. Purge your CDN or page cache and reload.
  6. A Content Security Policy is blocking the script. Check the browser console for a CSP violation and allow our CDN host.

Confirm it directly in the browser

Open your site, then your browser's developer tools, and look at the Network tab for a request to our CDN. If the request is not there at all, the tag is not on the page. If it is there but failing, the response tells you why.

Verification and re-verification

Once verified, a website stays verified. If you later remove the script, usually through a theme update that overwrites your header, traffic simply stops arriving. Setting up an alert rule is the fastest way to notice that. See Alerts.

Frequently asked questions

How long does verification take?

Check the status after publishing the installation and visiting the website. If verification or event arrival remains unconfirmed, work through the checklist above. A delay alone does not identify the cause.

Does my own traffic count against my plan volume?

Your visits are tracked like any other, but plan volume is metered on billable ad clicks rather than total page views, so ordinary internal browsing does not meaningfully consume it.

Make your next click count

Your budget has better places to go.

Connect your campaigns, configure your protection and let AdProtektor handle the ongoing checks. Start with your own traffic.

free trial • Cancel anytime • Automatic protection • Already a customer? Log in