One profile per customer, built from everything you know about them.
Compass turns scattered activity from commerce, surveys, and events into a single, queryable customer record — with identity resolution, an event pipeline, and a full audit trail.
A profile is more than a contact
Each of these pieces feeds the same record, so audiences and campaigns can reason across all of them at once.
Unified profiles
One record per person, assembled from every connected source — commerce, surveys, events, and engagement — instead of a row in each disconnected tool.
Identity resolution
Compass links identifiers — email, customer IDs, and more — so activity from different systems lands on the right person.
Extensible attributes
Add your own attributes without a schema migration. Declared survey answers and business-specific fields become first-class data you can query.
Event pipeline
A validated pipeline ingests events from your ecosystem, normalizes them, and writes them onto the customer timeline.
Commerce facts
Orders, products, and spend are stored as structured commerce facts you can use directly in audiences and campaigns.
Customer activity
A single chronological timeline shows what each customer did and when — across every connected product.
Merging customers is safe because it is reversible.
When two records turn out to be the same person, Compass merges them into one profile. If a merge was wrong, it can be undone — the process is designed to be reversible, so consolidating identities never means losing the ability to correct a mistake.
- Merge duplicate records into a single profile
- Reverse a merge if it was incorrect
- Source contributions remain traceable
- No destructive, one-way identity changes
See where every fact on a profile came from.
Profiles are built from events, and events carry provenance. That means you can trace an attribute back to the source and moment that created it — which is essential for trust, debugging, and answering customer questions.
- Attributes trace back to their source event
- A chronological, inspectable timeline
- Provenance retained as data flows in
- Answer "why is this on the profile?" precisely
Your customer data lives in your tenant — not a shared pool
Each business is a separate tenant with its own database. Customer records are isolated at the infrastructure layer, so one business's data is never mingled with another's.
A data foundation your whole platform can build on.
Connect Shopify, add surveys and events, and watch scattered activity become one intelligent profile.