Skip to main content
Sometimes your Upstack Data pixel might not be firing correctly, sending inaccurate event counts, or tracking the wrong values — and pixel errors hurt Meta delivery and campaign performance. This guide walks through our diagnostic process so you can identify and fix the most common pixel issues.

​
Quick diagnosis checklist

Before diving into detailed troubleshooting, check these key areas:
  • Pixel status — Any reported errors in Meta Events Manager? Do events fire in real time in Pixel Helper?
  • Meta Events Manager — Do event counts match what you see in Upstack?
  • Script attributes — Is the pixel using async (correct) or defer (wrong)?
  • Theme and app conflicts — Do custom theme code or third-party apps interfere with the pixel?
  • Third-party tracking — Are other tools creating duplicate events?
  • Domain configuration — Is your pixel correctly set up for subdomains or aliases?

​
Step 1: Use Pixel Helper to view real-time events

What is Pixel Helper? Meta’s official browser extension that shows all Meta pixels firing on your site in real time. Upstack also offers its own Pixel Helper extension for debugging Upstack-specific events.
  1. Install the Pixel Helper browser extension from Meta.
  2. Navigate to your Shopify store or landing page.
  3. Open Pixel Helper (click the icon in your browser toolbar).
  4. Perform an action (page view, add to cart, purchase) on your site.
  5. Check if the event appears in Pixel Helper with the correct event name, value, and Click ID.
What to look for:
  • Events appearing twice = potential duplicate tracking
  • Events appearing once = normal
  • Events not appearing = script loading issue
  • Events with value: $0 = bundle or discount configuration issue
  • Events with missing Click ID = domain or redirect issue

​
Step 2: Compare Pixel Helper to Meta Events Manager

The official source of truth for pixel data is Meta’s Events Manager.
  1. Go to your Meta Business Suite and navigate to Events Manager.
  2. Select your pixel and click the Test Events tab.
  3. Keep this tab open in one window.
  4. In another window, visit your Shopify store while logged into Meta Business Suite.
  5. Perform test actions (page view, add to cart, etc.) and watch Events Manager for incoming events in real time.
What to compare:
  • Event counts: Pixel Helper and Events Manager should show similar counts (within 5–10%).
  • Event timing: Do events appear within seconds of the user action?
  • Event values: Do they match what Pixel Helper shows?
If they don’t match: Your pixel is likely firing, but something is preventing Meta from receiving the full data. This often indicates a consent/privacy setting issue or a redirect problem.

​
Step 3: Check your script tag configuration

The way your pixel script loads affects which events are captured. There’s a critical difference between async and defer. To find your pixel script:
  1. On your Shopify store, right-click anywhere → Inspect (or press F12).
  2. Search for fbq in the page source (Ctrl+F / Cmd+F).
  3. Find your Meta pixel script tag.
Why this matters: If your pixel uses defer instead of async, it won’t load until after the page is fully rendered. If users bounce within the first 2–3 seconds, the pixel never fires, causing major under-counting. How to fix: Contact Upstack support with a screenshot of your script tag. We can update your pixel configuration to use async loading.

​
Step 4: Check for competing tracking tools

If you’re seeing double the events (e.g., Upstack shows 10,000 page views but Facebook shows 20,000), you likely have duplicate pixel tracking. Common culprits:
  • Google Tag Manager (GTM) firing the same pixel
  • Stape (a data layer tool) sending duplicate events
  • Triple Whale Sonar tracking the same conversions
  • Multiple Upstack Data pixels installed
  • Replo or custom page tracking firing the same events
To fix: Disable the duplicate tracking source — usually by keeping Upstack Data as your primary tracking method and removing others. Check GTM for conflicting Meta pixel tags, and in Shopify go to Settings → Customer events to verify only one Upstack pixel is active.

​
Step 5: Audit third-party app configurations

If you’re using apps like Replo (custom pages), Kaching (one-click upsells), or other checkout builders, they may be sending their own conversion data that conflicts with Upstack. Apps to check:
  • Replo — Verify the pixel script is set to async loading, not defer.
  • Kaching — Check if it’s tracking Add to Cart or Purchase separately.
  • Bundle/discount apps — These often send inflated values because they show the full price before discount.
Custom theme code can also interfere — if you’ve modified your theme, check that no custom scripts conflict with the pixel, and temporarily disable suspect apps to see if the error clears.

​
Step 6: Fix bundle and discount tracking issues

The problem: When products are bundled with a discount, your store shows the full price first, then applies the discount at checkout. Your pixel may capture the full (inflated) price, causing Meta to optimize for the wrong bid. Example: A 150bundleshowsas150 bundle shows as 150 in inventory, but costs 80atcheckout.Yourpixelfireswithvalue:80 at checkout. Your pixel fires with value: 150, Facebook optimizes for high AOV, bid errors occur. How to fix:
  1. Find your bundle or discount app settings.
  2. Configure it to send zero-dollar values for discounted bundle items.
  3. Or, ensure your pixel only fires with post-discount prices.

​
Step 7: Check for redirect loops and domain issues

If your Click ID is being lost, or if events aren’t firing on subdomains, you likely have a domain configuration issue. Common problems:
  • Subdomains — If you have www.example.com and example.com, the pixel may not recognize both.
  • Alias domains — Secondary domains may need server-side pixel setup.
  • Redirects — A redirect loop can break Click ID preservation.
How to fix:
  1. Consolidate to one primary domain if possible.
  2. For subdomains, ensure the pixel is hard-coded on all domains.
  3. For redirects, remove redirect loops in your domain configuration.
  4. Contact Upstack support — we can configure server-side pixel tracking if needed.

​
When to escalate to Upstack support

If you’ve worked through the above steps and still have issues, gather this information and contact us:
  1. Screenshot of Pixel Helper showing the event (or lack thereof).
  2. Screenshot of your script tag (from browser Inspector).
  3. List of third-party apps you have installed.
  4. Comparison of Upstack vs. Facebook event counts for the last 24–48 hours.
  5. Your Shopify store domain(s).
  6. Exact event counts — what you expect vs. what you’re seeing.

​
Summary: the diagnostic path

  1. Open Pixel Helper — events firing? → Go to Step 2.
  2. No events? → Check script tag (Step 3), verify app installation, ensure consent is enabled.
  3. Double events? → Check for competing trackers (Step 4) or third-party apps (Step 5).
  4. Wrong values? → Check bundle/discount config (Step 6).
  5. Missing Click ID? → Check domain setup (Step 7).
  6. Still stuck? → Escalate with screenshots and details.
Still stuck? Contact support@upstackdata.com with your Pixel ID and a description of the issue. We typically respond within a few hours.

Verify your Shopify pixel

Full verification walkthrough with Pixel Helper and Events Manager.

No events appear in dashboard

When events never reach Upstack at all.

Duplicate purchases

Fix double-counted conversions in Upstack.

Set up on landing pages or subdomains

Server-side setup for alias domains.