How to Measure ChatGPT Ads: oppref, UTMs, Conversions

Measure ChatGPT Ads with oppref, UTMs, the OpenAI Pixel and Conversions API. Set up events, check attribution, and compare Ads Manager with GA4.

Ecem Bircan
7 min read
Conversion APIs

To measure ChatGPT Ads, tag the landing URL with UTMs, preserve OpenAI's oppref click reference, and send purchase or lead events to OpenAI with the Measurement Pixel, the Conversions API, or both. Then compare attributed conversions in Ads Manager with sessions and outcomes in your own analytics. These reports answer different questions, so their totals will not always match.

OpenAI documents the setup in Conversion Measurement and Measure Results. Here is the practical sequence.

For the campaign plan around this measurement work, see our 2026 ChatGPT Ads holiday playbook. It covers when to launch before Black Friday, how to prepare a product feed, and what to change for Q5.

The short version

  1. Add utm_source=chatgpt and campaign UTMs to the ad's landing URL so your analytics can identify visits from ChatGPT Ads.
  2. Keep the real oppref parameter on the landing URL through redirects and navigation. It connects an eligible ad click to later conversion events.
  3. Create a web data source in OpenAI Ads Manager. Send the completed purchase, lead, or registration event with the Pixel, Conversions API, or both.
  4. Configure the matching conversion event for the campaign and choose its attribution window. An event reaching OpenAI does not automatically become an attributed conversion.
  5. Test one real action, check event receipt, then review the conversion columns in Ads Manager alongside your analytics report.

What is oppref in ChatGPT Ads?

oppref is OpenAI's click reference. OpenAI appends it to the landing URL after an ad click, for example https://example.com/pricing?oppref=<click-reference>. The OpenAI Pixel captures the value and stores it in a first-party __oppref cookie for later events. The cookie requests a 30-day lifetime when measurement consent is granted; browser limits can shorten it. That cookie lifetime is separate from the campaign's attribution window.

If you send events through the Conversions API, capture the original oppref value and include it on the server event when available. The API does not collect it automatically. Preserve it through CDN redirects, URL rewrites, checkout, and form flows. Do not invent a value when one is missing.

oppref and UTMs have different jobs:

SignalWhat it tells youWhere to use it
opprefWhich eligible ChatGPT ad click may be matched to a conversionOpenAI Pixel or Conversions API
utm_source, utm_medium, utm_campaignHow to group landing visits in your analyticsGA4 or your warehouse
Conversion event, such as order_createdWhat the visitor actually didAds Manager and your first-party event pipeline

A UTM-tagged session is useful for traffic analysis. It does not replace an OpenAI conversion event, and an oppref value alone is not a purchase or lead.

Step 1: Tag the landing URL with UTMs

Add campaign parameters to your landing URL, for example:

https://example.com/demo?utm_source=chatgpt&utm_medium=paid&utm_campaign=fall_demo

OpenAI says static UTMs persist on ad clicks. Ads Manager also supports dynamic parameters, including {campaign_id}, {ad_group_id}, {ad_id}, and {ad_account_id}. Use those when you need to join visits to a specific campaign or ad. Check the final URL after any redirect: both your UTMs and OpenAI's added oppref should survive.

Keep a consistent source and medium across campaigns. That makes the ChatGPT Ads traffic segment easy to find in GA4 without grouping it with ordinary referrals from ChatGPT.

Step 2: Send the conversion event

Create a web data source in Ads Manager and get its Pixel ID. Choose the delivery path that matches where the action is recorded:

DeliveryUse it forWhat to check
OpenAI PixelActions recorded in the browserInitialize on relevant pages, respect measurement consent, and fire the event after the action succeeds
Conversions APIConfirmed actions recorded on your serverUse the Pixel ID and API key for the same ad account; include oppref when available
BothBrowser and server copies of the same actionSend the same event name and event ID through both paths so OpenAI can deduplicate them

A server-only setup still needs a Pixel ID as its data source. It does not require installing the browser Pixel. For a purchase, send the standard order_created event; for a submitted lead, use lead_created. OpenAI's conversion tracking guide lists the setup and its supported events specify the event data each action needs.

If you use both paths, give each completed action one stable ID, such as its order ID. Reuse that ID for the Pixel event and the matching server event. A new random ID on each send defeats deduplication. If you provide customer information for matching, follow OpenAI's formatting and hashing guidance and send only data you are permitted to share.

Hardal's OpenAI Ads destination sends supported web events through the Conversions API. The Measurement Pixel guide covers browser setup and consent controls in more detail.

Step 3: Configure attribution in Ads Manager

An accepted event is not necessarily an attributed conversion. In Ads Manager, create a conversion event setting for the same data source and exact event name, then attach it to the campaign. Choose the attribution window before comparing results. OpenAI currently documents 7-, 14-, or 30-day click-through windows and an optional 0- or 1-day view-through window in Measure Results.

For a useful comparison, record the conversion event, window, time zone, and reporting date range beside each dashboard. Ads Manager may count eligible view-through conversions when that window is enabled. GA4 sessions and Ads Manager clicks can also differ because a click does not guarantee a loaded, consented analytics session.

Step 4: Check that measurement works

Run one test journey from an ad landing URL to a completed action:

  1. Confirm the landing URL keeps UTMs and oppref after redirects.
  2. Confirm the Pixel or server integration sends the intended event to the correct data source. Use OpenAI's recent events monitor for receipt, and keep Pixel debug mode on while testing.
  3. Confirm the event name matches the campaign's conversion setting. If both delivery paths are active, confirm they share an event ID.
  4. Check the Conversions, Click-through conversions, and View-through conversions columns in Ads Manager. Check campaign traffic and completed actions in GA4 or your warehouse for the same dates and time zone.

If Ads Manager receives events but reports zero conversions, check the attached conversion event, source, attribution window, and click reference before changing your tags. OpenAI's troubleshooting guide walks through that case. Event receipt proves delivery; campaign reporting depends on attribution.

Keep crawler traffic out of the ad report

GPTBot, OAI-SearchBot, ChatGPT-User, and OAI-AdsBot are different OpenAI crawlers. Their requests to your site are not ad clicks or conversions. Measure crawler activity in server logs or Hardal AI Visibility, and keep it separate from your ChatGPT Ads reports. For the crawler side, see the AI visibility playbook.

Measure ChatGPT Ads with Hardal

You do not need to use Hardal already to get started. Connect your site or app events, add the OpenAI Ads destination, and validate delivery. Keep GA4 and Google Tag Manager running while you compare the results. There is no need to replace your current setup on day one.

The same first-party event flow can also send conversions to Meta, Google, TikTok, and other destinations. That gives your other campaigns better conversion data too, without building a separate pipeline for each channel. Keep your ChatGPT landing page UTMs and oppref, and request a demo if you want help setting it up.