From ad click to order: see what reached your platforms
Raasid sends your store's events to your ad platforms from the server, and keeps a record for each one: delivered or rejected, and why. So you know what your decisions rest on.
Is the pixel enough?
Short answer: the pixel gets some of it through, and the rest depends on the shopper's browser. Here is the difference in detail.
Three scenarios: a store with no pixel, a store with browser pixel only, and a store using Raasid.
Your budget goes to whoever clicks, and the platform never hears about the sale. You have no number of your own to measure against.
The pixel sends from the shopper's browser, so anything that blocks it blocks the event. The harder part is that you cannot tell which events went missing, because nothing logs it.
The event goes straight from your store's server to each platform and leaves a trace: delivered or rejected, why, and how many identifiers it carried. So you can compare the platform's number to your store's instead of guessing.
The pixel leaks data drop by drop, not all at once
Each of these eats into your data, and the problem is that all of them are silent: nothing tells you the event never arrived.
The blocker stops the pixel script from loading, so the event is never sent.
When the shopper declines tracking, the pixel loses the identifiers that tie the sale to the ad.
Safari caps the lifetime of script-written first-party cookies, so the link between a visit and a later purchase breaks.
A JavaScript error or a dropped request kills the event, and nothing tells you it never arrived.
A camera at the door can't track a whole warehouse
Imagine you run a store and want to know how many people came in and bought. The obvious first idea is to install a camera at the door - that's exactly what the browser pixel is.
Pixel = camera at the door
The problem: the customer can dodge the camera in many ways - an ad blocker, declining tracking, a tab closed before the script loads. Worse, you have no idea how often it happened, because nothing logs it.
- Ad blockers cover the camera entirely
- Safari on iPhone uses a side door
- Privacy settings turn off the lights
- iOS 14+ ATT cuts most data signals
Raasid = employee inside the warehouse
Instead of a camera, put someone inside the warehouse recording every transaction straight from the internal records. When Ahmed buys, the server tells Meta directly - whatever his settings or device - and leaves a log showing whether the event arrived.
The order itself comes from your store's webhook, not the thank-you page. A missed thank-you page, an ad blocker, or a closed tab cannot invent a conversion or drop one. Your store is the source of truth.
- Ad blockers can't reach the server
- Works on Safari, iOS, and every browser
- Unaffected by user privacy settings
- The server is the source of truth, out of reach of iOS 14+ ATT
Browser pixel vs server-side tracking
| Feature | Browser pixel | Raasid (server-side) |
|---|---|---|
| Ad-blocker resistance | Blocked | Unblockable |
| Data control | Platforms take it all | You decide what's sent |
| Site speed | Heavy JS loads | Zero client load |
| iOS 14+ impact | Can be blocked | Unaffected |
| Data Enrichment | Not possible | Automatic per event |
What does Raasid actually do when Ahmed completes an order?
Trace every moment between the ad click and the delivery - step by step, with real data.
Ahmed taps a Meta ad on Safari iPhone
Ahmed clicks an ad for a 480 SAR jacket. Safari opens on iOS 17 with the AdGuard blocker enabled.
Ahmed adds the jacket to cart
42 seconds after landing, Ahmed adds the product to his cart. The pixel tries to fire AddToCart, but it's blocked.
Ahmed completes the order
Ahmed pays. Your server issues order #20891. Raasid takes Ahmed's data, normalises it, hashes it, and pushes it to Meta.
Automatic deduplication
Browser and server both fire for the same order. Raasid ties them with the same event_id, so Meta receives it once - no inflated ROAS.
Meta learns and re-optimizes
Meta matches hash(email + phone) against its graph, identifies Ahmed, and feeds the algorithm a high-quality signal. It starts hunting for more shoppers like him.
How Raasid works, step by step
From the moment a customer clicks your ad to the moment the conversion lands in your ads manager.
Connect your store
One-click official app for Zid, Salla, and Shopify. WordPress, Magento, and custom (Webhook) stores coming soon. Setup takes under two minutes, no engineering required.
Activate your ad channels
Activate Meta, TikTok, Snapchat, and Google with one click - a secure one-click login, no tokens to copy and no developer. Event maps are pre-built per channel.
Collect every event automatically
Raasid captures visits, cart additions, checkouts, and sales - all as first-party, server-side events.
Enrich data & build identity
Geo IP is appended, emails normalized, PII hashed via SHA-256, and a stable Event ID is generated - a server-side identity that ad-blockers can't strip.
Match quality improves
The enrichment engine attaches as many of the identifiers you already hold as it can to every event - email, phone, visitor id, ad-click id, IP - so the platform can find the buyer. The dashboard shows coverage for each identifier separately.
Data is pushed back to ad platforms
Clean data streams through Meta CAPI, TikTok Events API, and Snap CAPI - every visit and every sale tied to the ad that drove it.
You decide on numbers you can audit
Algorithms learn from the signal that reaches them. Raasid shows you what actually arrived at each platform, and how much each platform claimed for itself against what your store recorded - so you compare instead of guessing.
"Why is your number different from my store's?" - answered per order
Two screens from the dashboard: one reconciles your store's orders against what Raasid received and attributed, the other opens any customer's journey touchpoint by touchpoint.
Matching
Your store's orders against what Raasid received and sent.
Why some orders carried no click identifier
Not every order comes from an ad - this separates organic from fixable
What was sent to the platforms
A single order may be sent to several platforms
Customer journey
Every marketing touchpoint and every order, in the order they actually happened.
Which touchpoint earns the conversion
The models disagree - here they sit side by side
Journey timeline
Browsing impact
Before the purchase
Activate your channels and watch every connection in one place
Click Activate on each platform - a secure one-click login, and Raasid confirms the connection instantly before you go live.
Connect your ad platforms
Click Activate on each platform - a secure one-click login. No tokens to copy, no developer.
Start without code
Unlock your store's full potential with server-side tracking that survives ad-blockers and iOS 14+.
Native integration with every ad channel that matters
Raasid by the numbers
Real infrastructure and measurable results, with no vague promises.
Questions every merchant asks
Will I lose my pixel if I install Raasid?
No. Your pixel keeps running as is. Raasid adds a server-side layer on top and handles deduplication between the two automatically. Meta receives each event once and only once.
Meta recommends CAPI - isn't Raasid the same?
Raasid uses Meta CAPI under the hood, but handles the hard parts: PII hashing, Event IDs, deduplication between pixel and server, automatic retries, live EMQ, and alerts. Setting up CAPI manually takes weeks of engineering and constant maintenance.
The pixel is free - why pay for Raasid?
The pixel is free, but it runs in the shopper's browser and leaves you no record. Raasid does not replace it: it adds a path from your store's server, and gives you a clear answer for every event - delivered or rejected, and why. Whether that is worth the price is your call to make on your own numbers during the trial.
What's the difference between an attribution tool and Raasid?
An attribution tool analyses data that already arrived and splits credit between channels; it sends nothing new to the platform. Raasid sends the event itself (visit, cart, purchase) from your store's server straight to each platform over the official Conversions API, so the algorithm learns from a fuller signal rather than only your report changing. You can run both together: Raasid delivers, attribution reads and compares.
Ready to link every conversion to the ad that drove it?
Activate Raasid from the Zid app market and get a guided install by our team.