OpenAI

Set up Mobile Measurement Partner Integrations

Connect a mobile measurement partner to ChatGPT Ads.

Updated: 8 hours ago

ChatGPT Ads supports integrations with select mobile measurement partners. These integrations can help advertisers measure eligible conversions and share event data for reporting and optimization. Available capabilities and setup options vary by partner; refer to the partner’s documentation for current details.

Before you begin

You’ll need:

  • An active Ads Manager account

  • A Pixel ID and Conversions API key from the Conversions section of Ads Manager

  • Your app or website configured in your measurement partner

  • Appropriate permissions in AppsFlyer, Adjust, Branch, or Singular

  • A list of the standard or custom events you want to send to ChatGPT Ads

See OpenAI’s measurement documentation for information about supported events, the JavaScript Pixel, and the Conversions API.

AppsFlyer, Adjust, Branch, and Singular are the mobile measurement partners currently supported for ChatGPT Ads. We’ll update this article as additional mobile measurement partner integrations become available.

Set up AppsFlyer

  1. In AppsFlyer, open Partner Integrations and find ChatGPT Ads (OpenAI).

  2. Activate the integration and enter your ChatGPT Ads Pixel ID and Conversions API key.

  3. Map the events you want to send to ChatGPT Ads.

  4. For mobile apps, create an attribution link and use it in the appropriate ChatGPT Ads campaign. For websites, configure event forwarding from the AppsFlyer Web SDK to the ChatGPT Ads Conversions API.

For complete instructions, see the AppsFlyer setup guide.

Set up Adjust

  1. In Adjust Campaign Lab, add ChatGPT Ads as a partner.

  2. Select your app, enable data sharing, and enter the required ChatGPT Ads credentials.

  3. Map the events and optional data you want to share.

  4. Configure your attribution settings and campaign link, then use the resulting click URL in the appropriate ChatGPT Ads campaign.

For complete instructions, see the Adjust setup guide.

Set up Branch

  1. In Branch, go to Configuration > Integrations > Ad partners and select ChatGPT Ads.

  2. Select Enable, then enter your ChatGPT Ads Pixel ID and Conversions API key on the Postbacks tile.

  3. Map the events you want to send to ChatGPT Ads, then enable Send all events, which is required for the Conversions API.

  4. Create a Branch Ad Link and use it as the destination URL in the appropriate ChatGPT Ads campaign, keeping Branch's macros in the Landing page query parameters field.

  5. In Ads Manager, create a conversion event for each event you're sending and link it to your campaign.

For verification steps and complete instructions, see the Branch setup guide.

Set up Singular

  1. In Singular, go to Partner Configuration and add OpenAI Ads (ChatGPT).

  2. Enter your OpenAI Ads Pixel ID and Conversions API key.

  3. Map the events you want to send to OpenAI Ads.

  4. Under Manage Links, create a Singular Link and use it in the appropriate campaign.

For complete instructions, see the Singular setup guide.

How attribution works

Attribution for these integrations is click-based. For mobile app measurement, use the attribution link generated by your measurement partner in the corresponding ChatGPT Ads campaign. Attribution windows and event-sharing settings are configured in your measurement partner, so refer to its documentation for available options.

Reporting

Attributed events appear in the Conversions metric in Ads Manager. Allow 24–48 hours for reporting. For more information, see Measure Results.

Troubleshooting

If conversions do not appear:

  • Confirm that the partner integration is active.

  • Verify the Pixel ID and Conversions API key.

  • Confirm that event names are mapped correctly.

  • Make sure the correct tracking link is used in the campaign.

  • Confirm that the relevant conversion is attached to the campaign.

  • Test using a new eligible ad click.

  • Allow 24–48 hours for reporting.

For direct server-side measurement, see the Conversions API documentation.

Was this article helpful?