Causation
Measurement describes; it does not prove cause
A number rising after the measurement did does not mean measurement caused it: season, stock, price and creative all move together. Raasid shows what changed and when; why stays yours.
The methodology
Before you move a budget on a number: how it was computed, over what denominator, and where it stops — including what this measurement cannot tell you.
Every number on this panel has one written definition and one written boundary — all five, in full.
The measurement chain
The number is the output of six steps. Knowing them changes what you do about a low one: look at the weak step, not the whole figure.
A visit, a view, a cart, a checkout, an order — from your store's server, not the browser, so no blocker or closed tab decides what was recorded.
Scattered events gather onto one person using the identifiers available — email, phone, click ID. The more complete, the fewer sessions stay unowned.
The store's order is matched to its event. One with no counterpart stays in the denominator and visible, not dropped.
A qualified ad interaction is looked for inside the window. None means a measured order with no channel — shown as it is, never spread by guesswork.
One channel, one campaign, so an order is never counted twice. Platforms may each claim the same one — a leading reason the numbers differ.
Attributed orders roll up into campaigns, products and periods with spend divided over them — and every aggregate opens into its rows.
Causation
A number rising after the measurement did does not mean measurement caused it: season, stock, price and creative all move together. Raasid shows what changed and when; why stays yours.
What never arrived
An order that never reached us — broken connection, unconnected channel, a period before activation — appears as a known gap, neither inferred nor estimated.
Off your store
Views, in-app engagement and modelled conversions happen inside the platform. We show what it reports beside our numbers, and claim no way to verify it.
The limit of identity
Start on one device, finish on another with no shared identifier, and one shopper arrives as two. Identifier completeness is on the dashboard because it is this step's ceiling.
How much of the measurement completed at all is a metric in its own right — identifier completeness and coverage.
The limits, in writing
Four things you would test us on, written down before you ask. A methodology that does not know its edges is not one to set a budget against.
Why they disagree
Why is the platform's number bigger than my store's? Four mechanical reasons — and neither has to be wrong to differ.
Saw an ad here, clicked another there, then bought. Each credits the order to itself, so their total exceeds your order count with no one wrong.
Seven days after a click here, twenty-eight there, a view with no click at a third. Your period is one; their windows are not.
When signal is short, platforms estimate conversions rather than leave them at zero — stated openly, but part of the figure is an estimate, not an event in your store.
A platform records the purchase as it happens; confirmation, cancellation and return are outside its reach. Raasid reads the order in your store's state.
The connection, last on purpose
The store through its platform's app, each channel through its own official login — no tokens, no theme edits. Measurement starts at connection, never retroactively.
Click Activate on each platform - a secure one-click login. No tokens to copy, no developer.
The channels read today
The next step
Connect your store and one ad channel, then compare what Raasid confirms against what the platform reports over a period you know well.