Open AI Ad Platform Metrics Vs GA4

[u/Chiefer2]

Looking to hear from others currently running campaigns on ChatGPT.

We have, in recent weeks, gained access to OpenAI Ads. Our company has put a small amount of dollars towards testing the platform.

Following roughly the same sentiment we would follow on other platforms, we are running with Page Viewed conversions as our Conversion goal (just for now as we see the quality of traffic being sent over).

However, only 70.2% of clicks get recorded as a Page Viewed conversion. I figure this would be misclicks or people who couldn't load the page and gave up - fine.

The more concerning part to me is the variance of Page Viewed Conversions to GA4 metrics between each ad group we are testing (all one campaign with same tracking parameters).

Ad Group A has GA4 reporting at 97.2% of what Open AI is reporting for Conversions (Awesome!), Ad Group B shows 63.5% representation, and Ad Group C only records at 39%.

I have QA'd all ads using a Pixel Helper to ensure that the Page Viewed conversion is firing, and it is indeed correctly attributing on my tests.

Is anyone else experiencing such discrepancies? Let me know your experience so far.

[u/goodgoaj]

This is normal, there is no ad platform that exists today where ad platform clicks = GA sessions. They are 2 completely different metrics.

Is ChatGPT Ads more problematic for a click to land rate vs a Google / Meta? Not really.

[u/quiethush78]

that 39% number on Ad Group C is rough. are those clicks coming from mobile-heavy sessions? webview environments are notorious for dropping tracking pixels before the page fully loads, and the ratio differences between ad groups could just be device mix differences

[u/Ishan_GS]

Yes, we're running it for three clients at GrowthSpree, a B2B SaaS marketing agency, and we're seeing a meaningful dashboard-to-GA mismatch too. So you're not alone, and it's not your tagging, especially given your Pixel Helper checks pass.

I'd focus on your ad group variance rather than the overall 70%, since identical tracking producing 97%, 63%, and 39% points to something differing between the groups rather than a platform-wide reporting gap. Worth checking whether the ad groups send traffic to different URLs or through any redirect, whether device or geo mix differs meaningfully between them, and whether page load times differ by destination. A slow or redirect-heavy page loses far more sessions before the tag fires, which produces exactly that spread. Honestly though, the platform is early, and reporting is thin, so I'd treat its numbers as directional and use GA as your source of truth for decisions until it matures.

[u/ksz2018]

The 70% and the ad group spread are two different findings and only the second one is worth your afternoon.

Clicks to page views never reconciles on any platform. A click is counted at the ad, a page view is counted on your site, and everything in between eats the gap: people who back out before the script runs, prefetch, blockers, a phone that dropped signal on the tap. 70% is unremarkable and it will not move much.

The spread is the real thing, because you have controlled for the parameters and not for the destination. Check whether all three ad groups land on exactly the same URL. A redirect, a country or language router, or an app generated landing page in front of one of them is enough on its own. The two systems are not gated on the same conditions: the platform is counting its own pixel firing on your page, and GA4 will only credit the campaign if your parameters are still on the URL when the GA tag runs and analytics storage was allowed at that moment. Anything sitting between the click and the tag can cost you the second one and leave the first untouched.

All of this reaches me as support tickets rather than as media buying, since a Shopify tracking app is what my employer sells and it is what merchants blame first when two dashboards disagree. Which is a long way of saying I have never once found the cause sitting on the ad side.

To separate the two failures on Ad Group C: put GA4 page views on that landing URL next to GA4 sessions attributed to the campaign. Page views close to the platform's number with sessions well short of it means nothing is missing and only the attribution is. Page views also short means the tag is not running for part of that traffic, which is consent or a blocker rather than anything about the ad group.

If all three groups genuinely do land on the same URL with the same consent setup, say so, because then it gets interesting.