Quick answer: measuring ChatGPT Ads requires three layers: UTM to separate paid traffic from organic traffic, the Measurement Pixel for website events, and the Conversions API to send more reliable events from the server, including offline events. Ads Manager conversions are based on clicks; conversions following only an impression are a separate metric. KPIs should be assessed from the channel through to the CRM.
A campaign without measurement generates spending, not information. With ChatGPT Ads, this is even more sensitive, because the same domain can bring visits from both ads and organic links in responses, and because attribution rules differ from those of other channels. This guide describes OpenAI’s official tools, how to configure them and which indicators to use when making decisions. The information has been verified as of 5 October 2026 and may change: the platform is evolving rapidly.
What Ads Manager measures and what it does not
Available metrics
Ads Manager reports include impressions, clicks, spend, CTR, average CPC, average CPM and conversions, if measurement is configured. Impressions, clicks and CTR update approximately every 15 minutes; spend may appear with a delay of 7–8 hours. Zero spend in the first few hours therefore does not mean there are no costs.
What is left out
OpenAI states that conversations remain private from advertisers. You will not see the text of conversations in which the ad appeared, or users’ exact questions. Measurement is based on what happens afterwards: visits, website events and events recorded in your systems.
This has a practical consequence: to understand which needs generate results, you need to work on your campaign structure. Separate ad groups for each need and dedicated landing pages make results understandable even without access to conversations.
The tools: three layers of measurement
UTM: separating ads from organic traffic
Static UTM parameters added to destination URLs are retained on click and allow you to analyse ChatGPT Ads traffic in the analytics tools you already use. They are the first and simplest layer, but also the most important for a specific reason: ChatGPT can also bring visits to your website through links in organic responses. Without UTM parameters, ad traffic risks becoming mixed with organic traffic from the same domain, making it impossible to evaluate either.
A consistent convention, agreed before launch and applied to every ad, prevents reports that cannot be compared.
Measurement Pixel
The Measurement Pixel is OpenAI’s tool for measuring website events. It is installed in the head section of the pages where you want to record conversions and automatically handles certain technical details:
- it reads an attribution identifier called oppref from the landing URL and stores it in a first-party cookie for 30 days;
- it creates a browser reference in a second cookie, which lasts for one year;
- it adds the page origin and groups events that occur close together.
The Pixel also offers automatic advanced matching, which detects supported customer information on the website and sends it only after hashing it in the browser. For consent, remember that the Pixel treats it as active by default: in Italy, it must be configured to wait for the user’s acceptance, and events blocked before consent are not recovered.
Conversions API
The Conversions API sends events directly from your server. OpenAI describes it as a more reliable source than the Pixel alone and recommends using it where possible. Some features to be aware of before designing the integration:
- it accepts batches of up to 1.000 events, but if one event in the batch is invalid, the entire batch is rejected;
- each event must have a timestamp within the last 7 days, and no more than 10 minutes in the future;
- the event source can be web, mobile app, offline, point of sale, telephone, email or other;
- unlike the Pixel, it does not capture the oppref identifier itself: this must be saved at the time of the visit and sent with the event;
- in mixed integrations, you can read the browser cookie created by the Pixel and send it with the server event, while respecting consent.
The 7-day limit is crucial for businesses with long sales cycles: a contract signed after a month cannot be sent as an event with the actual signing date.
Events: what to track and how
Mapping the funnel to standard events
OpenAI provides a list of standard events. It is best to use them whenever they describe the action, because they are the only events that can be used as a goal in conversion campaigns. A suggested mapping for the most common cases:
- visits and content: page_viewed, contents_viewed;
- lead generation: lead_created, appointment_scheduled;
- registrations: registration_completed;
- e-commerce: items_added, checkout_started, order_created;
- subscriptions and trials: trial_started, subscription_created.
Custom events are only needed when no standard event describes the action. The monetary value must be sent as an integer in the currency’s smallest unit, together with the currency code: 42,00 euros becomes 4200 with currency EUR.
A campaign with the Conversions objective optimises towards a single standard event, which cannot be changed after creation. Choose it with the available signal in mind: OpenAI warns that events occurring too rarely make results harder to evaluate.
Deduplication between browser and server
If the same conversion arrives from both the Pixel and the Conversions API, the same identifier must be used in both submissions, with the same Pixel ID. OpenAI uses the first event received and ignores subsequent events with the same key. Without this precaution, the same quote request can be counted twice, making the cost per conversion appear better than it really is.
Attribution: clicks, views and windows
Click-through and view-through
Web conversions support two attribution methods:
- click-through: the conversion is attributed to a click on the ad, within the click window configured for the account;
- view-through: when available for the account, the conversion is attributed to an impression of the ad alone, with a fixed window of one day.
If a conversion qualifies for both, the click takes precedence. There is another, more important point: view-through conversions are a separate metric at campaign level. The Conversions total, cost per acquisition, post-click conversion rate, bids, billing and optimisation remain based on clicks.
Why the figures do not match other tools
Conversions in Ads Manager rarely match those in the website analytics tool or CRM. The most common causes are predictable:
- different attribution rules and windows;
- users who refuse consent and are not measured by the Pixel;
- duplicate events that are not handled or, conversely, lost events;
- conversions also attributed to other channels that have interacted with the same customer.
There is no need to force the figures to match. What matters is deciding in advance which tool is authoritative for which decision: Ads Manager for optimisation within the platform, and the CRM or business management system for evaluating the channel.
KPIs: what to look at and in what order
The following model is a suggested approach to reading data from the level closest to the platform to the level closest to the business. Each level explains the next.
- Delivery: impressions, spend, average CPM. These answer the question “is the ad being shown?”.
- Interest: clicks, CTR, average CPC. These answer “is the ad relevant to the people who see it?”.
- Conversion: click-through conversions, landing page conversion rate, cost per conversion. These answer “does the page turn the click into an action?”.
- Value: qualified leads, opportunities, revenue or margin attributed in the CRM. These answer “does the channel bring customers who justify the spend?”.
- Additional signals: view-through conversions, brand searches, direct visits. Treat these as clues, not figures to add to the results.
When an indicator worsens, look for the cause at the previous level. A high cost per lead with a good CTR, for example, indicates a landing page or offer problem, not an ad problem.
An eight-step setup and verification process
The following sequence is a suggested working method, to be completed before activating the campaign.
- Define the UTM convention and apply it to all destination URLs.
- Create a Pixel ID and Conversions API key in the conversions section of Ads Manager.
- Install the Pixel in the head of the relevant pages, with consent set to start disabled until acceptance.
- Map actions to standard events and decide which event will be used for optimisation.
- Integrate the Conversions API for events recorded by the server or CRM, saving oppref at the time of the visit.
- Configure deduplication with a shared identifier for events sent through both channels.
- Verify using test events, using the Pixel’s debug mode and the Conversions API’s validation without saving.
- Document the interpretation rules: which tool is authoritative for which decision, and how often the data is reviewed.
One frequently overlooked check concerns redirects: if a server rule or plugin removes parameters from the URL, oppref and UTM are lost before the Pixel can read them. This is why it is also useful to revisit the guide to the landing page for ChatGPT Ads.
Common measurement errors
The following errors are the most common in setups submitted for review, and almost all can be avoided before launch.
- Ads without UTM. Paid traffic becomes mixed with organic traffic from ChatGPT, and neither can be evaluated.
- Pixel active before consent. The default behaviour is not suitable for the Italian context: it must be set to wait for acceptance.
- The wrong event as the goal. Optimising for page views or downloads that do little to qualify prospects brings high volumes but few customers.
- Double counting. The Pixel and Conversions API send the same conversion without a shared identifier.
- Server events sent late. Events with timestamps older than 7 days are not accepted: CRM exports should be scheduled at least weekly, preferably daily.
- Fragile batches. A single invalid event causes the entire batch to be rejected: it is best to validate events before sending.
- Adding view-through conversions. Adding them to the total inflates results and makes the channel impossible to compare with others.
Frequently asked questions
Is installing the Pixel enough?
It may be enough to get started, but OpenAI recommends the Conversions API where possible because it is more reliable. For conversions that happen outside the website, such as phone calls or contract signings, the Conversions API is the only way to send them.
Do view-through conversions count towards cost per acquisition?
No. They are reported separately and are not included in the Conversions total, cost per acquisition, bids or optimisation, which remain based on clicks.
Can I send a sale closed after two months?
Not with the actual date: the Conversions API accepts events with timestamps within the last 7 days. For long cycles, it is best to optimise for an intermediate event, such as an appointment request, and evaluate sales in the CRM using the UTM parameters saved on the contact.
Why do Ads Manager and the analytics tool give different figures?
Because they use different attribution rules, windows and consent levels. This is normal: what matters is establishing which tool to use for each decision and maintaining that choice over time.
Do conversions from ChatGPT Ads include organic brand mentions?
No. Mentions in organic responses are not ads and do not go through advertising measurement tools. They are measured using other methods, as part of work such as the AI Search Visibility & ChatGPT Ads service.
If you want a measurement setup verified before spending your first euro, talk to Digital Creation about your strategy.
Sources and updates
Updated as of: 5 October 2026
Did you enjoy this article?