How to debug Shopify pixel issues: a step-by-step diagnostic

Most Shopify pixel debugging conversations start with the operator already trying their second or third app. The right first step is almost never installing more software. It's running a five-step diagnostic in the browser dev tools.

Step 1: Confirm the pixel script loaded

Open your storefront → open Chrome DevTools → Network tab → filter for fbevents.js (Meta) or gtag (Google) or klaviyo (Klaviyo). Reload the page. If you don't see the script load, the pixel isn't installed on this page. Check theme.liquid or the channel app's installation status.

Step 2: Confirm events are firing

In DevTools Network tab → filter for tr?id= (Meta), collect (GA4), or track (Klaviyo). Click around your site: view a product, add to cart, start checkout. Each action should generate a corresponding network request. If no events fire on user actions, the snippet loaded but the event triggers are broken.

Step 3: Inspect the event payload

Click on one of the event requests. Look at the request URL or payload. For Meta tr?id=, check the cd[* parameters. For GA4 collect, check the ep.* parameters. The customer_email, value, currency, content_ids should be present. If they're missing, your event is firing but with incomplete data.

Step 4: Validate in the platform's own debug tool

Meta Events Manager → Test Events tab → enter your shop URL. Each event you trigger in your browser should appear in the tab in real time. Google Tag Assistant similarly. Klaviyo Analytics → Real-time Activity. If events fire in the Network tab but don't appear in the platform's debug tool, the event_id or pixel ID is wrong.

Step 5: Check for ad-blocker / consent suppression

Some events fail because the browser is blocking them. Open DevTools → Console → look for errors mentioning AdBlock, uBlock, or DuckDuckGo. Then test in incognito with no extensions. If events fire in incognito but not in regular browser, ad blockers are suppressing. Server-side tracking via CAPI bypasses this entirely.

When to stop debugging and run an audit

If you've completed all five steps and can't identify the gap, run a tracking audit. DataGap reads your pixel feed via API and reports the exact configuration issue (missing event, wrong parameters, low match rate) without you needing to debug client-side.