Why does my ROAS differ from what Google or Meta report?

The ROAS truth check page puts Decisa's verified ROAS next to what Google/Meta claim for the same campaigns — a gap is normal, and each row's Why? button explains the likely cause.

Before you start

• A workspace with the Attribution module active and conversions coming in (pixel or checkout webhook).
• At least one connected ad platform with synced metrics. Without one, the page shows an empty state with a Connect an ad platform button.

Steps

1. Open ROAS truth check

   Use Sidebar → Attribution → ROAS truth check. The page title reads "Why your ROAS differs from the platform", under a one-line promise of why it exists: "The numbers, as they are. We compare what your pixel reported with what your server actually counted — so you trust the revenue, not just the dashboard."

2. Read the three summary cards

   Decisa ROAS is revenue Decisa verified from your own orders. Platform-reported ROAS is what the ad platform claims for itself. Revenue gap is the difference, with a hint telling you which side reports more. A note below the cards puts the gap in context.

3. Pick a grouping and date range

   Use the group-by selector to switch between Per campaign and Per platform, and the date picker to change the window (last 30 days by default).

4. Expand the biggest gaps

   The Per-campaign comparison table sorts the biggest gaps first. Click Why? on a row to see labeled signals — for example Platform-only revenue (the platform claims sales Decisa never saw) or Conversion-count mismatch (the counts don't line up) — each with a short explanation.

What happens next

• Some signals come with a shortcut link: a count mismatch points you to your conversion triggers; platform-only revenue points you to your pixel and webhook coverage.
• When every campaign matches within tolerance, a green banner confirms it: "Decisa and your platforms agree across all campaigns — your numbers are trustworthy."
• Curious how the model choice changes the picture? Use Compare attribution models → at the top of the table.

Gotchas