The OpenAI Measurement Pixel is a browser tool for sending website events to an Ads Manager data source. Install it with the Pixel ID created for your account, then send an event when the action actually happens. A tag that loads successfully does not prove that a purchase, lead or booking event is being received or attributed.
What the Pixel does
The Pixel runs in a visitor’s browser. It can capture the OpenAI click reference oppref from an ad landing URL and retain it for later measurement events. It also supports standard website events such as page views, lead submissions and completed orders. The Pixel does not observe a sale closed later on a phone call or WhatsApp unless that outcome is recorded through another supported integration.
Install and configure it
- In Ads Manager, create or select the right conversion data source and note its Pixel ID.
- Follow OpenAI’s current Measurement Pixel setup. Add the snippet to pages where events occur and initialize it with the correct ID.
- Send an event only when its corresponding action happens. Use an OpenAI standard event whenever it accurately describes the action; check the supported event list and data shape.
- If measurement consent is required, set the Pixel’s consent state before initialization and update it when the user makes a choice. Events blocked before consent are not replayed later.
- Test the full route from ad landing page to form, checkout, booking or confirmation—not just the home page.
Google Tag Manager can deploy the Pixel, but load order, consent rules and other scripts can affect it. A tag manager’s “fired” indicator is not proof that the event request reached OpenAI. Check the browser console and network request or the available event-monitoring tools.
Choose useful events
Measure a real funnel: for example, a product or pricing view, checkout start or lead submission, and a completed order or booking. Do not send a purchase event for a button click or an unqualified page view. OpenAI’s JavaScript Pixel currently does not support the app_installed and app_opened events; those are sent through CAPI.
For a Pakistan ecommerce site, send order_created only when the order is created in the store, and keep its order identifier, value and PKR currency aligned with the records you use for reconciliation. For a service company, a qualified form submission or booked consultation may be a more useful event than a page view. A WhatsApp click is not itself proof that a lead became a customer; record the later outcome through an appropriate server-side process if you need to measure it.
Test and diagnose
Use Pixel debug mode to inspect SDK activity in the browser console. Then complete one test journey and confirm that the correct source receives the intended event. Debug logs and received-event monitoring help check delivery; campaign reports separately decide whether an event qualifies for attribution.
If events are missing, check the Pixel ID and event name, whether the event fires after the real action, consent settings, browser blocking, checkout or embedded-form domains, redirects and page security rules. Confirm that oppref survives redirects. If both browser and server send the same action, use the same Pixel ID, event name and event ID so OpenAI can deduplicate it. Give attributed reporting up to 24–48 hours to appear.
Event quality is a diagnostic based on recent activity; it does not predict campaign performance or guarantee attribution. After a fix, confirm new events are arriving and allow its assessment window to refresh.
Quick answers
Where do I get a Pixel ID?
Create or select a web conversion source in the Conversions area of Ads Manager, then use the Pixel ID shown for that source.
Can I use Google Tag Manager?
Yes, if it loads the Pixel and event calls in the correct order. Verify the request itself; a tag-manager “fired” message alone is not enough.
Do I need CAPI as well?
Not for every setup. CAPI is useful when a server or CRM is the source of truth, including outcomes completed after a website visit. If both channels send one action, configure deduplication.
Why does a test event not appear as a campaign conversion?
Receipt and attribution are different. Check campaign event configuration, source connection, attribution window and matching signals; reporting may also take 24–48 hours.
Will the Pixel record a WhatsApp sale?
It can record a website event such as a WhatsApp click, but it cannot observe a sale completed later in the app. Record that outcome through a supported CRM or server integration if needed.