Case study: how getexitpass.com sends its sales to Meta and ChatGPT Ads

Published on October 12, 2026 by the Oriva team.

getexitpass.com offers flexible flight reservations for onward travel. The domain was connected to Oriva on September 26, 2026: 1h15 later, the first visit arrived, and its sales have gone to Meta and ChatGPT Ads since. Of its first 6 purchases, in euros and dollars, all 6 were accepted by both platforms, with not a single failure. What this shows: a complete setup in a little over an hour, with a log of every send. What it does not show: a sales gain or a better cost per purchase, which are not measured here.

1h15: between creating the domain in Oriva and the first visit received
6 of 6: purchases accepted by Meta and by ChatGPT Ads
0: failed sends on these purchases

The site and what is tracked

getexitpass.com sells online, in English, and publishes guides for its visitors. The conversion tracked is the purchase, with its amount and currency: there are some in euros and some in dollars on the same site.

getexitpass.com is the site of one of our customers, who authorized us to cite it and to publish these figures.

Two destinations are connected: Meta (Conversions API) and ChatGPT Ads. Sales are sent from Oriva's servers, not only from the visitor's browser, and only with the visitor's consent.

The setup, hour by hour

On September 26, 2026, in UTC (Paris is two hours ahead):

04:06: The domain is created in Oriva.
05:02 (+56 min): The tracking code is confirmed on the site.
05:07 (+1h01): The ChatGPT Ads destination is connected.
05:12 (+1h06): The Meta destination is connected.
05:21 (+1h15): The first visit arrives.

The first purchase tracked is from September 30, the sixth from October 11.

What Meta and ChatGPT Ads receive

Platform	Sent	Accepted	Failures
Meta	6	6	0
ChatGPT Ads	6	6	0

“Accepted” means the platform answered that it received the event. Data read from Oriva's log on October 12, 2026.

Each purchase carries its order number as its identifier: if a pixel sends the same purchase with the same identifier, the platform counts it only once. Each send leaves a line in Oriva's log, with the platform, the time and the response received: when one fails, you know which and why.

Traffic that also comes from AI assistants

On October 3 and 4, Oriva recorded 5 visits from ChatGPT (4) and Perplexity (1) on two of the site's guides, one in English, one in French. That is small, and these are visits, not sales: but it shows that its guides are also read through AI assistants.

What this means, and what it does not

What it shows

It means that a site can send its sales to two platforms in a little over an hour, and read each send afterwards.

What it does not show

It does not mean that these sales are more numerous or cheaper: no before/after comparison, no ROAS.
It does not mean that the platforms counted them in their reports: Oriva knows they accepted the sends.

Who does not need Oriva?

You sell through a single platform and its pixel is enough for you, with the Conversions API already switched on by the platform: the gap does not justify one more tool.
You do not run paid advertising. There is nothing to send back to the platforms.

What getexitpass.com did in a little over an hour, you can do on your site: a domain, a tracking code, your destinations. Oriva is for when you want to send the same sales to several platforms at once, from the servers, with a log that says where each send went and why it failed. The detail is on the Oriva and the Meta Conversions API page, and for ChatGPT Ads in the guide Tracking ChatGPT Ads conversions.

Start free trial

Sources

Oriva's data for getexitpass.com, read on October 12, 2026, with getexitpass.com's agreement. This article is updated with the coming weeks' data.