Short answer
Create a web data source in Ads Manager under Conversions, add the Pixel code (directly or through your tag manager) behind your consent banner, fire standard events such as lead, sign-up or purchase on real actions, and test with a new ad click. OpenAI's developer documentation has the exact code and event names.
Steps
- Ads Manager > Conversions > Data Sources > Create
- Copy the Pixel ID and code
- Install on every page, loaded after consent where required
- Fire standard events only after confirmed actions
- Keep oppref through redirects; the Pixel stores it in a first-party cookie
- Check Event Quality and test with a fresh click
Common mistakes
- Firing "lead" on page load instead of on submit
- Duplicate tags firing twice
- Stripping query parameters in redirects
- Using custom event names you want to optimise for (custom events can't be optimised)
Questions
Do we also need the Conversions API?
Not required, but OpenAI presents using both as more resilient.
Facts checked against the sources below on 12 October 2026. Platforms change quickly: if something here no longer matches what you see, tell us and we will update it.
