Journeys and products
Find where the shopper stops, and which product is worth more spend.
Raasid ties the visit's journey to the order, then shows how products performed and which channels and campaigns stood behind their sales - so you can tell a problem in the ad from a problem inside the store.
The problem
The ad brought a visit. What happened next?
A campaign is judged on the final order, but the road from visit to order has four stops, and any of them can halt traffic for reasons that have nothing to do with the ad. Without the stops, every drop in the result reads like a targeting problem.
The financial impact
Where it stops changes where you fix it.
Plenty of visits, few product views
The page, the load time or the quality of the visit may need a look - and more budget here buys more visits that fall at the same spot.
Plenty of views, few carts
The product, the offer or the price may be the place to look, rather than the targeting.
Plenty of carts, few checkouts
Shipping, payment or trust may be the problem - and all three sit inside your store, not inside the platform.
What Raasid shows
Two halves: the journey, then the products.
The purchase journey
Each stage with its count and its conversion from the step before, and the biggest drop named. The funnel locates the position; it does not prove the cause - so where it says “may be”, it means may be.
Product performance
- Orders per product.
- Confirmed revenue.
- The share of sales linked to paid advertising.
- The top contributing platform.
From the product to the campaign
Open a product to see the platforms and campaigns behind its orders, and go from a campaign down to the orders themselves.
The screen
From the visit to the order, stage by stage
Five stages with their counts, the conversion at each one, and the biggest drop marked. The point is where paid traffic stops, not web analytics.
Read the journey and products together
Switch the view and open the stage or product you want to understand.
Viewed a product · 43,300 visits did not move on from the previous stage. This locates the drop; it does not prove its cause.
An illustrative example
The highest revenue is not always the most ad-dependent
Sort by revenue, then by the share of sales linked to paid advertising, and the order changes. A product with higher revenue and a lower paid share is one whose sales largely do not come from your budget.
Ad spend per product is not shown here, and so there is no product-level ROAS: apportioning spend to a product in a way you could audit is not available in this reading, and a number built on an estimated split would have been the weakest figure on the page.
The decision it enables
You learn where to fix before you change the budget.
- A stop before the product view - the position is the page or the quality of the visit.
- A stop at checkout - the position is inside your store, and more spend will not move it.
- A product with a high paid share carrying its revenue - that is the one your budget actually stands behind.
The limitThe journey shows what was observed; it does not explain on its own why traffic stopped. And product performance depends on orders being attributable to a product in a way that can be audited.
Start
Tie spend to the journey and the product, not to the final order alone.
Connect your store and one ad channel, then compare what Raasid confirms against what the platform reports over a period you know.