About Raasid
A server-side tracking layer
Raasid sits between your store and your ad platforms: it captures the event on the server, delivers it to 4 ad platforms over their official APIs, and keeps you a record of every one - arrived or rejected, and why. 19 capabilities across 5 groups, and 3 store connectors working today.
The idea
Your store knows what it sold. Your platform knows only what reached it
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.
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
- 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)
- 19
- capabilities, each with its own pageCore event engine · Stores & channels · Monitoring & intelligence · Team & security · Commerce & payments
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.
Want to talk to someone?
Message us on WhatsApp - a person from the team replies. Or install the app and start.