Installing the PixelProof Chrome extension

The PixelProof Chrome extension is the companion to the storefront scanner. Where the storefront scan can only read the server-rendered HTML of your site, the Chrome extension runs inside a real browser session and sees the same JavaScript-injected pixel wiring your real shoppers see. This guide walks the installation, permission model, and the two scan paths the extension unlocks.

Where to install

Open the PixelProof extension listing on the Chrome Web Store and click "Add to Chrome" (or Add to Edge, or the equivalent in any Chromium-based browser). The extension follows Google's Manifest V3 policies documented on developers.google.com which restricts service workers and background pages to declared use cases, so the review is thorough and the listed permissions are what the extension actually uses.

The permission scope

At install time you'll see three permission prompts:

activeTab: the extension can read the current tab you're on when you click its icon. It does not run in the background on every site.

scripting: the extension can inject a scan script into the active tab, again only when triggered.

storage: the extension keeps your API key locally so you don't paste it every time.

There is no host_permissions on <all_urls>. That means the extension is dormant on every site until you actively click it, and the exact site you're on when you click is the only site it reads. Google's extension user data policy on developers.google.com requires the disclosure and prohibits selling scanned data, and the FTC's guidance on data brokers and browser extensions on ftc.gov adds the US enforcement lens on top of Google's own policy.

Step 1: Pin the extension

Click the extensions puzzle icon in the Chrome toolbar and pin PixelProof. Pinning is not required, but on a full-day session you'll click the icon multiple times per store audit and unpinned extensions add a click.

Step 2: Sign in

Click the pinned icon and paste the API key from your PixelProof account. The API-key section in your account (see the PixelProof API access help article) shows the key and a "copy" button. The key is stored locally in Chrome's chrome.storage.local, not synced to Google or exfiltrated anywhere.

Step 3: Scan a storefront

Navigate to your storefront (or a competitor's, or a client's). Click the extension icon and pick "Scan this store." The scanner walks the same detection rules as the server-side scan (see understanding your PixelProof scan results) plus a set of "in-browser only" checks that require JavaScript execution: Shopify Web Pixel Manager confirmation, Meta CAPI browser-side pairing verification, GTM tag firing confirmation.

Step 4: Scan a checkout (Shopify Plus only)

The extension can also scan checkout.liquid on Shopify Plus stores where you own the checkout theme. Add a test item to cart, proceed to checkout, and click the extension icon before you submit the order. The scanner will inspect the checkout DOM for the exact pixel emit lines. Shopify's Checkout Extensibility documentation on shopify.dev covers what the new checkout allows and disallows in terms of pixel scripts.

Why the extension is the definitive scan for Hydrogen

Shopify Hydrogen (headless React) storefronts render zero pixel wiring in server HTML: the entire tag payload is hydrated client-side by React after page load. A storefront-only scan can only surface a warning-severity headless-or-hydrated-storefront finding, it cannot confirm which pixels actually fire. The Chrome extension is the answer. Full context in the headless Shopify Hydrogen storefronts article.

Was this helpful?

Yes / No

Related articles

Understanding your PixelProof scan results

Headless Shopify Hydrogen storefronts and PixelProof

Meta CAPI setup, step by step

PixelProof product home

FAQ

Does the extension work in Safari or Firefox? Not yet. Manifest V3 is Chromium-only for now; a Safari Web Extension port is on the roadmap.

Does the extension read my shopper PII? No. The scan reads only page metadata, DOM structure, and network requests to pixel endpoints. Shopper email, address, and card data are never inspected. Full disclosure follows the Chrome extension user data policy on developer.chrome.com.

Do I need to rescan after every theme change? Yes, or at least run a fresh scan after any theme deploy that touches the header, checkout, or thank-you templates.

Still stuck? Email support@digitalempireholdings.com or support@digitalempireholdings.com.

FAQ

Does the extension work in Safari or Firefox?

Not yet. Manifest V3 is Chromium-only for now; a Safari Web Extension port is on the roadmap.

Does the extension read my shopper PII?

No. The scan reads only page metadata, DOM structure, and network requests to pixel endpoints. Shopper email, address, and card data are never inspected. Full disclosure follows the [Chrome extension user data policy on developer.chrome.com](https://developer.chrome.com/docs/webstore/user-data-faq).

Do I need to rescan after every theme change?

Yes, or at least run a fresh scan after any theme deploy that touches the header, checkout, or thank-you templates.