CDP
Every cookie, email, order and login. One profile per person.
Kontala CDP resolves identity in real time, keeps a live, consented profile for every visitor and customer, and syncs audiences that update themselves to the tools you send from.
Six reasons to build on one customer profile
One profile per person, in real time
Cookies, devices, emails, phone numbers, orders and account IDs are stitched as they arrive, across your website, apps, Shopify and your own systems.
No duplicate customers, and no nightly batch job deciding who is who.
Identity you can trust, and undo
Clear rules decide every merge, each merge is recorded with the evidence behind it, and any merge can be reversed.
A wrong merge is an undo, not a data-cleaning project.
Audiences that update themselves
Segments combine traits, behaviour, sequences and consent, and membership changes within seconds of the event that decides it.
Campaigns reach people while the intent is still there, not after tonight's batch.
Personalise in real time, safely
One lookup returns a visitor's traits, live cart and segment flags, filtered by how strongly the visitor was identified and what they consented to.
Storefronts and apps react to each visitor without exposing anyone's personal data.
Consent enforced at every step
Consent is checked at collection, resolution, personalisation and activation, and again for the exact email address or phone number at the moment of sending.
Marketing only reaches people who said yes, on the channel they said yes to.
History that stays right
Events are never rewritten. Identity is applied when data is read, so when profiles merge or split, every report and model follows.
Attribution and lifetime value include the visits from before someone signed up.
Everything on one customer profile
Identity resolution
- Stitches cookies, app device IDs, emails, phone numbers, Shopify customers, CRM IDs and marketing IDs into one profile.
- Add your own identifier types, such as loyalty numbers, each with its own limits and merge rules.
- Keeps two known people apart, even when they share a device.
- Signed email links recognise returning shoppers on a new device, reversibly.
- Every merge is recorded with its evidence and can be undone, with a review queue for conflicts.
- Consented device matching proposes likely matches for review and never merges on its own. Opt-in
Profiles and computed traits
- Lifecycle stage, sessions, engagement and time on site, kept current with every event.
- Orders, net revenue, average order value, refund rate and when the next order is expected.
- Top categories and brands, price band, recently viewed products, and the live cart and checkout.
- Acquisition channel and campaign, location, language and devices.
- RFM scores, predicted lifetime value and churn risk, scored daily.
- Up to 50 custom attributes, such as a count, sum or top N over a time window.
Segmentation
- Combine traits, events, consent and other segments in one builder.
- Counts and sums over rolling windows, and sequences such as “viewed, then did not buy within a day”.
- Size estimates, overlap with existing segments and sample profiles before you publish.
- Membership updates within seconds of an event, and on time when a window passes.
- Versioned definitions, with size over time, entries and exits, and the compiled SQL for analysts.
Activation
- Sync segments and profile fields to Klaviyo lists for email and SMS.
- Consent, identity strength and suppressions are checked when each update is sent, not when the segment was built.
- Only the fields you allowlist leave the platform.
- Retries, rate limiting and a nightly reconciliation keep every list in step.
- Meta and Google audiences, sent as hashed contact data. Coming soon
Real-time profile API
- Look up any identifier and get back traits, the live cart, recent products and segment flags.
- Answers depend on how the visitor was matched, so a forwarded email link never unlocks someone else's data.
- No profile fields without personalisation consent.
- Built for 20 ms lookups (p95) from your storefront edge or app backend.
Privacy, consent and security
- An append-only consent ledger for each device, email address and phone number.
- Contact data is sealed at collection and rests only in an encrypted vault. Everything else sees keyed hashes.
- Access and erasure requests reach every store, model and destination, and are logged.
- Roles from marketer to privacy officer. Revealing contact data needs a fresh two-factor check and a written reason.
- An audit log of every reveal, unmerge, erasure and key change.
- Dedicated cells with their own encryption keys for regulated businesses. Coming soon
Sources in, audiences out
- Kontala Data Capture
- Shopify store and checkout
- iOS and Android apps
- CRM, POS and backends via API
- Klaviyo email and SMS
- Storefronts and apps via API
- Meta Coming soon
- Google Coming soon
Runs on Google Cloud in the EU, with every event and identity change kept in BigQuery.
Built for everyone who touches a customer
CRM and lifecycle
“Build the audience once. It keeps itself current.”
- Combine behaviour, traits and consent without writing SQL.
- Klaviyo lists stay in step, with no CSV exports.
Web and ecommerce
“Know who is on the page while they are on it.”
- Live cart, recent products and segment flags from one API call.
- Recognise returning shoppers across devices and email clicks.
Data and engineering
“One identity graph, not five copies of the customer table.”
- Full event and identity history in BigQuery, never rewritten.
- Server-to-server APIs, safe retries, and identity rules as configuration.
Privacy and legal
“Consent is enforced, not hoped for.”
- Every reveal of contact data needs a reason and is audited.
- Erasure reaches every store, model and destination, and is logged.
Not a black-box identity graph
Rules you can read, merges you can undo
Every merge records its evidence and can be reversed, so a mistake never becomes permanent.
Guesses never merge
Device matching only proposes candidates. Nothing merges because a score is high.
Real time, not overnight
Identity, traits and segment membership update within seconds of each event.
One profile every module shares
Analytics, Personalisation and CVM read the same profile, so every team sees the same customer.