Orders and customers
Any number you see, you can open down to the orders that made it.
Instead of stopping at total revenue or an order count, open it: the order's number, value and state, the channel, the campaign, and the journey known before the purchase.
The problem
An aggregate hides the things that would change your decision.
If you cannot get from the number down to the order, you cannot tell whether the gap is real performance or a data problem.
- Orders cancelled or returned after they were recorded.
- More than one platform crediting itself with the same order.
- A returning customer showing up as a fresh acquisition.
- An order that carried no eligible ad click.
- Part of the store's orders never arriving, or never completing measurement.
If you cannot get from the number down to the order, you cannot tell whether the gap is real performance or a data problem.
The financial impact
Each of these costs a budget decision.
Budget going to a retargeting campaign
Plenty of orders and a low CPA, but most of those buyers were returning - which makes it a poor home for acquisition budget.
A campaign judged on cancelled orders
An order is read at its final state, not at the moment of purchase - and cash on delivery makes that gap wide.
Comparing ROAS before checking coverage
If part of your orders never completed measurement, comparing two campaigns compares two coverages, not two performances.
What Raasid shows
From your store's total orders down to one order and its customer.
Store order matching
Raasid sets your store's orders against what reached it, what completed measurement, and what could be tied to an ad interaction. Unmeasured orders do not disappear - they stay on the screen as a gap that needs explaining.
Open an order and read its evidence
- The order's number, value and date.
- Its state: confirmed, cancelled, returned or pending.
- Channel, platform and campaign where they exist.
- The attribution model applied.
- The reason it was not attributed, when it was not.
- A link to the known customer journey.
New and returning customers
Whether the buyer is new or returning, on a stated definition. CAC in Raasid rests on new customers; CPA covers orders from new and returning buyers alike.
The screen
From your store's orders to what can be measured
Four stages, each with its count and its share of your store's own total. A share alone hides how many orders it stands for; a count alone hides how far it fell from the total every other number is read against.
Go from the total down to the order itself
Open a stage or an order to see the evidence behind the number.
- Store orders1,284−13
- Reached Raasid1,271−359
- Measured912−412
- Linked to paid500
- Status
- Confirmed
- Customer
- Returning
- Platform
- Meta
- Campaign
- Sales - retargeting
- Why it linked
- Last paid click
An illustrative example
One known journey, break included
The touchpoints in the order they happened, with the break drawn where it falls rather than filled in with a guess. Where two devices share no identifier the journey stays partial - and that is written down, not hidden.
And in the matching above: 372 orders cannot carry a full advertising judgement. Before you compare ROAS, check coverage first.
The decision it enables
You can tell whether a number deserves a decision or a second look.
- A confirmed order in a final state on a known channel - a number you can move on.
- An order with no eligible paid interaction - evidence neither for the campaign nor against it.
- Low coverage in a period - postpone the comparison instead of building on it.
The limitRaasid links journeys with the identifiers available. A shopper who starts on one device and finishes on another with no shared identifier may appear as two journeys, and no complete cross-device tracking is claimed.
Start
See the orders behind your campaign numbers.
Connect your store and one ad channel, then compare what Raasid confirms against what the platform reports over a period you know.