ChatGPT Ads measurement partners: every integration, what it needs and when to use one
The measurement, mobile and CRM integrations for ChatGPT Ads: how each one connects, the data rules they follow, and when a direct setup is enough.
Published Sep 28, 2026 · 14 min read
What is a ChatGPT Ads measurement partner?
A measurement partner is a third-party product that connects to ChatGPT Ads to report on campaigns, to send conversion events on your behalf, or both. OpenAI states that, depending on the partner, integrations may support conversion tracking, attribution, reporting and optimization across web, app and offline activity.
Two terms recur below. The Pixel ID identifies a data source, and oppref is the OpenAI click reference appended to the landing page URL after an ad click. More definitions are in our ChatGPT Ads glossary.
OpenAI also states that available capabilities and setup options vary by partner, and refers advertisers to each partner's documentation for current details. The partner's own guide is the authority for its screens.
Do you need a measurement partner for ChatGPT Ads?
No. OpenAI states that you measure conversions by creating a data source in Ads Manager and sending events with the OpenAI Pixel, the Conversions API, or both. A site with one lead form can install the pixel, send one event and stop there. Our guide to conversion tracking covers that route.
A partner earns its place in three situations:
- Your conversion data already lives in a warehouse, a customer data platform or an attribution tool, and you want to send it from there.
- You advertise a mobile app, where attribution runs through a mobile measurement partner.
- You want ChatGPT Ads reported next to your other channels in a tool your team already uses.
OpenAI's developer documentation describes the Conversions API as a more reliable tracking source than the pixel alone. In our judgment, a partner is one way to get there without writing the integration yourself.
Which measurement partners does OpenAI support?
OpenAI currently lists five measurement partners and four mobile measurement partners, and says it will update both articles as more integrations become available. HubSpot is documented separately.
| Group | Partners | Typical use |
|---|---|---|
| Measurement partners | Fospha, Hightouch, LiveRamp, Triple Whale, WorkMagic | Reporting, attribution, sending web and offline events |
| Mobile measurement partners | AppsFlyer, Adjust, Branch, Singular | App attribution through a tracking link |
| CRM integration | HubSpot | Campaigns, leads and performance inside the CRM |
The "typical use" column is our summary. OpenAI does not rank the partners.
OpenAI adds one note about Triple Whale: it also offers data enrichment through Sonar Optimize. OpenAI's article does not describe that product further, so we do not either.
What do you need before connecting a partner?
OpenAI lists the same basics for both partner types:
- An active Ads Manager account.
- A Pixel ID and a Conversions API key, from the Conversions section of Ads Manager.
- A data source, app or website that holds the conversion events.
- The appropriate permissions in the partner's product.
- A list of the standard or custom events you want to send.
Two different keys appear in the setup steps, and they are easy to confuse.
| Credential | Where it comes from | What it is for |
|---|---|---|
| Pixel ID | Conversions section of Ads Manager | Identifies the data source |
| Conversions API key | Conversions section of Ads Manager | Authenticates server-side event requests |
| Advertiser API key | Settings in Ads Manager | Setup and management requests |
OpenAI's developer documentation states that server-side event requests use a separate Conversions API key, and that both keys belong on your server. Fospha, Triple Whale and WorkMagic ask for an API key created under Settings. Hightouch, LiveRamp and the mobile partners ask for a Pixel ID with a key.
Our recommendation: create a separate key for each partner. If you have not set up the account yet, start with Ads Manager account setup.
How do you connect each measurement partner?
Each partner has a short setup, and the steps below follow OpenAI's help article.
Fospha. Log in to Ads Manager at ads.openai.com, go to Settings, then API Keys, and create a new key. Share the key and your UTM setup with your Fospha representative.
Hightouch. Add the ChatGPT Ads (OpenAI) destination, authenticate with your Pixel ID and API key, choose the model that holds your events and create a sync. Then configure record matching and map the event properties.
LiveRamp. Request access to the OpenAI integration from your LiveRamp representative. Set up a batch file or a streaming event feed to LiveRamp if you do not have one. Create a destination account for OpenAI with your Pixel ID and Conversions API key, map your events, then check Ads Manager to confirm the events arrived. OpenAI states that both offline and online conversions can be streamed through the API or batched in flat files, which matters if sales close in a shop or on the phone.
Triple Whale. In Ads Manager, go to Settings, select General, and create an API key for Triple Whale. In Triple Whale, open Data, then Integrations, find ChatGPT Ads, click Connect and enter the key. OpenAI adds that you should keep applying Triple Whale UTMs to your campaigns, so traffic, orders and customer journeys are attributed inside Triple Whale.
WorkMagic. In WorkMagic, open Integrations Settings, then Platform Integrations, then the Marketing tab. Find the ChatGPT Ads card and click Connect. Review and agree to the terms. Create an API key in Ads Manager under Settings, General, and paste it into WorkMagic.
Fospha and Triple Whale both depend on UTM parameters in your destination URLs. OpenAI states that you can add your own UTM parameters to each creative's destination URL. Our guide to URL parameters explains how.
How does the Hightouch destination work?
It sends rows from a model in your data source to ChatGPT Ads as conversion events. Hightouch's documentation describes the destination as syncing data from any source to OpenAI conversion events.
What Hightouch documents:
- Credentials: two fields, Pixel ID and API key.
- Sync type: Events.
- Supported sync mode: Insert.
- Field mapping: event properties are sent through field mapping.
- Debugging: a live debugger shows the API calls made during each sync run, and sync alerts can go to Slack, PagerDuty, SMS or email.
One requirement appears in both OpenAI's article and Hightouch's documentation: the event model must use a truly unique primary key, so that every event is sent.
Because the only supported mode is Insert, we read this as an append-only stream: a row that has been sent is not corrected by editing it later in the warehouse. That is our interpretation of the documented sync mode, so confirm the behavior with Hightouch before relying on it.
Which mobile measurement partners work with ChatGPT Ads?
AppsFlyer, Adjust, Branch and Singular are the mobile measurement partners OpenAI currently supports. The pattern is the same in each: enable the ChatGPT Ads integration, enter your credentials, map the events, then create a tracking link and use it in the campaign.
| Partner | Where to start | Link to use in the campaign |
|---|---|---|
| AppsFlyer | Partner Integrations, ChatGPT Ads (OpenAI) | An attribution link |
| Adjust | Campaign Lab, add ChatGPT Ads as a partner | The click URL from your campaign link |
| Branch | Configuration, Integrations, Ad partners | A Branch Ad Link as the destination URL |
| Singular | Partner Configuration, OpenAI Ads (ChatGPT) | A Singular Link from Manage Links |
Partner-specific details from OpenAI's article:
- AppsFlyer: for websites, you configure event forwarding from the AppsFlyer Web SDK to the ChatGPT Ads Conversions API instead of using an attribution link.
- Branch: you enter the credentials on the Postbacks tile and enable Send all events, which OpenAI says is required for the Conversions API. You keep Branch's macros in the Landing page query parameters field. You also create a conversion event in Ads Manager for each event you send and link it to the campaign.
OpenAI states that attribution for these integrations is click-based. Attribution windows and event-sharing settings are configured inside the partner, not in Ads Manager.
Three technical points affect app advertisers directly:
- The events
app_installedandapp_openedare available through the Conversions API only. The JavaScript pixel does not support them. - They are sent with
action_sourceset tomobile_app, using the Pixel ID from an existing web data source. - OpenAI states that native mobile SDK setup and mobile data sources are not currently supported. This is why app measurement runs through a partner or your own server.
For matching, the Conversions API accepts android_advertising_id for Android. OpenAI states that IDFA is not supported.
How is the HubSpot integration different?
HubSpot is not only a measurement pipe. According to OpenAI, it lets you create campaigns, add new leads directly to the CRM, trigger follow-up workflows and view performance next to your other ad channels.
It is available to all HubSpot customers wherever ChatGPT Ads are available. You need a Marketing Hub Free, Starter, Professional or Enterprise account, plus permission to connect ad accounts in HubSpot and to manage the Ads Manager account.
To connect, open Settings in HubSpot, select Marketing under Tools, then Ads, then Connect account, and choose ChatGPT Ads. Performance is shown by campaign, ad group or individual ad, including impressions, clicks, contacts, customers and cost.
One permission catches teams out. For ChatGPT Business and Enterprise organizations, a global admin must approve HubSpot's Ads access in the OpenAI Admin Console. It is off by default. Being an Ads account admin or a HubSpot administrator does not make you a global admin. If an account shows as Restricted, that approval is the first thing to check.
What rules does partner-sent data still have to follow?
The same rules as any Conversions API request. A partner changes who sends the event, not what a valid event looks like.
| Rule | What OpenAI documents |
|---|---|
| Batch size | Up to 1,000 events per request. If one event fails, the full batch fails |
| Event time | Within the last 7 days and no more than 10 minutes in the future |
| Amounts | Integers in the currency's minor unit, for example 12999 for $129.99 |
| Hashed identifiers | SHA-256, sent as a lowercase, 64-character hexadecimal string |
Before you map fields, also note:
- Event names. Standard events include
lead_created,order_created,registration_completedandappointment_scheduled. Anything else is sent ascustomwith acustom_event_nameof 1 to 64 characters. - Email normalization. Trim whitespace and convert to lowercase before hashing. OpenAI states that raw email addresses, phone numbers, external IDs and names must not be sent.
- Partner identifier. Integrations that send events on behalf of advertisers include
integration_sourceat the top level of every request. It is 1 to 64 ASCII characters and does not affect authentication.
Two of these rules deserve attention in a warehouse setup. If your warehouse already stores hashed emails, map that column as it is. Hashing a hash produces a value that cannot match. And because event time must fall within the last 7 days, a first sync pointed at years of history will include rows the API does not accept. Both points are our reading of the documented rules.
The consent rule is unchanged too. OpenAI states that you should send conversion data only after giving users clear information about the data you collect and obtaining all necessary consents where the law requires them.
Should you keep the pixel when you use a partner?
Yes, for a website. The pixel captures oppref from the landing page URL and stores it in a first-party cookie, so later conversion events can be connected to the ad click. OpenAI states that, unlike the pixel, the Conversions API does not capture oppref for you. A server-side route has to capture the value and pass it along.
The __oppref cookie expires 30 days after the pixel writes it. OpenAI notes that cookie expiry is separate from conversion attribution windows.
OpenAI recommends using the pixel and the Conversions API together for more resilient measurement. To stop one conversion being counted twice, both copies need:
- The same Pixel ID.
- The same event name.
- The same event ID:
event_idin the pixel andidin the Conversions API. - For custom events, the same
custom_event_name.
OpenAI uses the first event it receives for a matching key and ignores later duplicates. Our suggestion: use the order or lead number as the event ID, because both your website and your warehouse already know it.
The pixel also supports automatic advanced matching, which a server-only route does not give you.
When do partner conversions appear, and why might they show zero?
Allow 24 to 48 hours. OpenAI states that attributed events appear in the Conversions metric in Ads Manager, and that reporting can take that long.
If conversions do not appear, OpenAI's checklist is:
- Confirm the integration is active.
- Verify the Pixel ID and Conversions API key.
- Confirm event names are mapped correctly.
- Make sure the correct tracking link is used in the campaign.
- Confirm the relevant conversion is attached to the campaign.
- Test with a new eligible ad click.
Step five causes the most confusion. OpenAI states that an event can be firing or accepted and still show 0 if it does not match the conversion event configured for the campaign. For standard events, the configured event type must match the event you send. For custom events, the custom event name must match exactly. A matching display name alone is not enough.
Fixing the setup does not repair the past. OpenAI states that historical events from the mismatched setup will not backfill, so check the match before traffic starts.
For a faster check than waiting for reports, the Ads API has a recent-events endpoint that returns a sample of events from roughly the last 15 minutes. Server events appear there with the channel server_to_server, browser events with pixel_sdk.
How do you check the quality of partner-sent events?
Use the event quality assessment on the data source. OpenAI states that event quality refreshes daily using seven complete calendar days, and that each pixel or data source has its own assessment.
Three warnings are especially relevant to partner and warehouse setups:
- Delayed Conversions API events. The check looks for receipt within one hour of the action. In our reading, a sync that runs once a day would not meet it. OpenAI's advice is to send the event promptly and to keep the original time of the action when retrying.
- Missing click information. Preserve
opprefthrough redirects and tracking links, and pass it into the server event. - Limited email or customer ID information. Check that eligible events carry an email or a stable customer identifier, hashed as documented.
OpenAI is explicit that the score does not predict campaign performance or guarantee a match.
Signal quality matters most on conversion campaigns. OpenAI states that custom conversion events are not currently supported for the Conversion optimization objective. If a partner sends your main outcome as a custom event, that campaign type cannot optimize toward it.
Why do partner numbers differ from Ads Manager?
Because they measure differently. OpenAI states that Ads Manager, your analytics provider and other ad platforms may report different conversion totals, and that a difference does not necessarily indicate an error.
The reasons OpenAI lists:
- Different attribution methods or attribution windows.
- Event timestamps, reporting time zones or date boundaries.
- Browser, consent and storage conditions.
- Different deduplication behavior.
- Campaign or conversion-event configuration.
- Modeled conversion reporting, where available.
In Ads Manager, the click-through reporting window can be set to 7, 14 or 30 days, and the view-through window to 0 Day or 1 Day. A partner applies its own windows. Before comparing, align the date range and time zone. For what the reports contain, see reporting and privacy.
Which route should you choose?
Choose by where your conversion data already lives. This section is our judgment, based on what each integration is documented to do.
| Your situation | Route |
|---|---|
| One website, one lead form | The pixel, plus the Conversions API for qualified leads |
| Sales process run in HubSpot | The HubSpot integration |
| Data warehouse or offline sales | Hightouch or LiveRamp |
| A mobile app | One of the four mobile measurement partners |
If you run an online store with an attribution tool, use the partner you already have, provided it is on OpenAI's list.
Whichever route you take, decide the event names and the event ID scheme first, and write them down. If you would rather have this built and tested for you, see our services or contact us.
Frequently asked questions
Which measurement partners does ChatGPT Ads support?
OpenAI currently lists Fospha, Hightouch, LiveRamp, Triple Whale and WorkMagic as measurement partners, and AppsFlyer, Adjust, Branch and Singular as mobile measurement partners. HubSpot has its own integration. OpenAI says it will update its articles as more integrations become available.
Does Hightouch support ChatGPT Ads?
Yes. Hightouch has a ChatGPT Ads (OpenAI) destination. You authenticate with your Pixel ID and API key, select the model that holds your events and create a sync. The supported sync type is Events with the Insert mode, and the event model needs a truly unique primary key.
Do I still need the pixel if I use a partner?
For a website, we recommend keeping it. The pixel captures oppref automatically, and the Conversions API does not. OpenAI recommends using both together, with the same event ID for the same conversion so it is counted once.
Can I measure app installs from ChatGPT Ads?
Yes, server-side. app_installed and app_opened are available through the Conversions API only, with action_source set to mobile_app. The mobile measurement partner integrations connect with your Pixel ID and Conversions API key. Attribution for these integrations is click-based.
How long until partner conversions show in Ads Manager?
OpenAI says to allow 24 to 48 hours for attributed conversions to appear in reporting, and notes that totals may change as recent events are processed.
Can I send offline conversions?
Yes. The Conversions API accepts offline, physical_store and phone_call as values of action_source. Among the partners, OpenAI states that LiveRamp supports both offline and online conversions, streamed or batched in flat files.