What is Unify?
Unify is where your incoming data becomes a single, usable customer profile. Events, profile attributes, and consent information arriving with different identifiers are stitched together, so each customer exists once rather than as scattered fragments across devices and channels.
It is built from three pillars: the Catalogue defines the shape of your data, Identity Resolution decides which records belong to the same person, and Calculated Attributes derive new per-user values from raw events.
The three pillars
Catalogue. The schema layer. It defines the fields your organisation can hold, grouped into categories, using either Zeotap standard fields or custom fields you create.
Identity Resolution. The stitching layer. It takes the identifiers on incoming events and decides which unified profile each one belongs to, according to the ID strategy you configure.
Calculated Attributes. The derivation layer. It aggregates events over a period into a single value per user, so behaviour becomes something you can filter on.
How the pillars fit together
The pillars run in sequence as data moves through the platform. Sources ingest your data, and the Catalogue defines the fields it maps into. Identity Resolution then stitches those incoming events to unified profiles, so each customer is represented once. Calculated Attributes derive per-user signals from the events now attached to those profiles. From there the data leaves Unify: Audiences segment on it, and Journeys and Destinations activate it.
What lives elsewhere
Unify covers the concept layer. Several things that feel adjacent live in other modules.
- Sources, source mapping, enrichers, and Non-Customer Entity mechanics live in Integrate. The Catalogue defines your fields; mapping incoming source fields onto them happens in Sources.
- Building and activating audiences lives in Segment.
- Journeys and campaign orchestration live in Orchestrate.
- Consent and data governance controls live in Protect.
- Step-by-step onboarding lives in the Get Started Guide.
In this section
Last modified on August 28, 2026
