ChatGPT Ads Not Tracking? A Troubleshooting Checklist for Shopify
If your ChatGPT ad tracking is missing conversions or showing wrong numbers, it is usually one of a few fixable causes. Work through this checklist to find and fix it.
“ChatGPT Ads Not Tracking? A Troubleshooting Checklist for Shopify”
The short version
- "Not tracking" usually means one of three things: no events at all, events but no attributed conversions, or numbers that look too low. Each has a different fix.
- The most common cause is relying on a browser pixel alone, which misses conversions. The fix is server-side tracking through the Conversions API.
- Other frequent culprits: an invalid Conversions API key, missing purchase events, double counting, or the wrong dataset connected.
- Work through the checklist below in order. Most issues are quick to fix.
If your ChatGPT ads look like they are not tracking — conversions missing, numbers that seem too low, or a dashboard stuck at zero — do not panic, and do not turn off the campaign yet. It is almost always one of a small set of fixable causes. Here is how to figure out which one you have and fix it, fastest checks first.
First, pin down what "not tracking" actually means
There are three different problems hiding under "not tracking," and they have different fixes:
- No events at all. Nothing is being recorded. Likely an install or firing problem.
- Events, but no attributed conversions. Traffic is tracked, but sales are not tied back to ChatGPT. Likely an attribution or purchase-event problem.
- Numbers that look too low. Conversions are recorded, but fewer than you know happened. Likely pixel loss, the server-side gap.
Knowing which bucket you are in tells you where to look. Now work through the checklist.
The troubleshooting checklist
- Is your tracking app installed and active? Confirm the app is installed and its pixel is enabled. If it was recently uninstalled or switched off, nothing fires.
- Are events firing at all? Place a test order or trigger a test event and check whether it appears in your tracking dashboard within a few minutes. Nothing showing up points to an install or firing issue.
- Are you sending events server-side, not just a browser pixel? A browser pixel alone misses a large share of events. If a pixel is all you have, that is very likely your problem. You need the Conversions API as well.
- Is your Conversions API key valid? An expired, wrong, or under-scoped key silently rejects your events, usually showing up as
401or403errors. Re-check the key and re-enter it if in doubt. - Are purchase events specifically firing? Page views and product views can work while the purchase event quietly fails. Purchases are what campaigns optimize on, so confirm order events are actually captured.
- Are your events deduplicated? If you send both browser and server events without a shared event ID, you double count, and your numbers become untrustworthy in the other direction.
- Is the right dataset or pixel ID connected? Events sent to the wrong OpenAI dataset will not appear where you are looking. Confirm the ID matches your ad account.
- Did a recent theme change break a manual pixel? If your pixel was pasted into your theme, a theme update or edit can break it. App-embed installs avoid this entirely.
- Have you given it a fair window? If everything is set up correctly but conversions are simply low or zero, it may be attribution timing or an early channel, not a tracking bug. (That specific case is covered in Why are my ChatGPT ads showing 0 conversions?.)
Quick reference: symptom to cause
| What you see | Most likely cause | Fix |
|---|---|---|
| No events at all | App not installed or active, or pixel not firing | Confirm install, then run a test event |
| Events but no purchases | Purchase event not firing | Verify the order event is captured |
| Conversions far below real sales | Browser-pixel-only (pixel loss) | Add server-side Conversions API tracking |
| Events rejected or errors | Invalid or under-scoped API key (401/403) | Re-check and re-enter the key |
| Inflated or doubled numbers | No deduplication | Use a shared event ID across pixel and server |
| Nothing where you expect it | Wrong dataset or pixel ID connected | Point tracking at the correct dataset |
The most common culprit: a browser pixel alone
If you take one thing from this, it is this: most "my numbers are too low" problems are not a bug, they are the limitation of browser-only tracking. Ad blockers, Safari's tracking protection, and shoppers who click on their phone and buy on a laptop all cause the browser pixel to miss real conversions. The fix is server-side tracking through OpenAI's Conversions API, deduplicated against the pixel, which is covered in full in How to track OpenAI Ads conversions on Shopify.
How to confirm your tracking is actually fixed
Do not just assume it worked. Verify:
- Place a test order and confirm the purchase event appears within a few minutes.
- Check for healthy match and delivery quality, with few rejected events.
- Confirm you are not double counting.
- Confirm ChatGPT-attributed orders show up when you expect them.
The shortcut
Most of this checklist is exactly what a good tracking app handles for you. Reach installs the pixel through Shopify's app embed (no theme edits to break), forwards every event server-side through the Conversions API, deduplicates automatically, and shows you delivery status while flagging failed events, so instead of hunting for the problem, you see it. It installs in about 30 seconds.
Stop guessing why your tracking is off. Install Reach on the Shopify App Store to get server-side ChatGPT Ads tracking that installs in 30 seconds and shows you exactly what is being delivered, no code required.
Frequently asked questions
Why are my ChatGPT ads not tracking conversions?
Usually one of: the pixel is not firing, you are relying on a browser pixel with no server-side tracking, your Conversions API key is invalid, the purchase event is not firing, or the wrong dataset is connected.
How do I know if my pixel is firing?
Place a test order or trigger a test event and confirm it appears in your tracking dashboard within a few minutes. If nothing shows up, the pixel is not firing.
Why are my conversions lower than my actual sales?
Almost always pixel loss. A browser pixel misses conversions to ad blockers, tracking protection, and cross-device shopping. Server-side tracking recovers them.
What does a 401 or 403 error mean on my Conversions API?
Your API key is wrong, expired, or does not have the right permissions. Re-check and re-enter it.
Do I need server-side tracking, or is the pixel enough?
You need both. A pixel alone under-counts. Server-side delivery through the Conversions API is what makes the numbers trustworthy.
How long before ChatGPT ad conversions show up?
Events should appear within minutes. If setup is correct but conversions are still zero over days, that is likely an early channel, not a tracking failure.