Written by
Subscribe
Get fresh updates among the first!
News — 07 Sep 2026
How to Track ChatGPT Ads Conversions with Affise: Complete Setup Guide (2026)
On August 18, OpenAI announced its largest ad expansion to date: ChatGPT Ads is rolling out to 31 European markets, including Germany, France, Spain, Italy, the Netherlands, Poland, and the Nordics. The rollout began the following week, six months after the first US pilot launched in February. With Europe added, ChatGPT Ads now runs in 35 countries.
The numbers behind the expansion explain why OpenAI is moving fast. ChatGPT has around one billion weekly active users, and OpenAI says roughly 20% show commercial intent – planning a trip, comparing software, furnishing a home. Tens of thousands of marketers have run campaigns on the platform, and OpenAI reported ad revenue growth of over 25% in August alone.
One caveat for European advertisers: at launch, campaigns go through OpenAI’s Ads Solutions team, agency partners, and technology partners. Self-service access through Ads Manager will follow later this summer, as it did in the US, where self-serve opened in May after the initial managed pilot.
ChatGPT conversations don’t compress anything. People describe what they’re trying to accomplish, their constraints, and what matters to them in full sentences, often across several turns. When an ad appears in that context, its relevance is higher than any keyword targeting can reach. That’s the pitch, and structurally it holds: the platform knows the user’s actual task, not a proxy.
The platform has matured quickly. In the first six months, OpenAI added conversion optimization on top of CPM and CPC bidding, geo-targeting, custom audiences, and measurement beyond clicks through the OpenAI Pixel and Conversions API. That last part enables proper tracking – more on that below.
The campaign structure will feel familiar to anyone who has run Google or Meta ads: Campaign → Ad group → Ads.
A website pixel alone has blind spots. It misses conversions confirmed after the session – approved orders, qualified leads, deposits – and degrades under cookie restrictions, ad blockers, and browser privacy settings. Since OpenAI optimizes delivery based on visible conversions, every missed one skews optimization.
Affise closes this gap through the OpenAI Conversions API. Conversions registered in Affise are sent server-to-server directly to OpenAI Ads, independent of the user’s browser. Because Affise already forwards conversions to Meta cAPI and Impact the same way, adding OpenAI is a configuration task, not a website rebuild. Send conversions to Affise once, and Affise distributes them to each platform’s API. Structural difference from typical affiliate tracking. OpenAI Ads doesn’t accept redirect tracking links as ad destinations – your ad points straight at your landing page. So the click is registered from the page itself via the Affise WebSDK, not through a redirect.
Your first conversions run in validation mode – Affise verifies everything reaches OpenAI correctly before anything is recorded. Send one real test conversion, confirm it in Ads Manager, and only then scale spend against the signal.
Standard browser-based tracking pixels face significant limitations, such as cookie restrictions, ad blockers, and strict browser privacy settings, which can lead to missed conversion data. Additionally, client-side pixels cannot capture post-session conversions like offline approvals, qualified leads, or delayed deposits. Because OpenAI optimizes ad delivery based on visible conversion signals, any untracked conversion directly degrades campaign optimization. Integrating server-to-server tracking via the OpenAI Conversions API ensures that Affise sends verified conversion data directly to OpenAI, independent of the user’s browser environment. To learn more about how performance tracking and payouts function holistically, read our complete guide on affiliate management systems.
Unlike traditional affiliate networks, OpenAI Ads does not accept redirect tracking links as destination URLs, requiring ads to point directly to your landing page. When a user clicks a ChatGPT ad, OpenAI appends its click identifier directly to the landing page URL using the {oppref} macro. The Affise WebSDK installed on your landing page captures this identifier and stores it within the sub1 parameter. When a user completes a conversion, Affise passes the conversion payload along with the stored sub1 value directly to OpenAI’s conversion endpoint for accurate attribution. If you want to see how businesses leverage these tracking workflows to scale performance, read our client case studies.
First, you should keep your existing OpenAI Pixel active alongside the Conversions API because OpenAI automatically deduplicates events arriving from both sources to ensure complete data accuracy. Second, keep in mind that OpenAI only accepts conversion data timestamped within the last 7 days; if your sales cycle or approval process exceeds this window, you will need to configure your postbacks to fire on initial registration rather than delayed approval. Finally, all initial tracking configurations run in validation mode, requiring you to send a real test conversion and confirm receipt in Ads Manager before scaling ad spend. For additional insights on optimizing marketing channels and strategy, visit our performance marketing knowledge hub.
Stay on top of the competition. Let us keep you updated with news, insights, and more
