
According to PPC Land, ChatGPT Ads has a pixel, Conversions API and platform targeting (iOS, Android, web) in the US, with no information on measurement in the new countries. In Portugal, before access exists, what can already be prepared is the base of any measurement: consistent UTM parameters, clean conversion events, a source report in Analytics and a sheet to record enquiry quality.
What the report says about measurement
PPC Land indicates that a pixel, Conversions API and platform targeting (iOS, Android and web) exist in the US, and that there are brand-suitability pilots with DoubleVerify and IAS, which are tests and may not reach new markets. The report says nothing on measurement in the 26 countries added in October.
What this means: there’s no guarantee that the measurement available in the US is available in Portugal, or on the same terms. Whoever plans to advertise should confirm, at the time, what measurement tools exist for their account and country.
Pixel and Conversions API: in plain language
The pixel is a small piece of code on your site that tells the platform when someone does something (for example submits a form). The Conversions API sends that information directly from your server, without relying on the browser, which can be more reliable when the browser blocks scripts. Many platforms recommend using both together, with deduplication so you don’t count twice.
In any case, the data sent must respect user consent and your site’s privacy policy. Safari 27, for instance, blocks at network level third parties that convert emails into persistent identifiers, showing how fragile identifier-based measurement is.

Measuring a new channel in four layers
- Consistent UTMs on every link
- Conversion events only for real results
- Source report in Analytics
- Enquiry-quality sheet
UTM parameters: the cheap, universal base
UTM parameters add to the page address information about the source (source, medium, campaign, content). With a consistent standard, Analytics can distinguish ChatGPT Ads traffic from other sources, even when the platform’s measurement is limited. Define the standard beforehand: lowercase names, no spaces, the same across all channels.
An example convention: source = “chatgpt”, medium = “paid-ai”, campaign = campaign name, content = ad identifier. Record the convention in a sheet. Months from now, consistency is what lets you compare channels without confusion.
Clean conversion events
Define what a real result is in your business: a quote request sent, a completed purchase, a call longer than a minute, a qualified WhatsApp conversation. Configure events only for that, and distinguish them from secondary events (clicks, scrolls, visits).
If the platform optimises for what you send it, sending weak events trains the algorithm to seek people who do weak things. Fewer, more reliable events is a rule that serves any channel and applies with particular importance on new channels, where the system has little history.

Fewer, more reliable events: the rule that serves any new channel.
A source report in Analytics
Create a report that shows sessions, key events and value by source, with a segment for AI assistants and AI ads. Compare with search, social and email. If ChatGPT’s volume is tiny, record it and move on; if relevant, dig deeper.
Recent studies cited by PPC Land indicate ChatGPT sessions are a small fraction of Google’s traffic but convert at a higher rate in a sample of 100 sites. Only your account can say whether that applies to you, and only clean measurement answers it.
The enquiry-quality sheet
Even with perfect measurement, the platform doesn’t know whether an enquiry was good. Create a sheet where sales records, per enquiry, the source, quality (browser, interested, qualified), whether there was a proposal and whether it closed. At each month’s end, calculate cost per qualified enquiry and per sale, by channel.
It’s the information that decides whether a new channel pays off. And it’s what later allows you to send platforms the qualified enquiries and sales, rather than just forms, if you have a CRM and legal basis.
Privacy and consent
The EU requires consent for many forms of measurement. Make sure your cookie notice is clear, that tags only fire after proper consent and that the privacy policy mentions the tools used. If you use Conversions API with customer data, have a legal basis and minimise what you send.
Google’s Consent Mode v2 is cited as a practical requirement for EEA advertisers by several specialist sources, though it should be confirmed in official documentation. Whatever the channel, compliance is a prerequisite, not an extra.
Frequently asked questions
Can I already use the ChatGPT Ads pixel in Portugal?
The report only confirms a pixel and Conversions API in the US. There’s no information on Portugal. Check in Ads Manager when you have access.
Are UTMs enough to measure?
They give the source of visits, but not the quality of enquiries. Combine with clean conversion events and a quality sheet.
Do I need Conversions API?
Not to start. Begin with UTMs and clean events. Conversions API pays off with volume and when the browser loses signal.