Which measurement partners connect to ChatGPT ads?

The short version

OpenAI supports a fixed list of measurement partners for ChatGPT ads, each with its own setup screen and credentials issued inside Ads Manager: either an Ads Manager API key, or a Pixel ID and a Conversions API key. The measurement partners are Fospha, Hightouch, INCRMNTAL, LiveRamp, Northbeam, Rockerbox, Triple Whale and WorkMagic. Mobile app attribution runs through Adjust, Airbridge, AppsFlyer, Branch, Kochava, Singular or Tenjin. 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.

Ad clickOpenAI adds a click reference called oppref to the landing page URL

Pixel in the browserFires page and conversion events and carries the click reference

Conversions API from your serverSends the same event with the same event ID, including sales that close later by phone or WhatsApp

Ads ManagerMatches the two by event ID so one sale is counted once, then reports and optimises on it

Before you connect any partner

Every integration on this page needs the same starting point.

• An active Ads Manager account.
• The credentials your integration requires: an Ads Manager API key, or a Pixel ID and a Conversions API key from the Conversions section of Ads Manager. Mobile partners need a Pixel ID from a Web data source and a Conversions API key.
• A data source containing the conversion events you want to send, where the integration sends events.
• The appropriate permissions inside the partner tool itself.
• A list of the standard or custom events you actually want to send to ChatGPT ads, where applicable.

Get these five in place before opening a partner's integration screen. Most of the setup steps below assume those credentials 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

Fospha

Log in to Ads Manager at ads.openai.com with admin access, go to Settings, then General, then API Keys, click Create New Key, and share the key in your Fospha onboarding portal 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, select OpenAI and click Continue. 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.

INCRMNTAL

In Ads Manager, go to Settings, then General, then API Keys, and click Create New Key to create a key for INCRMNTAL. In INCRMNTAL, go to Configuration, then Integrations, click Add Integration, search for OpenAI and click Add. Select Activities to connect marketing activity data, and Reporting as well if you want INCRMNTAL to retrieve spend data. Enter the key, click Test, confirm your campaigns appear in Preview, then click Save.

LiveRamp

Reach out to your LiveRamp representative to request access to the OpenAI integration. If you have not already, set up a conversion event feed to LiveRamp, following LiveRamp's online setup instructions for online conversion events and its offline instructions for offline conversions such as in store purchases. For offline conversions, create a destination account for OpenAI using your Pixel ID and Conversions API key; for online conversions, use the credentials named in the online setup instructions. Map your events and required fields according to the applicable guide, then check Ads Manager to confirm successful receipt.

Northbeam

In Ads Manager, select the ad account you want to connect, go to Settings, then General, then API Keys, and click Create New Key to create a key for Northbeam. In Northbeam, go to Integrations and UTMs, then OpenAI Ads during onboarding, or Settings, then Connections, then OpenAI Ads from the dashboard. Enter the key, confirm the correct ad account and click Connect. Then add Northbeam's required tracking parameter to your campaigns' Landing page query parameters in Ads Manager, following Northbeam's setup guide.

Rockerbox

In Ads Manager, go to Settings, then General, then API Keys, and create a key for Rockerbox. Use it on Rockerbox's integrations connection page to authenticate the OpenAI integration, and give your Rockerbox representative the key, your Pixel ID, Conversion Event ID and Rockerbox Segment ID. Confirm which field identifies each conversion, such as order_id for purchases; OpenAI says this value must match across your pixel events and Rockerbox conversion data so Rockerbox can deduplicate pixel and server side events. Then add Rockerbox's tracking parameters to your campaigns' Landing page query parameters.

Triple Whale

Before connecting, make sure your ChatGPT Ads account has at least one active campaign. In Ads Manager, go to Settings, then General, then API Keys, and create a key for Triple Whale. In Triple Whale, go to Data, Integrations, find ChatGPT Ads, click Connect, enter the key and click Save. Keep applying Triple Whale UTMs to ChatGPT ads campaigns so traffic, orders and customer journeys attribute correctly inside Triple Whale. For data enrichment through Sonar Optimize, OpenAI says to contact Triple Whale about availability and setup.

WorkMagic

In WorkMagic, go to Settings, then Platform Integrations, then Marketing, find the ChatGPT Ads card and click Connect. Review and agree to the terms, then in Ads Manager go to Settings, General, API Keys, and create a key for WorkMagic. Paste that key back into the WorkMagic integration screen and click Confirm.

Mobile measurement partners

OpenAI states: "Adjust, Airbridge, AppsFlyer, Branch, Kochava, Singular, and Tenjin are the mobile measurement partners currently supported for ChatGPT Ads." Before starting, you need an active Ads Manager account, a Pixel ID from a Web data source and a Conversions API key, your app or website already configured inside the chosen partner, the appropriate permissions inside that partner tool, and a list of the events you want to send.

How attribution works for mobile

OpenAI states that "Mobile app attribution through these integrations is click-based." Use the attribution link generated by the measurement partner inside the corresponding ChatGPT ads campaign, not a generic landing page URL. The partner's attribution windows and event sharing settings are configured in the partner's own platform, while "Ads Manager uses its own attribution settings for reporting." So the partner's dashboard and Ads Manager can credit the same install differently, and the reporting windows you pick in Ads Manager are covered in the reporting guide.

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 a mobile measurement partner, OpenAI's checklist is short and worth working through in order before contacting support.

1. Confirm the partner integration is actually active, not just configured.
2. Verify the Pixel ID and Conversions API key match what is shown in Ads Manager.
3. Confirm event names are mapped correctly between the partner and Ads Manager.
4. Confirm the correct tracking or attribution link is used in the campaign, not a generic app or website URL.
5. Confirm the relevant conversion is attached to the campaign.
6. Test using a new, eligible ad click rather than checking historical data.
7. 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 partner's own attribution or tracking 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 on credentials issued in Ads Manager, an API key or a 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 one of the seven supported mobile partners 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 conversion events a partner sends arrive in the same OpenAI data source that event quality assesses.

A note for UAE and Gulf advertisers

None of the eight measurement partners or seven 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, INCRMNTAL, LiveRamp, Northbeam, Rockerbox, Triple Whale and WorkMagic as measurement partners, and Adjust, Airbridge, AppsFlyer, Branch, Kochava, Singular and Tenjin as mobile measurement partners.

Do I need a developer to connect a measurement partner?

Depending on the partner, a connection needs either an Ads Manager API key, created under Settings, then General, then API Keys, or a Pixel ID and Conversions API key from the Conversions section, 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 mobile app attribution through these integrations is click based and uses the attribution link generated by the measurement partner in the corresponding campaign. The partner's attribution windows and event sharing settings are configured in the partner's platform, while Ads Manager uses its own attribution settings for reporting.

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?

It depends on the partner. Fospha, INCRMNTAL, Northbeam, Triple Whale and WorkMagic connect with an Ads Manager API key, while the mobile partners and LiveRamp offline conversions use your Pixel ID and Conversions API key. For conversions to be reported and optimised inside Ads Manager, events still have to reach an OpenAI data source, whether from the Pixel, the Conversions API or a partner that sends them. The partner adds routing, modelling or cross platform reporting on top.

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