Tagging Pixel verification

Why the check can report a missing pixel that is actually there, and the two things that fix it.

Once the Tagging Pixel is installed, AdPage checks whether it really loads on your website. This page explains what that check does, and what to do when it reports a missing pixel that you know is there.

How the check works

The check opens your shop page in a real Chromium browser from Amsterdam, waits for the page to finish loading, and looks for two things: scripts loading from your tagging domain, and the hits those scripts send.

Loading the page in a real browser matters. A check that only reads the page source cannot see a script that is added while the page loads, and would report a working pixel as missing.

The check runs when you press Verify pixel in your container settings, and once a day on its own.

When the check reports a missing pixel

Two causes are common, and neither of them means something is wrong with your pixel.

1. No website URL for this domain

The check needs to know which page to open. If the Website URL is empty for this tagging domain, AdPage derives it from the tagging domain itself: tagging.example.com becomes example.com.

That guess is right for most shops, but not all. If your shop lives somewhere else, the check opens the wrong page, finds nothing, and says so. You will recognise this case by the wording: the result mentions that the URL was derived.

Fill in the website in Settings → Tagging Pixel and verify again.

A container can have several tagging domains, and each one has its own Website URL. Filling it in for one domain does nothing for the others — check each domain you use.

2. Your firewall or bot protection blocks the check

A firewall, WAF or bot protection in front of your shop can refuse visitors it does not recognise. Our check is then turned away before it ever sees your page, and the result looks the same as a missing pixel.

The fix is to allow our check through. Your container dashboard shows the IP addresses it comes from, with a button to copy them.

Copy the addresses from your dashboard, not from this page. The list is kept up to date automatically, and the dashboard always shows the current one. If verification starts failing again later, open the dashboard and compare the list.

1

Open your container dashboard

The list appears under Automatic verification still pending, or under the pixel status when a check has failed.

2

Copy the addresses

Use Copy list to put all of them on your clipboard at once.

3

Allow them through

Send the list to whoever manages your hosting, firewall or bot protection, and ask them to allow these addresses. In Cloudflare this is a WAF rule; in other setups it may be an IP allowlist or an exception for a security rule.

4

Verify again

Press Verify pixel in your container settings. The check should now reach your page.

Confirming the pixel manually

If you cannot change the firewall, you can confirm the pixel yourself with Confirm manually. Your container then stops warning about an unfinished setup.

Be clear about what this does and does not do:

• It records that you checked the pixel. It does not verify anything on our side.

• AdPage keeps checking in the background. As soon as a check sees your pixel load, your manual confirmation is replaced by a real verification.

• It does not make tracking work. If the pixel genuinely is not installed, confirming it manually only hides the warning — you will still see no data coming in.

To check the pixel yourself, open your website, press F12 to open the developer tools, go to the Network tab and filter on your tagging domain. Reload the page. If you see requests to that domain, the pixel is loading.

What's next?

With the pixel verified, your container is collecting data. From here you can move on to the tracking rules in your Google Tag Manager containers, or check the data quality of your setup under Monitoring.