Item logo image for Pixel Validator: Meta, Google, TikTok & X

Pixel Validator: Meta, Google, TikTok & X

ExtensionTools
Item media 4 (screenshot) for Pixel Validator: Meta, Google, TikTok & X
Item media 1 (screenshot) for Pixel Validator: Meta, Google, TikTok & X
Item media 2 (screenshot) for Pixel Validator: Meta, Google, TikTok & X
Item media 3 (screenshot) for Pixel Validator: Meta, Google, TikTok & X
Item media 4 (screenshot) for Pixel Validator: Meta, Google, TikTok & X
Item media 1 (screenshot) for Pixel Validator: Meta, Google, TikTok & X
Item media 1 (screenshot) for Pixel Validator: Meta, Google, TikTok & X
Item media 2 (screenshot) for Pixel Validator: Meta, Google, TikTok & X
Item media 3 (screenshot) for Pixel Validator: Meta, Google, TikTok & X
Item media 4 (screenshot) for Pixel Validator: Meta, Google, TikTok & X

Overview

Read-only validation for ad and analytics pixels across nine platforms. Catch duplicate events, missing values and unhashed PII.

Pixel Validator checks whether your advertising and analytics tags are installed correctly, and tells you exactly what to fix. Most tag debuggers show you what fired. This one judges it. Reload any page and Pixel Validator runs a full rule set over what your tags actually sent, then reports each problem with the reason it matters and the change that fixes it. WHAT IT CATCHES - A snippet pasted twice, so every page view counts double and frequency reporting drifts - A purchase with no value or currency, so return on ad spend never computes - A price sent as ₹1,299.00 where the platform expects 1299.00 — symbols and separators make the value unreadable, and it is dropped - An event named AddtoCart instead of AddToCart — case sensitive, so it is filed as a custom event and cannot be used for value optimisation - A Google Ads conversion value sent with no conversion label, matched to nothing - A TikTok test event code left in production, quietly excluded from reporting - Email addresses and phone numbers sitting readable in event parameters, which are never hashed - Identity fields sent unhashed where the platform expects SHA-256 - A tag that loads so late that visitors who bounce are never counted - A tag present in the page source that never fires at all Supports 9 PLATFORMS All nine are checked on every page. When a platform is not present, it is listed as checked and absent, so you can tell "this site has no TikTok pixel" from "this tool does not look for TikTok". HOW IT READS A timeline across the top plots every request by when it fired, coloured by the worst problem found in it. Two page views 60 milliseconds apart appear as two ticks almost touching — a double fire becomes something you see rather than something you work out. Checks lists every finding grouped by severity, labelled with its platform. Passing checks are shown too, so you can see what was verified rather than only what broke. Events shows every request in order, with its problems listed inline. Expand one for its parameters, identity fields and delivery details. Hashed identity fields render green, readable ones red. Tags groups each account under its platform with timings and event counts. When more than one platform is present, a filter narrows everything to one of them. Copy report puts the whole capture on the clipboard as JSON, ready for a ticket or a handover. Identity hashes are truncated in the export, so a shared report cannot be matched back to a person. READ ONLY BY DESIGN Most pixel debuggers wrap the tag's own global — fbq, ttq, gtag — so they can intercept calls. That is risky. Meta's base code opens with a check that stops the library loading entirely if fbq already exists, and several other tags behave the same way. A debugger built that way can break the thing it was installed to measure. Pixel Validator only reads. It watches the requests your tags send, reads resource timing for the libraries, and scans the page source for snippets. Nothing is patched, queued or rewritten. What it reports is what your visitors actually trigger. PERMISSIONS AND PRIVACY Pixel Validator requests access to a specific list of advertising and analytics endpoints — facebook.com/tr, google-analytics.com, analytics.tiktok.com and the equivalent for each supported platform. It does not request general access to the websites you visit and cannot read their content. No data leaves your browser. There is no analytics, no account, no server and no remote code. Captures are held in session memory for the current tab, discarded when the tab closes, and never written to disk or transmitted anywhere. WHO IT IS FOR Performance marketers, agencies and developers who need to prove tracking is right before a campaign spends against it. Useful during a build, during a migration to a new tag manager, and during the quarterly audit where someone finally asks why the platform's revenue does not match the shop's. Free, with no account and no upgrade prompt.

Details

  • Version
    2.0.3
  • Updated
    August 31, 2026
  • Size
    54.28KiB
  • Languages
    English
  • Developer
    Email
    viewadspend@gmail.com
  • Non-trader
    This developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.

Privacy

Manage extensions and learn how they're being used in your organization
The developer has disclosed that it will not collect or use your data. To learn more, see the developer’s privacy policy.

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes
Google apps