Pixel Scanner Chrome Extension: Detect Tracking in Real-Time

## The Audit That Changed Everything A privacy consultant was evaluating a potential client's website. The client claimed GDPR compliance—they had a cookie banner, after all. The consultant installed a pixel scanner extension, browsed to the homepage, and saw the truth: - Meta Pixel: Firing before consent - Google Analytics: Active immediately - TikTok Pixel: No consent gating - LinkedIn Insight: Tracking page views - 4 more advertising pixels: All pre-consent The "compliant" banner was cosmetic. Seven different advertising networks were tracking every visitor from the first pageload. The consultant turned a 2-hour audit into a €45,000 remediation contract. The right tools reveal what website owners don't want you to see—or don't know themselves. ## Why You Need a Pixel Scanner Browser extensions see what happens in real-time. Unlike remote scanners, they: - Detect dynamic script loading - Monitor events as they fire - Show consent state changes - Reveal delayed tracking initialization If a tracking pixel tries to hide, an extension catches it. ## What the Extension Detects ### Tracking Pixels (20+) | Platform | Detection Signals | |----------|-------------------| | Meta Pixel | `fbq()`, `fbevents.js`, `_fbp` cookie | | Google Ads | `gtag()`, `googleads.g.doubleclick.net` | | Google Analytics | `GA4`, `UA`, `gtm.js` | | TikTok Pixel | `ttq.track()`, analytics.tiktok.com | | LinkedIn Insight | `li_fat_id`, `snap.licdn.com` | | Twitter Pixel | `twq()`, `ads-twitter.com` | | Pinterest Tag | `pintrk()`, `ct.pinterest.com` | | Snapchat Pixel | `snaptr()`, `tr.snapchat.com` | | Criteo | `criteo.com`, `cto_bundle` | | Microsoft UET | `uetq`, `bat.bing.com` | | And more... | Hotjar, Mixpanel, Amplitude, etc. | ### Pre-Consent Violations The extension monitors network activity from page load: 1. Records timestamp when page starts loading 2. Watches for consent banner interaction 3. Flags any tracking before explicit consent 4. Shows violation severity (pixel type, data sent) ### Google Consent Mode v2 Verifies all four required signals: - `ad_storage`: Advertising cookies - `analytics_storage`: Analytics cookies - `ad_user_data`: User data for ads (new in v2) - `ad_personalization`: Personalized advertising (new in v2) Shows default state, update events, and whether signals propagate correctly. ### CMP Detection Identifies which consent management platform a site uses: - Cookiebot - OneTrust - GetCookies - Usercentrics - Iubenda - TrustArc - No CMP detected Useful for competitive research and understanding industry adoption. ## Real-Time Event Monitoring Like Meta Pixel Helper, but for everything: ``` [0.1s] Page load started [0.2s] ⚠️ _fbp cookie set (pre-consent) [0.3s] ⚠️ fbq('track', 'PageView') fired [0.4s] ⚠️ gtag('event', 'page_view') fired [0.8s] Consent banner displayed [2.1s] User clicked "Accept All" [2.2s] gtag('consent', 'update', {...}) [2.3s] Additional tracking initialized ``` This timeline shows exactly when violations occur and how consent changes affect tracking. ## Installation ### Chrome Web Store 1. Visit the [Chrome Web Store](https://chrome.google.com/webstore) 2. Search "GetCookies Pixel Scanner" 3. Click "Add to Chrome" 4. Pin the extension for easy access ### Manual Installation (Developer Mode) 1. Download the extension from [getcookies.co/extension](https://getcookies.co/extension) 2. Open `chrome://extensions` 3. Enable "Developer mode" 4. Click "Load unpacked" 5. Select the extension folder ## Using the Extension ### Quick Scan 1. Navigate to any website 2. Click the extension icon 3. View instant results: - Detected pixels - Cookie inventory - Consent Mode status - Pre-consent violations ### Detailed Analysis Click "Full Report" for: - Complete pixel list with fire events - Cookie categorization - Network request timeline - Consent signal history ### Export Results Save findings as: - JSON (for technical analysis) - PDF (for client reports) - CSV (for spreadsheets) ## Use Cases ### Competitive Analysis Understand how competitors handle consent: - What tracking do they use? - How do they implement consent? - Are they actually compliant? ### Pre-Launch Verification Before going live with website changes: - Verify consent implementation works - Check that script blocking is active - Confirm Consent Mode signals fire correctly ### Vendor Due Diligence When evaluating marketing tools: - Does the vendor's script respect consent? - What cookies does it set? - Does it work with Consent Mode? ### Incident Response When a complaint comes in: - Document current tracking state - Identify violation sources - Capture evidence for remediation ### Training and Education Show stakeholders what tracking looks like: - Demonstrate pre-consent violations - Explain consent signal flow - Visualize third-party data collection ## What Makes This Different from Meta Pixel Helper Meta Pixel Helper shows: - Meta Pixel events only - Event parameters - Pixel ID GetCookies Pixel Scanner shows: - All tracking pixels (20+) - Cookie analysis - Consent Mode status - Pre-consent violations - GDPR compliance scoring - CMP detection It's the difference between checking one thing and auditing everything. ## Privacy-First Design The extension: - Runs entirely locally in your browser - Sends no data to external servers - Doesn't require an account - Doesn't track your browsing - Open-source inspection available We built a privacy tool. It would be ironic to make it a tracking tool. ## Common Findings ### "14 pixels detected, 8 firing pre-consent" **Severity**: Critical Many sites load all marketing pixels immediately. This is the most common violation. Each pixel that fires before consent is a separate GDPR infringement. ### "Consent Mode: Missing ad_user_data" **Severity**: High Sites updated for Consent Mode v1 may not have added the v2 parameters. Without `ad_user_data` and `ad_personalization`, Google can't properly gate advertising features. ### "No CMP detected" **Severity**: High If a site uses cookies but has no consent mechanism, there's no legal basis for tracking EU visitors. Basic but common oversight. ### "CMP detected but pixels fire immediately" **Severity**: Critical Having a banner doesn't mean it works. If tracking loads before the consent check, the banner is cosmetic compliance. ## Frequently Asked Questions ### Does this extension work on all websites? Yes. It monitors network activity and DOM changes on any site you visit. ### Will websites know I'm scanning them? No. The extension is passive monitoring. It doesn't inject anything or change page behavior. ### Can I use this for client audits? Absolutely. Export findings as PDF for professional reports. ### Is the extension free forever? Yes. The extension is completely free with no premium tier. ### What about Firefox/Safari? Currently Chrome only. Firefox version planned for Q2 2025. ## Download Now Get the extension from: - [Chrome Web Store](https://chrome.google.com/webstore) - [Direct download](https://getcookies.co/extension) Every marketer has Meta Pixel Helper. Privacy-conscious teams need something that sees the whole picture.