analytics-checkanalytics-check

A deliberately broken install

This page configures the same GA4 property twice, initialises the same Meta pixel twice, and denies analytics consent. Nothing here talks to Google or Meta — the duplicates live in dataLayer and the fbq queue, which is exactly where the checker reads them from. Run the bookmarklet now.

The install

window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-DEM0BR0KEN');
gtag('config', 'G-DEM0BR0KEN');
gtag('consent', 'default', { analytics_storage: 'denied' });

!function(f){if(f.fbq)return;var n=f.fbq=function(){n.queue.push(arguments)};
f._fbq=n;n.queue=[];}(window);
fbq('init', '8891234567890');
fbq('init', '8891234567890');

What you should see

  • GA4 — Measured twice: G-DEM0BR0KEN configured 2x
  • GA4 — No hit recorded yet, blamed on denied Consent Mode
  • Meta Pixel — Initialised twice: 8891234567890 set up 2x
  • Meta Pixel — Nothing sent yet
  • Consent — analytics_storage is denied
  • GTM — No GTM container found
  • Clarity — No Clarity tag found