Setting up conversion tracking for ads in ChatGPT

What OpenAI Ads is and when conversion tracking makes sense

According to the OpenAI Help Center, OpenAI Ads is the ad platform for sponsored ads below answers in ChatGPT. Conversion tracking shows what visitors did on your site after the click, because according to the same page OpenAI gives advertisers only aggregated results, not conversations or personal data.

The platform is new and its terms may change. As of October 2026, official OpenAI sources say:

• A US trial started on 9 February 2026, showing ads to users on the Free and Go plans (OpenAI Help Center).
• On 18 August 2026, OpenAI announced expansion to 31 European countries, but names only some of them and does not list the Czech Republic. According to an update of 31 August 2026, self-serve Ads Manager is available in these markets; OpenAI labels it a beta.
• The Ads Manager availability page lists the Czech Republic as available for advertisers based there (Ads Manager availability).
• Personalised ads are not yet available in the EEA or Switzerland; without personalisation, ads follow the current conversation.
• Besides CPM and CPC buying, the announcement of 18 August 2026 lists conversion optimisation. According to the documentation it needs an attached conversion event, so it does not work without tracking.

Who it suits and who it does not

It suits you if you use Ads Manager and want to see orders and leads from ads, or optimise for conversions.

It does not suit you if you do not run ads in ChatGPT. Without a data layer carrying the order value, start with GA4 ecommerce tracking. Google Ads conversions and enhanced conversions are covered by Google Ads conversion tracking. Campaign management is not part of this service.

Pixel, Conversions API or Image Tag?

All three use a Pixel ID which, according to the pixel documentation, is created in the conversions tab in Ads Manager.

Route	Where it runs	When to choose it
Measurement Pixel	in the browser, oaiq function	a standard site or shop, events after clicks or form submissions
Conversions API	on the server	you have a backend; the documentation calls it more reliable than the pixel alone
Image Tag	an image, no JavaScript	a page without JavaScript or a fallback inside <noscript>

The pixel captures the oppref click parameter from the URL itself (pixel documentation) and uses standard events such as order_created for an order and lead_created for a lead.

The Conversions API does not capture oppref; your site must store and send it. Running pixel and server together requires deduplication (Conversions API documentation).

The Image Tag sends one event on page load, with no clicks, forms or user data.

Cookie consent and the OpenAI pixel

The pixel stores two first-party cookies: __oppref with the ad click identifier (30 days) and __obref with a random browser reference (365 days).

In the Czech Republic, Section 89(3) of Act No. 127/2005 Coll. requires prior consent for storing data on a user’s device or accessing it. The only exemptions are technical storage for transmitting a message and storage strictly needed for a service the user explicitly requested. The visitor did not request ad measurement, so under this reading an ad pixel is not exempt. The reading is supported by the Czech data protection authority (ÚOOÚ), which explicitly lists advertising among the purposes covered by consent since 2022, and by the European Data Protection Board: its Guidelines 2/2023 place tracking pixels within Article 5(3) of Directive 2002/58/EC, which Act No. 127/2005 Coll. implements.

The catch: according to the pixel documentation, the pixel assumes consent (true) unless it finds a stored denial, so by default it tracks on page load. Two fixes:

1. Fire the pixel only after consent. The script loads once the cookie banner (CMP) confirms marketing consent.
2. Load it with consent denied. Call oaiq("consent", false) before init and oaiq("consent", true) after consent. Blocked events are not replayed, and false deletes both cookies.

Render the Image Tag only after collecting the required consent, and send __obref to the Conversions API only in line with consent, stopping when it is revoked.

Consent Mode v2 passes consent status to Google tags, according to Google’s documentation. The OpenAI pixel must be tied to the banner choice separately, in code or in Google Tag Manager.

How the setup works

1. Clarifying goals. What counts as a conversion, which route and which cookie banner.
2. Pixel ID. Created in Ads Manager, plus a Conversions API key for server-side tracking.
3. Deployment. The pixel tied to consent, events with value, currency and event_id. With GA4 and Google Tag Manager in place, it uses the same data layer. According to the pixel documentation, a Content Security Policy (rules on where a page may load scripts from) must allow bzrcdn.openai.com and bzr.openai.com.
4. Verification. No OpenAI requests or pixel cookies before consent; after consent, the order is sent once with the right amount.
5. Handover. What is sent where and how to check it.

What you get

• a deployed Measurement Pixel, or the Conversions API or Image Tag where needed,
• standard events with value and currency,
• deduplication through a shared event_id,
• consent-based firing, verified in the browser,
• short documentation of the setup.

What to watch out for

• Amounts in minor currency units. OpenAI expects an integer in the currency’s ISO 4217 minor unit. The ISO 4217 list gives the Czech koruna two decimal places, so 1,234.50 CZK is sent as 123450. Google Ads takes the value as a number with a decimal point (1234.50), so the data layer value needs converting.
• Double counting. According to the pixel documentation, pixel and API events match on Pixel ID, event name and event_id (id in the API); the first one received counts. Without a shared ID, the order counts twice.
• One event for optimisation. According to the documentation, a conversion-optimised campaign needs exactly one standard event, and it cannot be changed after creation.
• Automatic matching. The pixel can detect supported customer information on the page and send it hashed (SHA-256). Check your privacy policy covers it.
• Different numbers. View-through conversions are reported separately and count neither in conversions nor in optimisation. Numbers need not match GA4.

How much OpenAI Ads conversion tracking costs

The price list shows tracking as scope-based, and it explicitly includes OpenAI Ads conversions. The indicative hourly rate in the price list is from 500 CZK/hr. The price depends on the scope and complexity of the project.

It rises with the Conversions API, more events, a missing data layer or a custom cookie banner. A site with GTM, a data layer and a working CMP needs less work.

Describe your setup via the contact form. webrocks replies within 24 hours.

Frequently asked questions

Can businesses in the Czech Republic advertise in ChatGPT?

As of October 2026, the Ads Manager availability page lists the Czech Republic as available for self-serve access, provided the advertising and billed entity is based there. Ads Manager is still in beta.

Do I need cookie consent for the OpenAI pixel?

In the Czech Republic, yes, under this reading of Section 89(3) of Act No. 127/2005 Coll. The pixel stores cookies for ad measurement, which is not technical storage strictly needed for a service the visitor requested.

Pixel or Conversions API?

The pixel suits a standard website, the Conversions API a site with a backend. Both can run together with deduplication.

How do I stop an order being counted twice?

Use the same Pixel ID, event name and event ID in the pixel and the Conversions API, for example the order number.

Is there a Google Tag Manager template?

OpenAI’s documentation lists no official GTM template and describes deployment in code. In GTM, the pixel goes in a custom HTML tag that fires after consent.