Verifying your installation

Verification is not a formality. AdProtektor cannot score a visit it never sees, so a website that has not verified is not protected, regardless of how the rest of its settings look.

How to verify

1. 1

   Install the snippet

   See Installing the tracking script.

2. 2

   Publish your site

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

3. 3

   Visit your own site

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

4. 4

   Check the dashboard

   Open Settings → Install code. The status flips to verified within a few seconds of the first page view arriving.

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 site key is wrong or from a different website. Copy it again from Settings → Install code for the site you are verifying.
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.

Verification and re-verification

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