Everything inside Raasid

Direct server-to-server delivery, with smart retry logic and a durable queue that holds every event even when a platform is slow to answer.

A score out of 100 with a blunt verdict beside it - "good: strong matching data" or "weak: the platforms are matching blind". Under it, every identifier with its own rate: email, phone, visitor ID, ad-click ID, IP, browser data - each tagged as either "yours" (something you can improve) or "automatic" (our side). Plus delivery status in detail: accepted, rejected, held back, unauthorized, or needs reconnecting. With two tabs - conversions alone, or all events - because the two numbers differ sharply and you deserve to see both.

Geo IP, email normalization, SHA-256 hashing, and session unification to lift match rates.

Activate Meta, TikTok, Snap, and Google in one click - a secure login with no tokens to copy, and independent settings per channel.

The first screen you open answers one question: where the platforms' numbers diverge from reality, and why. Each platform gets a plain line - "Meta reports 32% below Raasid", "Snap reports 130% above", "TikTok reports nothing" - with the gap in riyals and its likely cause. Below it, "what needs your attention now": priority-ranked cards, each carrying the evidence in numbers, the action to take, and a direct link to the screen that fixes it.

Live feed of every event entering the system, its delivery status per platform, and the full payload that was sent.

Ten alerts that catch problems before they cost you: connection dropped, tracking stopped, events rejected, ad-click matching fell, order coverage fell, orders arriving untraceable, spend up with no revenue behind it, real ROAS dropped, fewer ad visitors converting, and cart abandonment spiking. High-severity conditions are re-checked hourly, and you can mute any type you do not care about.

Run two settings side by side on the same orders and see the difference yourself: every channel's revenue under each, and a column showing exactly how much its share moved. And Raasid tells you the truth other tools leave out - 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." Four models you can switch between live: last paid click, first click, linear, and position-based - with an attribution window you choose.

Your own order counts from Zid or Salla, side by side with what Raasid received, day by day. How many arrived, how many were attributed to an ad, and how many stayed unattributed and why - every order listed by its number. "Why is your number lower than my store's?" now has a per-order answer.

A table of every matched order: its date, its number, the channel that drove it, the exact campaign name, its status, and its value - filterable by any platform, with a button that opens that buyer's full journey. When a number looks wrong, you don't argue with us about it: you open the order and see where it came from yourself.

Ad platforms report cost per "conversion" using the inflated placed-order count. Raasid reports what an order actually costs: cost per order placed, per confirmed order, per delivered COD order, and the share of spend that went to orders that were lost. And it goes further down - the cost of every stage before the order: what a single session cost you, a product view, an add-to-cart, a checkout started. So you know exactly where spend turns expensive, not just the final result.

Exactly where ad-driven shoppers fall out, from landing to money collected, counting distinct shoppers at every step. Your single biggest leak is named outright: "your worst step is product view to add-to-cart." Alongside it: session length, engaged-session rate, and time to reach cart or checkout.

The whole story in one descent: what the platforms claimed, what Raasid actually attributed, minus cancelled and refunded, minus COD still awaiting delivery, down to revenue really collected. Every step shows orders and money, and the steps add up exactly.

What share of your store's own orders Raasid actually saw, computed against your real daily order total pulled from Zid or Salla. Turns "we matched N orders" into "we cover N of your M" - a number you can hold us to.

Every number you could misread carries an info circle that opens a short explainer: what it is, how it is calculated in words rather than formulas, a worked example, and its honest limit. Each one written against the service that computes the number, never from its label.

SHA-256 hashing of identifying data before transmission, so no raw identifiers leave your store.

A timeline of every touchpoint before and after the purchase, in the order it actually happened, with the channel named correctly - a paid ad shows as a paid ad, not "Direct". Alongside it: which touchpoint deserves the conversion (first touch, last paid touch, last touch) shown side by side so you can see how the attribution model changes the answer; browsing impact in numbers - page and product views, add-to-carts, checkouts started, sessions; and time to first purchase plus relationship length. Plus the customer's own number in your store so you can look them up in your Zid or Salla admin. Raasid holds no readable name, email, or phone.

Full shopper journey tracking - from view_product to add_to_cart to purchase - for every platform.

Recover confirmed purchases directly from the store database - even if the pixel fails at checkout.