How the technology works
The non-technical explanation
When someone visits a website, they leave behind a trail of raw interaction data. Traditionally, tools stitch that trail into a journey using an identifier - a cookie, a login, a device ID - which acts like a name tag. Remove the name tag, as consent rules now routinely do, and the journey falls apart into disconnected fragments.
Corvidae does not look for a name tag. It reconstructs which fragments belong to the same journey by learning the patterns of how real sessions behave, using neural network models, and rebuilding the sequence predictively. The journey is reassembled without ever identifying the person.
That reconstructed journey is then converted into a value against each advertising click and sent back to the platform, so the bidding algorithm is optimising against what actually happened rather than what it could see.
The technical explanation
Corvidae ingests raw first-party eventstream data via a first-party pixel.
A data cleansing layer normalises it, a re-evaluation engine recovers session relationships within non-session data, and a path-building engine links interaction sessions into complete journeys. Long short-term memory neural network models handle the sequential reconstruction using attention layers.
Reconstructed multi-touch journey values are exported via API against GCLIDs for Google, and equivalent identifiers for Meta, and to the client's own data and BI layer.
No cookies and no persistent personal identifiers are used at any stage, which makes the architecture GDPR and CCPA compliant by design rather than by configuration.