Measuring the result
You know what you spent. Raasid shows what came back.
Each platform reports results the way its own attribution works. Raasid goes back to your store's orders and ties spend to orders, revenue and new customers, so you compare campaigns off one reading before you change a budget.
The problem
The same campaign can look excellent in one place and ordinary in another.
Every platform uses its own window, its own signals and its own way of counting - and more than one can credit itself with the same order. Read each report on its own and you may raise a budget on overlapping revenue, or cut one because part of its result never showed up.
The financial impact
A difference in measurement changes the budget decision.
Scaling a campaign too fast
A high in-platform ROAS can rest on orders other platforms are also crediting to themselves.
Stopping a good campaign early
When coverage is short, a low result can be a measurement problem before it is a performance problem.
Mistaking an order for a new customer
CPA measures the cost of an order; CAC measures the cost of acquiring a new customer. A retargeting campaign can post an excellent CPA without being your best acquisition campaign.
What Raasid shows
From the whole period down to one campaign.
The financial summary
- Total connected spend.
- Store revenue and MER.
- New customers and CAC.
- Orders and CPA.
- The revenue Raasid tied to paid channels.
- Measurement coverage beside the result, not beneath it.
The platform comparison
- Spend, and the orders and revenue the platform reports.
- The orders and revenue Raasid measures.
- ROAS on both readings, and the gap in value and share.
- The coverage state, before you explain the gap.
Campaign performance
Per campaign: spend, orders, revenue, ROAS, the change from the period before, and the measurement state. Opening one takes you to the orders that made the number.
The basis the revenue was credited on
- Four attribution models you switch between live: last paid click, first click, linear, and position-based.
- An attribution window you choose, with the whole reading recomputed on the same orders.
- Two settings side by side, with a column showing how much each channel's share moved.
- And when the totals match across both settings it says so outright: nothing changed in your sales, the same money is being credited to different channels.
An explanation on every number
Every metric opens a short note answering what it means, where it came from, how it is worked out, and where it stops.
The screen
What the platforms report, beside what Raasid confirms
The same period on two methodologies. The gap is shown in value and in share, with the coverage state beside it - because a gap cannot be explained before you know the coverage it was read on.
Compare the same campaign from both sides
Choose a platform and a metric, then see how the decision changes.
What does this mean? The gap is not proof that one number is wrong. It flags a different attribution method, so do not move budget before opening the orders and coverage behind it.
An illustrative example
Three readings, three different questions
These are not three names for one metric. Each has a different scope and a different method, and the example is here to show why you need to know a number's source before you act on it.
The decision it enables
Instead of “which platform's number is highest?”, ask “which campaign has confirmed orders and coverage I can trust?”
- Where the reading is solid enough to scale on.
- Where you need to check before moving budget.
- Where the problem is measurement, not performance.
- Where the data does not support a judgement at all.
The limitThis describes what Raasid could tie together under the stated model and period. It does not prove experimentally that the ad caused the order, and it does not replace incrementality testing or MMM where you need them.
Next
Other groups you might be asking about
Start
Read your spend from the platform's side and the store's side together.
Connect your store and one ad channel, then compare what Raasid confirms against what the platform reports over a period you know.