PixelProof Docs
By Andy Gaber, Founder · Last updated 2026-08-14
PixelProof monitors whether the tracking that actually drives your Shopify ad spend — Meta Pixel, GA4, and Google Tag Manager containers — is still firing correctly on your storefront and checkout. This page covers everything you need to get a first scan running, the questions merchants ask most often, how PixelProof fits alongside tools you may already run, and what to do when something looks wrong.
Getting Started
- Run the free scan. Go to /meta-monitor and paste your storefront URL. No signup is required for the first scan — it reads the same publicly-rendered page source any visitor's browser already receives, so it sets no cookies and collects no personal data at this stage.
- Read your findings. The scan returns a severity-tagged list: which pixels/tags it found, which fired correctly, and which are missing, misconfigured, or blocked by the Aug 26 2026 Shopify checkout upgrade's removal of the Additional Scripts box.
- Apply the paste-ready fix snippet. Starter and Agency plans include copy-paste snippets for the specific gap your scan found (see the snippets library for the full catalog by platform and event type), plus a one-click re-scan to verify the fix landed.
- Turn on continuous monitoring. A single scan tells you today's state; a subscription runs the same check on a fixed weekly cadence (or continuously via the Chrome extension path) and emails you the moment something breaks again — most tracking drift happens silently after a theme update or app install, not on a predictable schedule.
- Check your plan tier. Pricing and feature boundaries are on /meta-monitor/pricing; the free scan is unlimited and un-gated, monitoring cadence and email alerts require a paid tier.
FAQ
Isn't Meta's Events Manager enough? Events Manager is reactive — you have to open it and notice a drop yourself, often days after ad delivery already degraded. PixelProof is proactive: it scans on a fixed cadence and emails you the moment a pixel, GA4 tag, or GTM container breaks, with the paste-ready fix attached.
We already use Elevar / Northbeam / SegmentStream — do we need this? Different scope, not a replacement. Those are server-side marketing-attribution platforms that model and report on conversion data you already have. PixelProof checks whether the tracking pixels themselves are still firing correctly on your storefront and checkout, including gaps the Aug 26 Shopify change introduces, which attribution platforms don't monitor for.
Our dev handles this manually. A manual check only catches problems when someone remembers to look, typically after a client already asks why ROAS dropped. PixelProof runs the same check automatically every week for less than one hour of a typical contractor's hourly rate.
We don't have Meta Pixel installed yet. The free scan still runs and tells you exactly what's missing, and paid plans include the install snippet plus a verification re-scan once it's live.
Is this GDPR/CCPA compliant? The free storefront scan reads only publicly-rendered page source — no cookies, no personal data collected. Paid accounts store your email and store domain under the privacy policy and standard processing terms; retention is enforced automatically (free-scan data past 30 days is anonymized, not just promised to be).
Integrations
- Shopify — the primary supported platform; the scanner reads storefront and checkout page source directly, no app install required for the free scan.
- Meta Pixel / Conversions API — detects both the browser pixel and, where visible in page source, server-side Conversions API wiring gaps.
- Google Analytics 4 / Google Tag Manager — detects GA4 config tags and GTM container load failures, including containers that load but fail to fire specific event tags.
- PostHog — powers PixelProof's own product analytics and (with visitor consent) session replay; see the cookie policy for exactly what's tracked and how to decline it.
- Rewardful — the affiliate/referral program integration for partners referring PixelProof customers; see /meta-monitor/affiliates.
- Stripe — billing for Starter and Agency plan subscriptions.
Troubleshooting
My scan came back clean but my ads still look off. A clean pixel-firing scan means the tracking mechanism itself is intact — it doesn't rule out attribution modeling issues, ad creative fatigue, or audience/budget problems upstream of tracking. Pair PixelProof with your attribution platform (Elevar, Northbeam, etc.) rather than treating a clean scan as "everything about my ads is fine."
The scan says a tag is missing, but I can see it in my theme code. The scanner checks what actually renders in page source a visitor's browser receives, not your theme editor. A common cause is an app or script that conditionally strips tags based on cookie consent state, geography, or a Shopify app conflict — re-run the scan in an incognito window from a different network to rule out a caching layer serving you a different render than a real visitor gets.
I fixed the snippet but the re-scan still shows the same error. Shopify's CDN and some app-injected scripts can take a few minutes to propagate; wait 5 minutes and re-scan. If it persists past 15 minutes, check whether a Content Security Policy header (some security apps add one) is blocking the exact script URL in the snippet — the browser console's Network tab will show a CSP violation if that's the cause.
I'm not receiving weekly monitoring emails. Check your spam folder first (unsubscribe_token-based one-click unsubscribe links sometimes trigger aggressive spam filters), then confirm your account email matches the one in your Stripe billing profile — monitoring emails send to the account email, not necessarily the card-holder email if they differ.
For anything not covered here, the fastest path is a fresh free scan (it's free and takes under a minute) — most "is this working" questions answer themselves once you see current output. For account or billing issues specifically, use the self-serve options on /meta-monitor/account.