History is fragmented
Paid, commerce, care and loyalty each work from a partial view of the same person.
Platform Convert & Engage Data Platform
CRM, CDP, loyalty, commerce and warehouse data unified into a living context graph of customers, products and outcomes. It refreshes on every run, and it stays on your infrastructure.
Audience freshness
Why change
The data exists. It is spread across systems that each know one thing about the customer and nothing about why it matters.
Paid, commerce, care and loyalty each work from a partial view of the same person.
By the time the segment refreshes, the moment that made it valuable has passed.
More pipelines, more cost, more places for the numbers to disagree.
Permitted use, lineage and retention are documented but not enforced.
What it does
A data layer built for agents and marketers alike: governed enough for the CDO, fast enough for real-time decisions, simple enough to query in a sentence.
01 The living context graph
Customers, households, products, offers, channels and outcomes are held as connected entities. Every run of every agent reads from it and writes back what happened, so context keeps improving instead of drifting.
02 Pipelines and quality
Connectors for web, app, CRM, commerce, loyalty and warehouse feed a standard event contract. Agents watch schema, freshness and volume, explain what broke, and hold bad data before it reaches a decision.
| Source | Mode | Freshness | Quality |
|---|---|---|---|
| Commerce orders | Stream | 4 s | 99.8% |
| CRM contacts | Zero-copy | Live | 99.1% |
| Loyalty ledger | Stream | 9 s | 100% |
| Store POS | Batch | 26 h | Late |
| Warehouse marts | Zero-copy | Live | 98.7% |
03 Audiences and activation
Marketers build behavioural, lifecycle and predictive audiences by clicking or by asking. Each audience is evaluated continuously and published to the channels and tools that need it, with consent applied on the way out.
High-value customers who haven't bought in 60 days but opened the app this week
Built: top 20% lifetime value, last order over 60 days ago, app session in last 7 days, marketing consent = yes.41,280 people · 3,912 excluded for consent
Agents at work
Data agents handle the unglamorous work: mapping schemas, watching freshness, explaining anomalies and answering questions. Anything that changes what a customer is, or who can see them, stays with a person.
Ingestion checks, freshness monitoring, trait computation, anomaly triage and documentation.
New sources, schema changes, new traits used in decisions and any new export destination.
Use beyond consented purpose, raw personal data leaving your environment and retention rules being bypassed.
What's inside
Use ours out of the box, or put the same interface in front of the CDP and warehouse you already own.
Web, app, CRM, commerce, loyalty, service and warehouse.
Schema mapping and validation at the point of ingestion.
Customers, products, offers and outcomes as connected entities.
Lifecycle, propensity and value, in batch and real time.
Behavioural, lifecycle and predictive, by click or by sentence.
Batch, event-driven and near-real-time on the same logic.
Profile and audience APIs, webhooks and reverse ETL.
Federated queries and zero-copy access where the source supports it.
Privacy-safe matching and measurement with partners.
Field-level provenance and freshness for every source.
Purpose, suppression and deletion enforced, not documented.
A permissioned MCP server so your own assistants can query the graph safely.
How it runs
Each step is a named, logged stage. Nothing autonomous is switched on until its data, permissions, monitoring and rollback have been checked.
How you'll measure it
We agree the numerator, denominator, cohort and success gate with you before anything goes live, and compare against a baseline or a holdout, never against a hunch.
Questions
Keep it. A standard adapter puts your existing Customer 360 behind the same interface the rest of the platform uses, so nothing is migrated. Use our data platform only where you have a gap.
In your cloud or data centre. The platform is deployed inside your environment and reads warehouse data in place where it can, rather than copying it out.
A table tells you who the customer is. A graph also holds how things relate: which offer they saw, what they bought next, what it cost and what margin it made. That is what agents need to make a good decision.
Each attribute and audience carries its permitted purposes. Every read by an agent, a campaign or an export is checked against them, and withdrawals propagate to downstream systems.
Composable by design
The data platform is the centre everything else reads from and writes back to.
Identity resolution and the unified profile that sits on top of this data.
ExploreReal-time decisioning reads context from the graph in milliseconds.
ExploreExposures and outcomes are written back so every test adds to what the graph knows.
ExploreReads from the warehouse, CDP, CRM and commerce systems you run today, through one standard adapter.
Small language models trained on marketing data are deployed inside your cloud or data centre, so customer data and the models reasoning over it stay under your control.
Getting started
Choose a lifecycle outcome, connect the two sources it depends on, build two audiences and activate them in one channel.