About Raasid
An independent reading of your results, and a signal that reaches your platforms
Raasid sits between your store and your ad platforms and does two things: it reads your campaign results from your store's own orders — on a stated denominator, with the gaps left visible — and delivers your supported events to 4 platforms over their official APIs, keeping each delivery's answer as it came.
The idea
They buy, it is recorded, it arrives, and the platform learns
The pixel runs in the shopper's browser, and there it loses events for reasons that have nothing to do with your store: privacy settings, ad blockers, a browser closed before it fires. Raasid sends the same event from the server, where none of that stands in the way.
- 1They buyAn ordinary order from your store
- 2The server records itNot dependent on the shopper's browser
- 3It reaches the platformOver its official API, with a record
- 4The platform learnsIt goes looking for buyers like them
What it is not
Three things that get misread
- Not a replacement for the pixel - the pixel stays where it is, and Raasid sends the same event from the server with an ID that stops it being counted twice.
- Not an ad platform and not a place you buy from - Raasid buys no ad, changes no budget and pauses no campaign.
- Not one store platform's add-on - the platform is a point of connection, and the product is independent of it and reaches four ad platforms rather than one.
The shape
What runs today, and what is in development
Principles
How we write what you read here
We don't promise what hasn't shipped
Each connector's status is read from one source in the code, and every page counts from it. A connector that has not shipped reads “in development” everywhere it appears, with no date.
No numbers without a source
You won't find a customer count, a growth percentage or a case study on this site. The figures in the dashboard images are example data and labelled as such; everything else is counted from the site's own data at render time.
The mechanism before the result
Everything described here is described as a mechanism: what is read, what is sent, and what comes back. The result depends on your store and your campaigns, and it is not ours to promise.
Where it runs
The connectors, plainly
- 4
- ad platforms receiving eventsMeta · TikTok · Snapchat · Google Ads
- 3
- store connectors working todayZid · Salla · Shopify
- 3
- connectors in development, with no dateMagento 2 · WordPress + WooCommerce · Custom store (Webhook)
- 18
- capabilities, each with its own pageWhat you decide on · Measurement quality · Events & channels · Trust & compliance
3 connectors work today (Zid, Salla, Shopify), and 3 are in development with no announced date. The detail of each - and what it reads - is on the platforms page.
Want to talk to someone?
Message us on WhatsApp - a person from the team replies. Or install the app and start.