Platform

The infrastructure beneath every decision.

One real-time system for user data: four services that turn raw signal into action, a control plane and a data plane that keep policy and processing separate, and an Activity Graph that understands what a user is trying to do. This page is the canonical definition of how the platform works.

Services

The service spine.

Every pipeline on the platform runs the same four services, in order. This is the canonical definition — every other page references these terms rather than redefining them.

  • Ingesting — real-time collection of user actions at the edge.
  • Graphing — structuring activity and identity into the graph: who the user is, what they did, what they're trying to do.
  • Decisioning — evaluating context, rules, and models to determine the right system action. Included in every Product — Decisioning is never metered.
  • Activating — delivering the result where it creates value: audiences, messages, system actions.
↓ Signals in
Site & app events · CDP / CRM & 1st-party · Inbound calls · Email engagement · Impressions · CTV exposure

Ingesting

Collect at the edge
Cross-device · Cross-channel
Deterministic · Probabilistic

Graphing

Resolve & structure
Identity · Activity
Audience · Portfolio

Decisioning

AI / ML engine
Context · Rules · Models
Real-time triggers

Activating

Route & act
Audiences · Messages
System actions
Actions out ↓
Audience activation · Lookalike seeding · Frequency & sequencing · Dynamic creative · Channel routing

Ingesting, Graphing, and Decisioning are included. Value is charged on Activating.

* DaaS = Data. The four services above are IaaS. Data-as-a-Service — the on-demand data service — is metered separately, per record. See how each service maps to a billable Usage on the taxonomy.

Taxonomy & token specification
How each service maps to Solution → Product → Feature → Usage
Read the spec
Architecture

Two planes, cleanly separated.

Data planes process events. Control planes control outcomes.

The platform splits into two planes that run independently. The control plane decides; the data plane processes. Keeping them separate is what lets policy, models, and orchestration evolve without touching the fabric that handles every event — and lets each scale on its own.

User Control PlaneDecides & directs
Real-time orchestration — evaluates context and rules, runs models, and directs the right system action.
AccessTargeting rulesContext evaluationAgent orchestrationAI/ML models
Directives & rules
User Data PlaneProcesses every event
Real-time state and activity fabric — captures actions, resolves identity, and carries out the actions the control plane directs.
User actionsIdentity resolutionActivity graphData sourcingSystem actions

The two planes scale and evolve independently — new models and rules ship on the control plane without disturbing the data fabric, and the data plane grows with volume without waiting on policy.

Activity Graph

Structured intent, not static segments.

The Activity Graph organizes everything known about a user into five layers — from who they are down to what they just did. Each layer answers a different question, and together they express intent rather than guess at it.

Identity → Vectors → Missions → Sessions → Actions
IdentityWho the user isIdentity
VectorsWhat they care aboutIntent
MissionsWhat they're trying to doIntent
SessionsHow they're interactingBehavior
ActionsWhat they didBehavior

Marketing platforms segment people. The Activity Graph understands what they are trying to do.

An Actor performs an Action at a Destination with an Action Agent.
Closed loop

Every pass makes the next one smarter.

The platform runs a single loop end to end. Three steps map directly onto the service spine; the last two close the loop by feeding every outcome back into the graph.

Observe
≈ Ingesting
Capture the action the moment it happens.
Decide
≈ Decisioning
Evaluate context, rules, and models to choose the action.
Act
≈ Activating
Deliver the result where it creates value.
Measure
closes the loop
Attribute the outcome back to the action.
Learn
closes the loop
Write what happened back into the graph.

Every action feeds the graph. The graph improves the next decision.

Operating modes

One infrastructure, two ways in.

The same control plane is reachable two ways — pick the one that fits the team, or use both.

Assisted

Guided decisioning

Configure targeting, rules, and activation through the interface — guided decisioning with no engineer required.

Programmatic

Developer-first access

Reach the same control plane directly through the API — developer-first access to every service and rule.

One unified infrastructure, dual access model.