Flagship · Osoul · live
Osoul: server-side tracking and CAPI sync
A tracking service built on the open-source tracking kit, turning guest events into signed server-side Conversions API events for ad-audience optimisation.
Part of the Osoul platform case study. Built on the open-source tracking kit.
Problem
Restaurants spend on ads to fill tables, but ad platforms only learn from conversions they can see. Browser pixels are blocked, lose events and know nothing about what happens in the restaurant: a reservation that turned into a visit, a visit that turned into a high ticket. Without those signals, ad platforms optimise for clicks instead of guests who come and spend.
Constraints
- Server-side first: events must reach ad platforms from Osoul’s servers, not depend on the browser.
- Trusted events only: anyone can call a public endpoint, so events must be signed by known clients.
- Privacy: personal data is hashed before it leaves the platform, only for tenants who enabled it, and only with the guest’s consent to ad signals.
- One schema: Guest App, Portal and reservation events share one tracking event schema.
Architecture

Key decisions
- Reuse the open-source kit instead of a vendor. The tracking kit already did signed events and user recognition; Osoul adds the restaurant event schema and the CAPI sync on top.
- Send outcomes, not page views. The valuable signals are a reservation honoured and a ticket closed, which only the server knows.
- Sign every event. HMAC request signing means the tracking service only accepts events from Osoul’s own clients.
Results
Numbers to come.