ChatGPT Ads · Status at source date: Documentation update
OpenAI expands the set of customer identifiers for conversion matching
OpenAI has expanded the set of matching inputs for the ChatGPT Ads Measurement Pixel and Conversions API, including additional customer and geographic fields.
What changed
The reviewed OpenAI documentation lists additional matching inputs for browser and server measurement, but the two interfaces use different shapes. The Pixel accepts customer information through its initialisation user object, while the Conversions API takes an event-level user object with plural lists for several identifiers. The server documentation also supports Android GAID. Barry Schwartz’s report identifies the matching update as information received from OpenAI.
Normalisation must happen before the required hashing, and the documented rule depends on the field. Geographic values and GAID do not receive the same treatment as fields explicitly named as SHA-256 hashes. More supported inputs do not mean every business should collect every field, and a successfully accepted event does not by itself establish an improvement in attribution accuracy.
Why it matters for advertisers
PMC analysis: this update makes an integration audit more valuable than a promise of better match rates. A field can be present but unusable if its shape, formatting or placement is wrong. Keep a mapping that states where the business gets each permitted value, how it is transformed and which interface receives it. That gives both implementers and reviewers a concrete way to spot mismatches between a browser setup and a server payload.
Also distinguish a measurement change from a business change. If more conversions become attributable after adding identifiers, the reported acquisition cost could improve without the business receiving more orders. Annotating the implementation date and comparing platform totals with independently recorded conversions helps prevent that change from being mistaken for incremental demand. The useful success criterion is a reliable, explainable measurement pipeline, followed by a separate assessment of advertising performance.
What to check next
- Map only the customer data the business is permitted to send, using the Pixel and Conversions API field definitions separately.
- Test field-specific normalisation and hashing with controlled examples, and use the server API’s validation option before relying on new production fields.
- Check event identity and deduplication where browser and server both send the same conversion, then annotate the change before comparing attribution coverage over time.
Sources & contributor credit
- Newsletter coverage · Paid Media Collective newsletter
Original newsletter text, contributor labels and media for this update.
- Source referenced in newsletterOpenAI Conversions API
Linked from the original newsletter. The source publication date has not been independently confirmed.
- Source referenced in newsletterOpenAI Measurement Pixel
Linked from the original newsletter. The source publication date has not been independently confirmed.
- Source referenced in newsletterSearch Engine Roundtable
Linked from the original newsletter. The source publication date has not been independently confirmed.
Source attribution checked
OpenAI authored the technical documentation and supplied the reported update. Barry Schwartz reported it; Juozas Kaziukėnas is credited only for a different story in the same article and is not misassigned to conversion matching.
Attribution evidence and limitations
Read full cached Conversions API article and Measurement Pixel article, including user-data rules and deduplication; read Roundtable body identifying OpenAI email as source of matching news. Current documentation may contain later capabilities, so rewrite stays on the archived identifier expansion.
Retained all original URLs; inspected Roundtable links to the two exact official technical documents. No external private customer data or live integration was accessed.
Viewed web/public/news/newsletter/chatgpt-ads-conversion-matching-identifiers.png. It shows the Conversions API heading, server request example and provisioning text, not the customer-field list claimed by the old alt text. No personal watermark; visual maker unknown.
- Read article including event-level user object, plural list fields, field-specific transformations and validation option.
- Read article including init-scoped user data, normalisation and browser/server deduplication.
- Read report; matching update attributed to OpenAI email, distinct from Juozas Kaziukėnas’s shopping-feed observation.
Attribution checked . This is a review date, not the original publication date.
- Published on this site
- Article updated
This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.
Original newsletter text and archive evidence
OpenAI expands the set of customer identifiers for conversion matching.
OpenAI has expanded the set of matching inputs for the ChatGPT Ads Measurement Pixel and Conversions API, including additional customer and geographic fields. The server API supports lists of hashed identifiers and Android advertising IDs, with field-specific rules for normalisation and hashing rather than one treatment for every value. For you, this means reviewing your integration against the current schema and testing the data you are permitted to send before expecting better attribution coverage.
Source captured . No explicit first-contributor label was provided for this update.
