Every measurement and mobile measurement partner OpenAI supports for ChatGPT ads, what each connects, and the setup steps published for each one.
On this page
- The short version
- Before you connect any partner
- Web and cross channel measurement partners
- Mobile measurement partners
- How attribution works for mobile
- Reporting and the same 24 to 48 hour lag
- Troubleshooting a mobile measurement partner integration
- What goes wrong when connecting a partner
- Choosing whether you need a partner at all
- A note for UAE and Gulf advertisers
- Quick answers
The short version
OpenAI supports a fixed list of measurement partners for ChatGPT ads, each with its own setup screen but the same two credentials behind it, a Pixel ID and a Conversions API key generated inside Ads Manager. Web and cross channel partners are Fospha, Hightouch, LiveRamp, Singular, Triple Whale and WorkMagic. Mobile app attribution runs through AppsFlyer, Adjust or Branch. OpenAI states it will update the list as more partners are added, so check the source article for the current set before assuming it is unchanged.
Before you connect any partner
Every integration on this page needs the same starting point.
- An active Ads Manager account.
- A Pixel ID and a Conversions API key, generated from the Conversions section of Ads Manager.
- A data source already containing the conversion events you want to send.
- The appropriate permissions inside the partner tool itself.
- A list of the standard or custom events you actually want to send to ChatGPT ads.
Get these five in place before opening a partner's integration screen. Most of the setup steps below assume the Pixel ID and Conversions API key already exist. If you have not created a data source yet, or are unsure which standard event to send, start with the conversion tracking guide rather than beginning inside a partner's dashboard, since the partner integrations below are a routing layer on top of that setup, not a replacement for it.
Web and cross channel measurement partners
| Partner | What you connect | Where the credentials go |
|---|---|---|
| Fospha | Pixel ID and API key, plus your UTM setup | Shared directly with your Fospha representative |
| Hightouch | A destination synced from a data model | Pixel ID and API key entered when adding the ChatGPT Ads (OpenAI) destination |
| LiveRamp | A streaming or batch event feed | A destination account created using your pixel ID and Conversions API key |
| Singular | Partner configuration plus a Singular Link | Pixel ID and API key entered under Partner Configuration |
| Triple Whale | An API key created for Triple Whale | Entered on the Triple Whale side under Data, Integrations, ChatGPT Ads |
| WorkMagic | An API key created for WorkMagic | Pasted into the WorkMagic integration screen after agreeing to its terms |
Fospha
Log in to Ads Manager at ads.openai.com, go to Settings then API Keys, click Create New Key, and share the resulting key with your Fospha representative along with your UTM setup. Fospha's own setup guide covers the remaining configuration on their side.
Hightouch
In Hightouch, open Destinations, click Add destination and select ChatGPT Ads (OpenAI). Authenticate it with your Pixel ID and API key, select the model containing the events you want to send, and create a sync to the OpenAI destination. Configure record matching and map the event properties you want to send. OpenAI specifically flags that the event model needs a truly unique primary key, or Hightouch will not send every event.
LiveRamp
Reach out to your LiveRamp representative to request access to the OpenAI integration. Set up a batch file or streaming event feed to LiveRamp, whichever fits your data, noting that both offline and online conversions can be streamed by API or batched in flat files. Create a destination account for OpenAI using your Pixel ID and Conversions API key, then map your events using LiveRamp's event types documentation. Confirm successful receipt inside Ads Manager once it is running.
Singular
In Singular, go to Partner Configuration and add OpenAI Ads (ChatGPT). Enter your Pixel ID and Conversions API key, map the events you want to send, then create a Singular Link under Manage Links and use it in the relevant campaign.
Triple Whale
In Ads Manager, go to Settings, then General, and create an API key for Triple Whale. In Triple Whale, go to Data, Integrations, find ChatGPT Ads, click Connect and enter the key. Keep applying Triple Whale UTMs to ChatGPT ads campaigns so traffic, orders and customer journeys attribute correctly inside Triple Whale. Triple Whale also offers data enrichment through Sonar Optimize, noted as a separate capability from the core integration.
WorkMagic
In WorkMagic, go to Integration Settings, then Platform Integrations, then the Marketing sub tab, and find the ChatGPT Ads card to start the connection. Review and agree to the terms, then in Ads Manager go to Settings, General, and create an API key for WorkMagic. Paste that key back into the WorkMagic integration screen to finish.
Mobile measurement partners
AppsFlyer, Adjust and Branch are the mobile measurement partners OpenAI currently supports. Before starting, you need an active Ads Manager account, a Pixel ID and Conversions API key, your app or website already configured inside the chosen partner, and the appropriate permissions inside that partner tool.
| Partner | Core steps |
|---|---|
| AppsFlyer | Open Partner Integrations, find ChatGPT Ads (OpenAI), activate it and enter your Pixel ID and API key. Map events. For mobile apps, create an attribution link for the campaign; for websites, configure event forwarding from the AppsFlyer Web SDK to the Conversions API |
| Adjust | In Campaign Lab, add ChatGPT Ads as a partner, select your app, enable data sharing and enter the required credentials. Map events, configure attribution settings and use the resulting click URL in the campaign |
| Branch | Under Configuration, Integrations, Ad partners, select ChatGPT Ads, enable it, and enter your Pixel ID and API key on the Postbacks tile. Map events and enable Send all events, which is required for the Conversions API. Create a Branch Ad Link, use it as the destination URL, and keep Branch's macros in the landing page query parameters field. In Ads Manager, create a matching conversion event for each event you send and link it to the campaign |
How attribution works for mobile
Attribution for these three integrations is click based. For app measurement, use the attribution link generated by the measurement partner inside the corresponding ChatGPT ads campaign, not a generic landing page URL. Attribution windows and event sharing settings are configured inside the measurement partner itself, so what window applies depends on that partner's own documentation, not a setting inside Ads Manager.
Reporting and the same 24 to 48 hour lag
Attributed events from any of these partners appear in the Conversions metric in Ads Manager, and OpenAI asks you to allow 24 to 48 hours for reporting, the same lag that applies to direct Pixel and Conversions API events. There is no separate, faster reporting path for a partner integration.
Troubleshooting a mobile measurement partner integration
If conversions do not appear after connecting AppsFlyer, Adjust or Branch, OpenAI's checklist is short and worth working through in order before contacting support.
- Confirm the partner integration is actually active, not just configured.
- Verify the Pixel ID and Conversions API key match what is shown in Ads Manager.
- Confirm event names are mapped correctly between the partner and Ads Manager.
- Confirm the correct tracking or attribution link is used in the campaign, not a generic app or website URL.
- Confirm the relevant conversion is attached to the campaign.
- Test using a new, eligible ad click rather than checking historical data.
- Allow the full 24 to 48 hours before deciding reporting is broken.
What goes wrong when connecting a partner
- Entering the wrong Conversions API key. Ads Manager can generate more than one key over time as teams change. Confirm the key entered into the partner matches the one currently shown in Ads Manager, not one copied from an old setup document.
- Mapping event names that look right but do not match exactly. A partner's event name has to correspond to what Ads Manager expects for that conversion, and a mismatch here behaves the same way a direct Conversions API mismatch does, the event fires but is not counted.
- Using a generic link instead of the partner's attribution link. This is the most common mobile issue. The campaign has to point at the AppsFlyer, Adjust or Branch attribution link, not a plain app store or website URL, or attribution has nothing to connect to.
- Forgetting to attach the conversion to the campaign. A correctly configured event sitting in the data source but not attached to the specific campaign will not be picked up, whether it arrives through a partner or directly.
- Checking for results too soon. The same 24 to 48 hour reporting lag applies here as anywhere else in Ads Manager. Testing with old traffic instead of a fresh eligible click is a common reason teams conclude an integration is broken when it is only slow to report.
- Assuming a partner replaces the need for OpenAI credentials. Every integration above still runs through your Pixel ID and Conversions API key. If those are wrong or missing, the partner layer cannot fix it.
Choosing whether you need a partner at all
A measurement partner is not a requirement for ChatGPT ads. The OpenAI Pixel and Conversions API work directly without one, and the conversion tracking guide covers that path in full, including the oppref click reference and advanced matching. A partner integration is worth the extra setup when you already run one of these tools for other ad platforms and want ChatGPT ads folded into the same cross channel reporting, or when your app already relies on AppsFlyer, Adjust or Branch for attribution and adding a direct server integration would duplicate work that already exists. If measurement quality still looks weak after connecting a partner, the underlying diagnosis is the same one described in the event quality guide, since a partner integration sends data through the same Pixel ID and Conversions API key that OpenAI scores.
A note for UAE and Gulf advertisers
None of the six web partners or three mobile partners are UAE specific tools, and OpenAI does not publish regional availability differences for any of them, so do not assume one is unavailable for a UAE billed account without checking with the partner directly. If your business already reports Google and Meta performance through one of these platforms for a Gulf entity, adding ChatGPT ads to the same connection is usually the lower effort path, since the account structure, currency handling and reporting cadence are already built. If you are choosing a measurement partner for the first time specifically to support a UAE launch, weigh the setup effort against simply running the Pixel and Conversions API directly, which is enough for most single market UAE advertisers and avoids taking on a new vendor relationship for a first test.
Quick answers
Which measurement partners does ChatGPT ads support?
On the date verified above, OpenAI lists Fospha, Hightouch, LiveRamp, Singular, Triple Whale and WorkMagic as web and cross channel measurement partners, and AppsFlyer, Adjust and Branch as mobile measurement partners.
Do I need a developer to connect a measurement partner?
Most connections need a Pixel ID and a Conversions API key generated inside Ads Manager, then entered into the partner's own integration screen. Mobile app attribution links usually need a mobile engineering resource to implement inside the app.
Is mobile app attribution for ChatGPT ads click based or view based?
Click based. OpenAI states that attribution for AppsFlyer, Adjust and Branch integrations uses the attribution link generated by the measurement partner in the corresponding campaign, and attribution windows are configured inside that partner, not inside Ads Manager.
How long until a measurement partner integration shows conversions?
OpenAI advises allowing 24 to 48 hours for attributed events to appear in the Conversions metric in Ads Manager, the same lag that applies to direct Pixel and Conversions API events.
Do I still need the OpenAI Pixel if I use a measurement partner?
Most partner integrations are built on top of the same Pixel ID and Conversions API key issued in Ads Manager, so the underlying OpenAI measurement setup still needs to exist. The partner adds routing, modelling or cross platform reporting on top of it.
What do I do if conversions are not appearing after connecting a mobile measurement partner?
OpenAI's checklist is to confirm the partner integration is active, verify the Pixel ID and Conversions API key, confirm event names are mapped correctly, confirm the correct tracking link is used in the campaign, confirm the conversion is attached to the campaign, and test with a new eligible ad click before allowing 24 to 48 hours for reporting.
Related
Conversion tracking
How OpenAI measures conversions, what the oppref click reference is, why Pixel plus Conversions API beats either alone, and how to handle WhatsApp and phone sales in the UAE.
Event quality
Every event quality warning OpenAI shows for a Pixel or data source, what each one actually means, and the specific fix for each, including UAE CRM setups.
Reporting and attribution
Every metric in OpenAI Ads Manager, how click and view conversions are counted, the 7, 14 and 30 day windows, reporting lag and how to export daily data.