How to install, use, and troubleshoot ChatGPT Pixel Helper — the OpenAI Ads pixel debugger by Ridoway.
Open the Chrome Web Store and search for "ChatGPT Pixel Helper by Ridoway", or click the Add to Chrome button on the extension landing page.
Click "Add to Chrome" and confirm the permissions. The extension needs access to read page data for detecting the pixel, monitor network requests for beacon inspection, and access browser tabs for state management.
Once installed, the extension icon will appear in your browser toolbar. Click it to open the popup on any page.
Navigate to any website that has the OpenAI Ads pixel installed. The popup will automatically detect pixel activity and display events in real-time.
The popup is divided into several sections, each providing specific information about the pixel implementation on the current page.
Displays the detected Pixel ID from the oaiq.js script tag. If no pixel is found, it will show "Not detected" with guidance on checking the page for pixel installation.
Shows all captured events in reverse chronological order (newest first). Each event displays its name (e.g., "checkout started", "page viewed"), timestamp, and status. Click on an event to expand and view its full parameters and conversion value.
Indicates how many network beacons have been sent to bzr.openai.com. Each beacon represents a successful pixel fire. The count includes both GET and POST beacons.
Shows whether the __oppref cookie is present, along with its value and expiration date. This cookie is used by OpenAI for deduplication and user matching.
If the page has debug mode enabled (via URL parameter ?oaiq_debug=1, __oaiq_debug cookie, or data attribute), the popup will show a debug badge and additional diagnostic information.
Lists any Conversions API (CAPI) calls detected alongside browser pixel events. This helps verify that server-side tracking is working correctly.
The extension captures all standard OpenAI Ads pixel events. Here are the most commonly tracked events:
| Event | Description |
|---|---|
page viewed | Fired when a page loads. The standard page view event. |
checkout started | Fired when a user begins the checkout process. |
items added | Fired when a product is added to the cart. |
purchase | Fired on a successful transaction. Includes order value, currency, and item details. |
lead | Fired when a user submits a lead form (Contact Form 7, WPForms, etc.). |
sign up | Fired when a user completes a registration. |
custom_event | Any custom event name you define in your pixel configuration. |
Debug mode provides additional logging and diagnostic information for troubleshooting pixel issues. The extension detects debug mode through three methods:
Add ?oaiq_debug=1 to any page URL to enable debug mode for that session. The extension will detect this and show additional information in the popup.
Set the __oaiq_debug cookie to "true" to enable debug mode across all pages. The extension checks for this cookie and displays its status.
Add data-oaiq-debug="true" to the pixel script tag for page-specific debug mode. The extension scans for this attribute and reports its presence.
If the extension is not detecting events or showing unexpected results, try these steps:
Verify that the page loads oaiq.js from cdn.openai.com. Check the page source for the pixel script tag. If using Ridoway Pixel plugin for WordPress, confirm the Pixel ID is configured in Settings.
Perform user actions like page navigation, form submission, or add-to-cart. Events only fire when the pixel's oaiq("measure", ...) is called. Check browser console for JavaScript errors that might block the pixel.
The pixel may be configured to send events via CAPI only, not browser beacons. Check your pixel configuration. Also verify that no ad blocker or privacy extension is blocking requests to bzr.openai.com.
If the wrong Pixel ID appears, multiple pixel scripts may be on the page. Check for duplicate installations or third-party plugins that also inject the pixel.
The extension may not have injected the main world script. Try refreshing the page. If the issue persists, reinstall the extension.
ChatGPT Pixel Helper is designed with privacy as a core principle:
The extension runs entirely in your browser. No data is sent to external servers, including Ridoway servers. All pixel inspection happens locally on your machine.
The extension does not store browsing history, persist event data beyond the current browser session, or modify pixel behavior in any way. It is read-only — it observes and reports, but never alters pixel functionality.
The source code is available for review on GitLab. We encourage security researchers and developers to audit the code.