ChatGPT Ads measures post-click actions through the OpenAI Pixel, Conversions API or both. Signal quality depends on far more than having a tag installed: oppref, event IDs, deduplication, advanced matching, consent, attribution windows and QA determine how much confidence you can place in reported conversions.
OpenAI documents a measurement architecture spanning browser-side Pixel, server-side Conversions API, click reference, deduplication, advanced matching and modelled measurement where available. This guide explains how those components work. If you need them implemented, validated or connected with business systems, see our ChatGPT Ads Tracking service.
OpenAI can report a conversion when an event arrives from a data source connected to the ad account, matches a conversion event configured for the campaign, occurs inside the applicable attribution window and can be linked to an eligible ad click using the available measurement signals.
Receiving an event is not the same as attributing it. Configuration, timing, click reference, matching and signal quality still affect whether the action is ultimately reported as a conversion.
Official source: Conversion Measurement · OpenAI Help Center.
The Pixel measures browser-side activity and can capture oppref and retain it in a first-party cookie. CAPI sends events from the server and fits situations where the backend, ecommerce platform or CRM owns the more reliable signal. OpenAI supports using both together.
| Route | Best fit | Critical point |
|---|---|---|
| OpenAI Pixel | Website events and journeys where the browser observes the action. | Firing, consent, storage, navigation and capture of oppref. |
| Conversions API | Server-side, backend, CRM or ecommerce events with first-party signal. | Payload, event mapping, oppref when available and event ID. |
| Pixel + CAPI | When browser and server together provide more resilient measurement. | The same conversion should share the same event ID so it can be deduplicated. |
The choice is not “browser bad / server good”. It depends on where the conversion is confirmed and which signal can be maintained most reliably.
Official source: Conversion Measurement · OpenAI Help Center.
Conversions API supports server-side event delivery. It is especially useful when the conversion is confirmed in a backend, when the server retains information the browser may lose, or when the architecture needs to complement client-side measurement.
CAPI does not automatically replace the Pixel. OpenAI recommends using the two together for more resilient measurement where the use case warrants it.
Official source: Conversion Measurement · OpenAI Help Center.
OpenAI appends oppref to the destination URL. The Pixel can capture it and store it in a first-party cookie so it remains available for later events; when available, advertisers can also include it in Conversions API calls.
That is why redirects, routers, domain changes, navigation and checkout flows matter: losing oppref before conversion removes a direct attribution signal.
Official source: Conversion Measurement · OpenAI Help Center.
When the same conversion is sent through Pixel and CAPI, OpenAI says the same event ID should be used. This allows browser and server payloads to be recognised as two transports for one underlying conversion rather than two separate outcomes.
A different event ID for the same purchase or lead can inflate reporting and contaminate the signal used for optimisation.
Official source: Conversion Measurement · OpenAI Help Center.
Advanced matching can contribute eligible first-party information where direct click information is incomplete. With automatic advanced matching (AAM), the Pixel can detect supported information from recognisable forms and other sources, normalise it and apply SHA-256 in the browser before including it with conversion events.
OpenAI explicitly says raw customer information is not sent through AAM. That does not remove the information, lawful-basis and consent requirements that may apply to the implementation.
Official source: Conversion Measurement · OpenAI Help Center.
Where modelled measurement is available, OpenAI may use aggregated patterns from observed conversions to estimate attribution for certain advertiser-reported events that would otherwise remain unattributed.
Reported totals may therefore include modelled conversions. A difference against analytics or CRM should not automatically be diagnosed as broken tracking.
Official source: Conversion Measurement · OpenAI Help Center.
OpenAI lists several reasons Ads Manager can differ from analytics or other platforms: attribution methods or windows, timestamps, reporting time zones, browser/consent/storage conditions, deduplication behaviour, event configuration and modelled conversions.
We keep UTMs and consistent naming so the sources can be reconciled. The objective is not to force one identical number, but to understand which question each system answers.
Official source: Conversion Measurement · OpenAI Help Center.
Platform documentation ends at event attribution; the business system normally needs more. In ecommerce it is useful to retain purchase, value and an identifier that can be reconciled with the actual order. In B2B, lead origin should be able to continue into CRM if qualification, opportunity or revenue are part of the commercial analysis.
This downstream layer does not change how Pixel or CAPI works. It simply tests whether the advertising conversion represents genuine business value.
OpenAI says conversion data should only be shared where permitted and in compliance with applicable law and its terms. Users should receive clear information and any consent required by law should be obtained before conversion data is sent.
Changes to CMP, checkout, redirects, routers or frontend code can affect an implementation even when the conceptual architecture has not changed. For operational review of those points, our ChatGPT Ads Tracking service covers implementation and QA.
Official source: Conversion measurement · OpenAI Help Center.
What each layer does, how deduplication works and why Ads Manager may not match GA4, ecommerce or CRM exactly.
Not always. Pixel and CAPI can be used separately. Where combining them adds resilience, OpenAI recommends using the same event ID for the same conversion sent by browser and server so it can be deduplicated.
OpenAI’s click reference appended to the landing-page URL. Pixel can preserve it in a first-party cookie and it can also be included with server-side events when available.
Use the same event ID for the same conversion sent through browser and server. This allows OpenAI to treat both payloads as one underlying conversion.
A Pixel capability that can detect supported first-party information, normalise it and apply SHA-256 in the browser before including it with events. OpenAI says raw customer information is not sent through AAM; use still depends on the applicable legal and consent framework.
Where modelled measurement is available, OpenAI may use aggregated observed-conversion patterns to estimate attribution for certain events that would otherwise remain unattributed. Reported totals may include modelled conversions.
Differences can come from attribution windows and methods, timestamps, time zones, consent, storage, deduplication, event configuration or modelled measurement. A discrepancy does not automatically mean one system is wrong.
Yes, and we recommend it. UTMs, analytics, ecommerce and CRM provide an independent commercial view alongside platform attribution.
The implementation must follow applicable law. OpenAI says conversion data should only be shared where permitted, after clear user information has been provided and any legally required consent has been obtained.
Our ChatGPT Ads Tracking service covers architecture, events, oppref, deduplication, QA and reconciliation with analytics, ecommerce or CRM.
What you sell, which markets you work in and what you want to learn from the first pilot. If the scope is not clear yet, we will define it with you.