How IsPixelWorking checks your tracking

IsPixelWorking loads your page in a real browser, watches what your ad tracking sends, and turns that into a report. This page explains exactly what we do, what we do not do, and where the limits are. If something in a report surprises you, this is the place to understand why.

The short version

  • We open the URL you give us in a headless Chrome browser running in the EU, twice, in two different ways. Monitoring plans add a third visit on a phone.
  • We record every request your page tries to send to ad platforms, but we stop those requests before they leave the browser, so your ad accounts do not receive test data.
  • We grade the Meta, TikTok and OpenAI pixels, each on its own. Other ad platforms we see on the page are listed but not graded yet.
  • We never fill in or submit forms, and we never click buy, cart or checkout buttons.
  • We report what we observed, and what we could not see.

The browser runs

The free check is two separate visits, A and B, each in a fresh browser with no cookies from the other. A whole check usually takes under a minute. Monitoring plans add visit C, on a phone.

Visit A: first visit, no interaction (desktop). We load the page on a desktop-sized screen, wait until it settles and do not touch anything. This shows what your tracking does before a visitor has answered the cookie banner. It is the basis for "fires before consent" findings: an event the pixel sends about the visit counts, a library's own start-up or diagnostics ping does not. We also take a screenshot.

Visit B: arriving from an ad, consent accepted, then button clicks (desktop). We load the page again as if a visitor came from an ad: the URL carries test click IDs for Meta, TikTok, OpenAI and Google (fbclid, ttclid, oppref and gclid), the way an ad click adds them. We accept the cookie banner and watch what your tracking does once a visitor has agreed, and whether your site keeps the click IDs (for Meta in the _fbc cookie, for TikTok in ttclid, for OpenAI in __oppref). Then we click the page's main call-to-action buttons, such as "Contact us" or "Book a call", and record which events each click sends. If a button leads to another page of your site, we check that the click ID survives.

Visit C: on a phone (monitoring plans). Monitoring plans add a visit on a phone-sized screen with touch input, also arriving from an ad. We accept the cookie banner, check the click IDs and click the main buttons of the mobile layout. Because most ad traffic is mobile, we compare which buttons send events on mobile and on desktop, and whether the mobile cookie banner works. In the free check, these checkpoints are shown as "included in monitoring plans".

The test click IDs are clearly fake, and since we stop all requests to ad platforms (see below), they never reach your ad accounts.

We stop tracking data from reaching ad platforms

Checking your tracking should not pollute your ad data. In every visit:

  • Requests that carry tracking data to ad and analytics platforms (Meta, TikTok, OpenAI, Google and others) are recorded and stopped inside our browser. Nothing reaches the platforms.
  • Tracking libraries still load, such as Meta's pixel script, the TikTok and OpenAI pixels and Google Tag Manager, because otherwise there would be nothing to check. Ads and other content from ad platforms are not loaded.
  • Tracking through your own domain. Some sites send events to their own domain first and forward them from their server (server-side tagging, Conversions API tools). We recognize common setups of this kind, stop those requests too, and report them as "tracking through the site's own domain". This recognition is a heuristic: it can miss unusual setups, and we label it as such.

Limitation: if your site forwards events from its own server to an ad platform in a way we do not recognize, we cannot see or stop that server-to-server traffic. When something after a click looks like a tracking event we could not stop, we stop clicking (see below).

What we never do

  • We never type into fields, fill in forms or submit forms. We only note that forms exist.
  • We never click buttons that look like buy, add to cart, checkout, payment or subscribe, in any of the languages we support. We note that they exist and report "Purchase events were not tested".
  • We never click buttons that look destructive (log out, delete, confirm order).
  • While we click buttons, requests that would send data to your server are stopped, not delivered.
  • If, after a click, we see something that looks like a tracking event we could not stop, we stop clicking for the rest of that visit and report "Button testing stopped early".
  • We do not follow links to other websites. Phone, email and WhatsApp links are clicked without opening them, only to see whether a tracking event fires.

Button clicks are observations, not verdicts

The report shows which events fired when we clicked each button, for example "Contact us → Lead" or "+48 600… → nothing". We do not grade this. We do not know which actions you count as a conversion, and real conversions usually happen after a form is submitted, which we never do.

Verifying that your leads and sales actually reach the ad platforms needs data from your ad accounts. That is coming next.

We recognize the cookie consent tools below and click their "accept all" button directly:

  • Cookiebot
  • OneTrust
  • Usercentrics
  • CookieYes
  • Complianz
  • Iubenda
  • Didomi
  • Termly
  • Osano
  • TrustArc
  • Axeptio
  • consentmanager.net
  • Sourcepoint
  • Quantcast Choice / InMobi Choice
  • CookieFirst
  • Borlabs Cookie
  • Klaro
  • Cookie Script
  • Shopify customer privacy banner
  • Consentmo (Shopify app)
  • Framer cookie banner
  • Finsweet Cookie Consent / Consent Pro (Webflow)
  • Squarespace cookie banner
  • Wix cookie banner
  • Google Funding Choices (Privacy & messaging)
  • Cookie Information
  • FastCMP
  • Ketch

If your banner is not on this list, we look for a cookie notice on the page and for a button whose text clearly means "accept" (in several languages), and click it.

If we find a banner but cannot operate it, we say so ("Cookie banner could not be operated automatically") and skip the checks that depend on consent instead of guessing. This can happen separately on desktop and mobile. We also never report "does not fire after consent" as critical unless we actually managed to accept your banner.

Where the browser runs

The browser runs in the EU. The exact country can vary from check to check, and every report shows the country the check ran from. If the browser cannot run from the EU, we retry or fail the check rather than run it from elsewhere.

We run from the EU on purpose: many sites only show a cookie banner, or only hold back tracking, for EU visitors. A visitor in another country may see different behaviour.

The browser identifies itself honestly as an automated checker (its User-Agent includes IsPixelWorking/0.1). See our bot page for details and how to opt out.

How findings are scored

Each pixel we find gets its own grade: the Meta Pixel, the TikTok Pixel and the OpenAI Pixel are scored separately, by the same rules. There is no overall grade for the page, so a good Meta Pixel cannot hide a broken TikTok Pixel. Two pixels of one platform on a page (for example the agency's and the client's) share that platform's grade.

Each finding has a severity. A pixel's score starts at 100 and each of its findings subtracts points according to its severity. Any critical finding caps that pixel's grade, and its score with it. Findings about the whole page, such as a cookie banner we could not operate, take no points.

When there is no grade. A grade says "we watched this tracking work, and this is how well it works". We only give one when we actually saw enough:

  • No Meta, TikTok or OpenAI pixel on the page. There is nothing to grade. Whether that is a problem depends on whether you run ads on these platforms to this page.
  • The visit after consent did not finish (the page was too slow or crashed), so we never saw what the pixels do after a visitor agrees.
  • The cookie banner could not be answered, so after-consent behaviour is unknown.
  • The site blocked our browser.

These reasons apply to every pixel on the page at once. In these cases the report still lists everything we did observe, marked as a partial check. If the visit was only cut short during button clicks, we grade it and say that button coverage was partial.

The score is not a share of conversions kept or lost. It ranks how serious the problems we saw are.

Severity Points off
critical 35
high 15
medium 7
low 2
info 0

Each pixel's score starts at 100. Grades: A ≥ 90, B ≥ 75, C ≥ 60, D ≥ 40, F ≥ 0. Any critical finding caps that pixel's grade at D, and its score at the top of that range. Checks without enough coverage get no grade (see above).

What we check

Meta Pixel

Finding Severity What it means
No Meta Pixel found (meta.pixel_missing) info We did not see a Meta Pixel on this page. If you run Meta ads to it, Meta cannot attribute conversions or optimize delivery for this page.
Meta Pixel fires before cookie consent (meta.fires_before_consent) critical The pixel sent data while the cookie banner was still waiting for an answer. For EU visitors this is a likely privacy problem (we report behaviour, not legal compliance), and it often means the consent setup is not wired to your tags at all.
Meta Pixel does not fire after consent (meta.not_firing_after_consent) critical The pixel script is on the page, but no events were sent after cookies were accepted. Meta receives nothing from this page, so ads optimize blind and conversions go unreported.
Meta blocks this pixel on this website (meta.pixel_blocked) critical The pixel script loads, but Meta refuses to accept its events here: this domain is not in the pixel's traffic permissions in Events Manager, or the pixel itself is restricted. Nothing this page sends reaches Meta, so ads optimize blind and conversions go unreported.
Meta event IDs repeat across visits (meta.event_id_reused) high The same event ID was sent on two separate visits. Meta treats events with the same name and ID as one event, so conversions from different visitors can be merged and dropped. Every event needs its own ID, shared only with its server copy.
Duplicate Meta events (meta.duplicate_pixel) high The same event was sent twice for the same pixel within a second, usually because the pixel is installed twice (for example in site code and in Google Tag Manager). Duplicates inflate reported results and confuse Meta's optimization.
Meta events have no event ID (meta.missing_event_id) high Without an event ID, Meta cannot match browser events with server (Conversions API) events, so the same conversion may be counted twice or dropped.
Click ID from Meta ads is not stored (meta.fbc_not_set) high When a visitor arrives from a Meta ad, the fbclid in the link should be saved in the _fbc cookie. Without it, Meta loses the link between the ad click and the conversion, which lowers match quality and reported results.
Mobile buttons are tracked differently from desktop (meta.mobile_cta_tracking_mismatch) medium A button that sends an event on desktop does not send it on mobile (or the other way round). Most Meta ad traffic is mobile, so conversions may be missing where they matter most.
Click ID saved by your site code in a non-standard format (meta.custom_fbc_format) medium Your site stores the Meta click ID in its own cookie, but not in the format Meta expects (fb.1.
Two different browser IDs (_fbp) (meta.conflicting_fbp) medium Two _fbp cookies with different values exist. The pixel and your server code may send different browser IDs for the same visitor, which weakens matching between browser and server events.
More than one Meta Pixel (meta.multiple_pixels) low Several different pixel IDs are active. This is fine if intended (e.g. agency and client), otherwise data is split.
No advanced matching (meta.no_advanced_matching) low Events carry no hashed customer data, which lowers Meta's event match quality.
Meta server events have no event ID (meta.server_copy_without_event_id) high Your site also sends these events to its own server (for the Conversions API), but without the event ID the browser copy carries. Meta cannot tell that both copies are one conversion, so it may count it twice.
Meta server events carry a different event ID (meta.server_event_id_mismatch) high Your site also sends these events to its own server, but with another event ID than the browser copy. Meta deduplicates on the event name and ID, so the two copies count as two conversions.

TikTok Pixel

Finding Severity What it means
TikTok Pixel fires before cookie consent (tiktok.fires_before_consent) critical The pixel sent data while the cookie banner was still waiting for an answer. For EU visitors this is a likely privacy problem (we report behaviour, not legal compliance), and it often means the consent setup is not wired to your tags at all.
TikTok Pixel does not fire after consent (tiktok.not_firing_after_consent) critical The pixel script is on the page, but no events were sent after cookies were accepted. TikTok receives nothing from this page, so ads optimize blind and conversions go unreported.
TikTok event IDs repeat across visits (tiktok.event_id_reused) high The same event ID was sent on two separate visits. TikTok treats events with the same name and ID as one event, so conversions from different visitors can be merged and dropped. Every event needs its own ID, shared only with its server copy.
Duplicate TikTok events (tiktok.duplicate_pixel) high The same event was sent twice for the same pixel within a second, usually because the pixel is installed twice (for example in site code and in Google Tag Manager). Duplicates inflate reported results and confuse TikTok's optimization.
TikTok events have no event ID (tiktok.missing_event_id) high Without an event ID, TikTok cannot match browser pixel events with server (Events API) events, so the same conversion may be counted twice and campaigns optimize on inflated numbers.
Click ID from TikTok ads is not stored (tiktok.click_id_not_set) high When a visitor arrives from a TikTok ad, the ttclid in the link should reach the pixel's events and stay available for server events. Without it, TikTok loses the link between the ad click and the conversion, which lowers attribution and reported results.
Mobile buttons are tracked differently from desktop (tiktok.mobile_cta_tracking_mismatch) medium A button that sends a TikTok event on desktop does not send it on mobile (or the other way round). Most ad traffic is mobile, so conversions may be missing where they matter most.
More than one TikTok Pixel (tiktok.multiple_pixels) low Several different pixel IDs are active. This is fine if intended (e.g. agency and client), otherwise data is split.
TikTok server events have no event ID (tiktok.server_copy_without_event_id) high Your site also sends these events to its own server (for the Events API), but without the event ID the browser copy carries. TikTok cannot tell that both copies are one conversion, so it may count it twice.
TikTok server events carry a different event ID (tiktok.server_event_id_mismatch) high Your site also sends these events to its own server, but with another event ID than the browser copy. TikTok deduplicates on the event name and ID, so the two copies count as two conversions.

OpenAI Pixel

Finding Severity What it means
OpenAI Pixel fires before cookie consent (openai.fires_before_consent) critical The pixel sent data while the cookie banner was still waiting for an answer. For EU visitors this is a likely privacy problem (we report behaviour, not legal compliance), and it often means the consent setup is not wired to your tags at all.
OpenAI Pixel does not fire after consent (openai.not_firing_after_consent) critical The pixel script is on the page, but no events were sent after cookies were accepted. OpenAI receives nothing from this page, so ads optimize blind and conversions go unreported.
OpenAI event IDs repeat across visits (openai.event_id_reused) high The same event ID was sent on two separate visits. OpenAI treats events with the same name and ID as one event, so conversions from different visitors can be merged and dropped. Every event needs its own ID, shared only with its server copy.
Duplicate OpenAI events (openai.duplicate_pixel) high The same event was sent twice for the same pixel within a second, usually because the pixel is installed twice (for example in site code and in Google Tag Manager). Duplicates inflate reported results and confuse OpenAI's optimization.
OpenAI events have no event ID (openai.missing_event_id) high Without an event ID, OpenAI cannot match browser pixel events with server (Conversions API) events, so the same conversion may be counted twice and campaigns optimize on inflated numbers.
Click ID from OpenAI ads is not stored (openai.click_id_not_set) high When a visitor arrives from a OpenAI ad, the oppref in the link should reach the pixel's events and stay available for server events. Without it, OpenAI loses the link between the ad click and the conversion, which lowers attribution and reported results.
Mobile buttons are tracked differently from desktop (openai.mobile_cta_tracking_mismatch) medium A button that sends a OpenAI event on desktop does not send it on mobile (or the other way round). Most ad traffic is mobile, so conversions may be missing where they matter most.
More than one OpenAI Pixel (openai.multiple_pixels) low Several different pixel IDs are active. This is fine if intended (e.g. agency and client), otherwise data is split.
OpenAI server events have no event ID (openai.server_copy_without_event_id) high Your site also sends these events to its own server (for the Conversions API), but without the event ID the browser copy carries. OpenAI cannot tell that both copies are one conversion, so it may count it twice.
OpenAI server events carry a different event ID (openai.server_event_id_mismatch) high Your site also sends these events to its own server, but with another event ID than the browser copy. OpenAI deduplicates on the event name and ID, so the two copies count as two conversions.

Whole page

These findings describe the page, not one pixel, and take no points.

Finding Severity What it means
No ad pixel found (general.no_pixel) info We did not see a Meta Pixel, TikTok Pixel or OpenAI Pixel on this page. If you run ads to it, the platforms cannot attribute conversions or optimize delivery for this page.
No server-side tracking detected (general.server_side_not_detected) info We saw no sign of server-side tracking (Conversions API, server-side GTM). Server-to-server traffic is invisible from a browser, so this is not proof it is absent.
Server-side tracking detected (general.server_side_detected) info We saw signs of server-side tracking. We cannot see server-to-server traffic, so we cannot tell whether it works.
The site blocked our checker (general.blocked_by_site) n/a The site refused automated access, so we could not check it and show no grade.
Cookie banner could not be operated automatically (general.cmp_not_operable) info We found a cookie banner but could not accept it automatically, so checks that depend on consent were skipped rather than guessed.
Purchase events were not tested (general.purchase_events_not_tested) info We found buy or add-to-cart buttons but never click them on sites that have not been verified, to avoid creating carts or fake conversions.
Button testing stopped early (general.cta_coverage_partial) info After a click we saw a request that looked like a tracking event sent to the site's own server. To avoid feeding test events into ad accounts, we stopped clicking.
Tracking through the site's own domain (general.first_party_tracking_detected) info Requests to the site's own domain looked like tracking events (heuristic). This usually means server-side tagging.

Some findings are marked as possible. These come from heuristics (for example, matching buttons between desktop and mobile by their text) and are more likely to be wrong than the others.

Other ad platforms

We also notice other ad platforms whose tags are on the page: Google Ads / Analytics, LinkedIn Insight Tag, Microsoft Advertising (UET), Reddit Pixel, Pinterest Tag, X (Twitter) Pixel and Snap Pixel. The report lists them as "not checked yet": we do not grade them, and their tracking requests are stopped like all others.

Server-side tracking

Server-to-server traffic (for example the Meta Conversions API or the TikTok Events API sending events from your server) is invisible from a browser. We look for signs of server-side tracking, such as known Conversions API tools, server-side Google Tag Manager, tracking requests to your own domain, or ad click IDs that your site code saves in its own cookies, and report "detected" or "not detected". We never say that your Conversions API works or is broken: we cannot see it. When we see such signs, missing event IDs on a pixel's events count as high severity, because without them the platform cannot deduplicate browser and server events.

Many setups also send a copy of each pixel event to the site's own server, which passes it on to the platform. When we see such a copy in the page's own traffic, we compare it with the pixel event. A copy with the same event ID lets the platform count the conversion once; a copy without an event ID, or with a different one, can make it count twice. Copies we recognize only by the event name are marked as possible. Treat this as a hint: what your server sends on to the platform stays invisible to us.

Known limitations

  • Location. We check from one EU country at one moment. Behaviour can differ by country (cookie banners, geo-redirects, prices, content).
  • Automated browser. We use a real Chrome browser that openly identifies as automated. Some sites or scripts behave differently for automated browsers.
  • A/B tests and personalization. If your site shows different versions to different visitors, we see one of them per run, and the runs may see different versions.
  • Bot protection. Some sites block automated browsers. When that happens we report "The site blocked our checker" and show no grade rather than a misleading one.
  • Server-side tracking is invisible to us, as explained above.
  • One page. We check the URL you give us, plus pages that its buttons lead to on the same site, not your whole website.
  • Timing. We watch each page for a limited time after loading and after each click. Tracking that only fires much later (for example after scrolling or a long delay) may not be seen.
  • Point in time. Websites, tags and consent tools change. A report describes what we saw when the check ran.

What we do not do

  • We do not give legal advice. A finding like "fires before consent" describes technical behaviour, not whether your site complies with GDPR or any other law.
  • We do not issue compliance certificates, and a good grade is not one.
  • We do not install tracking or send events to ad platforms for you. We check; we do not replace your tracking tools.
  • Our findings and grade never depend on which tracking tool or agency you use. When a fix option mentions a tool or service built by our own team, we say so.