JustOG, Inc.

Verify your OpenAI Ads pixel: watch every oaiq event fire, catch bad payloads, and confirm oppref attribution landed.

ChatGPT Ads Pixel Helper tells you whether your OpenAI Ads pixel is actually working — before you spend money finding out it wasn't. WHAT IT DOES • Get an answer, not a wall of output. A score at the top of the panel says whether this page is healthy, and every point it takes off names the finding that took it — open it up and the arithmetic is right there. A page with no pixel scores nothing at all rather than zero, because zero would be a verdict on something that was never meant to be measured. Keep browsing and you also get a running score for the whole site, so the product page and the thank-you page stop hiding behind one number. • Watch every event fire, live. The panel stays open beside the page, so you can click Add to Cart and see whether items_added actually fired — event name, payload, value, in order. No console, no network tab. • Catch the mistakes that cost money. It checks each event against OpenAI's own spec and tells you what's wrong in plain terms — a purchase value sent as 49.99 when the pixel expects 4999 minor units, an event name borrowed from another ad platform, the wrong data type for the event, a missing event_id that will double-count every conversion you also send from the Conversions API. • Confirm attribution landed. When someone arrives from a ChatGPT ad, the click id has to make it into the __oppref cookie or the conversion is never tied back to the ad. The helper shows you whether it did. • Know when you're being blocked. If an ad blocker or your own Content-Security-Policy is stopping the pixel from loading, events queue up and silently go nowhere. That shows up as an error, not as silence. • Spot a plaintext email before OpenAI does. Identifiers must be SHA-256 hashed. Anything that isn't 64 hex characters is normalised and sent as a raw value — so raw customer data leaves the browser rather than being rejected. That's flagged first, above everything else. And a value that can't be normalised at all is worse in its own way: the identifier is discarded in silence and your matching quietly gets nothing. • Stay correct when the pixel SDK moves. The rules are read from the shipped oaiq.min.js, not from the documentation — the two disagree, and it's the SDK that decides whether an event is kept. Every check is reconciled against the real SDK running in a real browser before release, which is how the fields OpenAI added and the two it retired were caught. • Name your pixels. Running more than one? Give each Pixel ID your own label — "Production", "Client A" — and see it on every site you visit. Stored locally on your machine; no account, nothing uploaded. • Read it in English or 中文, light or dark. The findings are translated, not just the buttons — while event names, fields and payloads stay in English, because those are identifiers in your own code. • Hand the problem to whoever fixes it. One click copies a written report — what's wrong, the exact call that caused it, and the corrected value — ready to paste into a ticket, a message to your developer, or an AI coding assistant. Raw JSON export too. WHY IT EXISTS Since conversion-optimised bidding, the events your pixel sends are the training signal for the auction. A broken pixel doesn't just under-report — it actively degrades delivery. Most implementations are checked once, by hand, and never again. • Free, no account, no sign-in • Nothing it reads ever leaves your browser. It has to read the page to check the pixel, but there is no server to send anything to — findings stay in the tab, in memory, and are gone when you close the browser. • Not affiliated with OpenAI. Built by MiraX.