Activation
Data only pays off when it gets back to where decisions happen
Deliveries push conversions back to Meta, Google and your own systems — with identity already resolved, the right filter, and an audit record for every send.
Genuinely server-side
It leaves your server, not the browser. Ad blockers and closed tabs stop being your problem.
Filters built on real payloads
You write the rule while looking at the actual payload, and test it against recent events before publishing.
Per-delivery audit
What was sent, what was rejected and why. No black box between you and the ad platform.
Deliveries
Pick the event, filter it, map it — on one screen
A delivery connects one of your events to a destination. You choose the source, write the business filter (approved purchase, first-time buyer, a specific product) and map the fields. What goes out is assembled server-side, with email and phone pulled from the identity graph — not from whatever happened to be in the payload.
- Filters built from the fields actually measured in that source
- Tested against recent real events before publishing
- Field mapping suggested by observed coverage per field
- Automatic pruning of anything that should not travel outside
Checkout · purchase
status = APPROVEDAND product contains “Coaching”AND first purchase
✓ tested: 8 of 30 real events would pass
value ← price_value
em ← lead.email (100%)
ph ← lead.phone (97%)
Purchase delivered · 214 ms
Quality
Match quality measured, not estimated
The quality screen shows real coverage of every parameter across payloads that were actually delivered: what percentage carried email, phone, external identifier, ad cookie, city. That is the number you use to decide where to invest to improve matching — not a generic score.
Reliability
A destination going down should not become a silent loss
Expired tokens, unavailable destinations and rejected payloads each get their own handling. The delivery holds what it cannot send, tells you what the problem is, and reprocesses when you reconnect — instead of silently dropping launch-day conversions.
- Circuit breaker per destination, so one failure does not take down the rest
- Held queue with reprocessing on reconnect
- Error categories separating credentials, format and transport
- Token expiry monitoring
Frequently asked questions
Does this replace the Meta pixel on my site?
It does not have to. The ideal setup runs both with the same event identifier, which is exactly how the platform sends them — Meta deduplicates and you get the coverage of both paths.
Can I send only approved purchases?
Yes, and it is the most common setup. Status arrives with the event and you filter on it. Without that filter, an expired payment becomes a conversion and teaches the campaign to find the wrong person.
Can I send to my own system instead of an ad platform?
Yes. The webhook destination delivers the resolved event in whatever shape you map, signed so your side can verify the origin.
Start measuring what actually becomes revenue
Create a free account, connect your first source and see your first lead timeline today. No card required.