How do I install the ChatGPT ads pixel?

The short version

The OpenAI Pixel is the JavaScript snippet that sits on your website and reports conversion events back to Ads Manager. It captures the oppref click reference automatically, can detect and hash matching information from your own forms, and works best paired with the Conversions API using the same event ID on both sides. This guide is about the Pixel specifically. For the wider measurement picture, including WhatsApp and phone leads, see our conversion tracking guide.

What the Pixel actually does

Once installed, the Pixel does three things. It fires the conversion events you configure it to send, on the pages where the real action happens. It reads the oppref parameter OpenAI appends to a landing page URL on an ad click, and stores it in a first party cookie so a later conversion on your site can be tied back to that click. And, where automatic advanced matching is enabled, it detects supported customer information already present in recognisable forms on your site, normalises it and hashes it with SHA-256 in the browser before sending it, without raw customer information ever leaving the browser.

Installing it, step by step

1. Create a data source

   In Ads Manager, open the Conversions section and create a data source. This generates your Pixel ID and Conversions API key together.

2. Place the Pixel snippet

   Install it on every page where a measurable action can happen, not only the homepage. This includes product pages, lead forms and confirmation pages.

3. Confirm it initialises with the correct Pixel ID

   Use debug mode while testing, so you can see the Pixel load and fire before you trust any live data.

4. Configure the standard conversion event that matches your goal

   A purchase, a sign up, a lead submission, or whatever the real business action is.

5. Attach the finished conversion event to your campaign

   Before traffic starts. A correctly built event sitting unattached to a campaign will not be picked up.

Installing through a tag manager

Deploying the Pixel through Google Tag Manager is supported, as long as the tag manager loads the Pixel snippet on the correct pages and does not block or reorder the initialisation and event calls. If the tag manager prevents the Pixel from loading reliably, whether because of load order, consent gating or a script conflict, install the snippet directly on the page instead, or move the event to server side measurement through the Conversions API.

Events the Pixel sends, and the shared event ID

OpenAI does not publish a fixed list of standard event names, but its event quality guidance groups conversion activity into three stages, and a healthy setup usually has events firing in more than one.

For resilient measurement, send the same conversion through the Pixel and the Conversions API together. When you do, use the same event ID on both. That is what lets OpenAI deduplicate the two copies of the same action into one counted conversion, instead of reporting it twice. Two teams sending the same event with different event IDs is one of the more common causes of inflated conversion counts we see.

Automatic advanced matching

When a click reference alone is not enough to connect a conversion back to an ad, matching information helps close the gap. Automatic advanced matching (AAM) does this without a separate development project: the Pixel detects supported customer information already entered into recognisable forms on your site, normalises and hashes it with SHA-256 in the browser, and includes it with the conversion event. OpenAI states plainly that raw customer information is not sent to OpenAI through this feature, and no changes to your existing Pixel implementation are required to turn it on. Only send information you are permitted to share, and only after the consent your own privacy notice requires.

Testing the Pixel properly

Do not trust a Pixel until you have walked its full journey once, end to end.

1. Click your own ad, or a link carrying an oppref style parameter, in a private browser window

   Confirm the landing page loads and the Pixel fires on page view.

2. Complete the real action the event is meant to capture

   A lead form, a checkout, a booking. Do not simulate it from a test page that skips the actual flow.

3. Check the click reference survived

   Confirm oppref, or the underlying cookie it set, is still present at the point the conversion event fires. Redirects, language switchers and some consent tools strip it silently.

4. Confirm the event appears in Ads Manager

   Allow 24 to 48 hours, since OpenAI states conversions specifically need that window to appear, even though impressions and clicks can show within minutes.

Why the Pixel shows 0, or seems to be missing events

Pixel versus Conversions API, side by side

Using both, with matching event IDs, is OpenAI's own recommendation for the most complete picture. If your business already uses a partner tool such as Triple Whale or Hightouch, see our measurement partners guide for connecting one of those directly instead of building a custom server integration. For what a poor event quality score actually means and how to fix it, see understanding and improving event quality.

How the Pixel feeds your event quality score

Every data source, meaning every Pixel and Conversions API pairing you set up, gets its own daily event quality assessment in Ads Manager. It is a diagnostic, not a performance prediction: OpenAI states the score and its warnings highlight areas of your setup worth reviewing, and do not by themselves predict campaign performance or guarantee that a conversion will match to an ad. Several of the warnings that show up trace straight back to how the Pixel was installed rather than to the Conversions API side.

• Limited email or customer ID information usually means the Pixel is not picking up matching information from your forms, either because automatic advanced matching is off or because your form fields are not in a recognisable format.
• Ad click information missing or cannot be connected points at oppref being lost somewhere in your redirect chain before the Pixel reads it.
• Limited Pixel and Conversions API activity means OpenAI has not observed enough accepted events from either channel to assess them, which is worth checking early rather than waiting weeks into a campaign to notice nothing is arriving.

The score refreshes daily using seven complete calendar days of data, with time allowed for recent events to arrive, so a change you make today will not clear a warning immediately. Confirm new events are arriving correctly first, then give the assessment window time to catch up.

Common Pixel installation mistakes

• Installing the Pixel only on the homepage. It needs to sit on every page where a measurable action actually happens, including deep pages a homepage visitor never sees.
• Skipping debug mode before trusting live data. A silent failure, wrong Pixel ID, script blocked by a consent tool, event never firing, looks identical to zero conversions from a genuinely quiet campaign unless you have watched it fire once yourself.
• Building the Pixel and the Conversions API with different event ID logic. If one system generates an event ID from an order number and the other from a timestamp, OpenAI cannot match the two copies and will count the same action twice.
• Assuming the Pixel alone is enough for a business that converts off site. A browser pixel can only see what happens in the browser. Anything closed on a call, on WhatsApp, or in person never reaches it without a server side event added afterward.

UAE and Gulf specifics

Two things trip up UAE sites more than the Pixel mechanics themselves. First, many UAE ecommerce and services sites route traffic through a language switcher between Arabic and English versions of a page, and that redirect is exactly the kind of hop that strips oppref if it is not built to preserve query parameters. Test the actual path an Arabic language user takes, not just the English one. Second, UAE service businesses that close leads on WhatsApp or by phone rather than on the website itself will find the Pixel alone captures very little, since the real outcome happens off site, days later. In that case the Pixel installation above is only step one; the outcome still needs to travel back through the Conversions API from your CRM once a lead becomes a sale. That fuller pattern, including preserving the original click timestamp, is covered in our conversion tracking guide.

Related