Why Is My ROAS in the Ad Platform Different From My Store Data?

Your ROAS differs because each ad platform counts conversions inside its own attribution window and credits itself, while your store counts orders. The gap widens when slow landing pages, errors or mobile friction lose paid visitors after the click. Reconcile by comparing campaign and device segments against orders on your own site.

Why does ROAS look different in the ad platform and in my store data?

Each ad platform reports the conversions it can attribute to its own ads, inside its own attribution window. Your store records orders. When a shopper sees an ad on one platform, clicks another and buys three days later, more than one platform may claim the order while your store counts it once. Sum the platform reports and you will often see more conversions than the store recorded.

This is a measurement gap and it is normal. It does not mean one number is wrong. It means the two numbers answer different questions, and only the store's order count tells you what was actually bought.

What does the site control that the ad platform cannot see?

The ad platform sees the click. The site decides what happens next. Noibu's ROAS agent is built on the idea that the site controls the revenue half of the ROAS equation, and how to improve ROAS from the site side lists five leaks: slow landing pages, errors on money pages, broken journeys, mobile-only friction and bot clicks. Each one lowers orders while spend and clicks stay the same, which is exactly how a campaign can look healthy in the ad account and weak in the store.

How do I reconcile the two numbers?

1. Segment by campaign and device. Averages hide the problem. A campaign that sends mostly mobile traffic to a slow landing page can look fine in aggregate and poor in its own segment.
2. Filter bots first. Non-human sessions can make the worst pages look worse than they are, so remove them before comparing.
3. Score on orders, not clicks. Divide order revenue by spend for each segment, using the store's orders as the source of truth.
4. Check the landing page. Look for speed problems and errors on the pages each campaign sends traffic to. Technical checks for paid traffic that is not converting walks through them, and how to see what shoppers do after an ad click shows the journey.
5. Ship one change per page. Log each change as a release and compare conversion and ROAS over matching windows before and after.

What about consent banners and tracking gaps?

Part of the gap between tools comes from what each one can measure. When shoppers decline tracking, some visits and orders go unmeasured by one tool and not another. What a consent banner does to ecommerce data and attribution explains how to read that gap, so you do not blame the campaign for a measurement difference.

How does Noibu's ROAS agent help?

The ROAS agent compares paid traffic quality with on-site behavior, scores ROAS on orders rather than clicks, and recommends where to shift spend. It drafts changes for a person to approve and then measures the result against the campaigns sending the traffic. It works in the Noibu console and in AI tools such as Claude. Read more in Noibu's ROAS agent or on the ROAS agent page.

The short version: what should you check first?

To see where your paid traffic leaks on your own store, start with Noibu's free website audit.

Noibu is AI for ecommerce operations, the always-on optimization system that keeps online stores running at their best. A team of supervised AI agents finds what's broken, slow, or leaking revenue, does the work, and hands results back for human approval. Trusted by retailers like Free People, Guess, Liquid I.V., and Ariat.

Frequently asked questions