The customer data platform
Five arrivals.
One customer.
Every analytics tool you own counts a person once per device, once per session, once per channel. Cookiebees resolves them into one record on your own domain - so lifetime value is real, segments count people, and every message knows who it is talking to.
Mobile web
Instagram ad
anonymous
Desktop
Google search
anonymous
Email tap
Newsletter
known email
Replied to a nudge
known phone
Mobile app
Checkout
order
One customer record
First seen on Instagram · bought on mobile
Sessions
0
Devices
3
Lifetime
₹0
A CDP is not a database.
It is one decision, applied everywhere.
The decision is to treat a person as a person. Everything below is a consequence of it - which is why bolting a CDP onto three tools that each keep their own idea of a customer never works.
Resolved on your own domain
Identity is built first-party, from a path on your root domain - not a third-party script that Safari caps and blockers strip. It survives the things that break everyone else's.
One record, not one row per session
The mobile scroll from Instagram, the desktop search a week later and the email tap after that collapse into a single customer with a single history.
The same record everything else reads
The CRM messages it, recovery targets it, and the ad platforms match against it. One graph, so the three never disagree about who somebody is.
Yours, and portable
It is your first-party data in your workspace. Export it, segment it, or push it to your ESP - we are not holding it hostage to keep you.
How resolution works
Four rungs. Every arrival climbs the same ladder.
An order and an abandoned checkout are the same question in different clothes: a payload turns up and we find the browser that was browsing. Both climb these rungs in this order, so a cart and its own order can never disagree.
The id we already hold
A server-set first-party cookie on your own domain, 400 days, re-issued on every visit. Safari’s seven-day cap never touches it.
Shopify’s own cart token
The token belongs to Shopify, not the checkout app, so a one-click checkout nobody has studied still joins for free.
The checkout partner’s session
Shopflo, GoKwik, Pragma, Appbrew: each one forwards an id, and the registry knows which. A new partner is one line of config.
The customer archive
Hashed email and phone, matched on what the ad platforms can use. The last rung, and the one that turns a stranger into a returning customer.
Every order records which rung joined it. When none did, the ingest log names the id the checkout offered, so a provider we have never seen becomes one line of config rather than a permanent blind spot.
Segments that count people
Not “2,740 sessions”. 2,740 people you can message.
Because the graph resolves to a person, a segment is a list you can act on rather than a number you read. Lifetime value, recency and behaviour are all properties of the same record, so the counts hold up when somebody asks how they were reached.
- Behavioural conditions: browsed recently, added and never bought, bought once and never again
- Lifetime value attributed to the channel that first found them
- Live counts that update as people move between segments
- Every segment is addressable - email, WhatsApp, or a Meta audience
What identity is actually worth
An abandoned checkout stops being a session. It becomes a person.
This is the difference resolution makes in money rather than in theory. An anonymous session can only be retargeted; a resolved customer can be emailed, messaged, offered the exact thing they left, and credited when they come back.
- Recovery playbooks that address a person, not a cookie
- The products they actually looked at, not a generic bestseller blast
- Revenue credited send by send, never estimated
- The same record the ad platforms match against, so conversions land
Checkout abandoned
cart ₹6,240 · known customer, reachable
45 minutes later
coupon COMEBACK10 sent by email + WhatsApp
Opened, clicked, came back
viewed cart → checkout, same evening
Purchased ₹6,240
credited to the send, not re-credited to the ad
Sent
90
Opened
48
Recovered
12
Revenue
₹0
Audiences the platform can actually match
Built from behaviour. Sized against Meta before they sync.
A segment is worth having only if the platform can match it. The Audience Builder states the identity wall beside every count, previews the match before the sync, and ranks audiences on cost per add-to-cart, the number spend actually joins to. Underneath it, a propensity score learned nightly on your own store says who buys next.
- RFM, acquisition channel, cross-sell, cadence, location, negation and no-purchase conditions
- Previewed against Meta, refused before the click when it cannot help
- Who buys next: calibrated nightly, never a ranking published as a rate
- Eight more audiences from behaviour the store already records
Checkout abandoned
cart ₹6,240 · known customer, reachable
45 minutes later
coupon COMEBACK10 sent by email + WhatsApp
Opened, clicked, came back
viewed cart → checkout, same evening
Purchased ₹6,240
credited to the send, not re-credited to the ad
Sent
90
Opened
48
Recovered
12
Revenue
₹0
One place, one identity graph
The graph is the floor the other two stand on.
Close the loop on your next lead
Transform your brand with signals.Your first order, credited, in ten minutes.
Measurement first, then everything else. Spin up your workspace in minutes and watch the first signal go back on your very first order. 30-day free trial, no card required.