Skip to content
Customer Profiles

Build a customer record around the person, not the application.

Most tools store a copy of the customer per app. Compass keeps one record per person — resolved from every source you connect, with the full history of what they bought, received, and agreed to.

Identity

One person, one record

Compass resolves the identifiers scattered across your systems into a single customer — and keeps the work reversible so a bad match is never permanent.

Identity resolution

Emails, orders, sign-ups, and events resolve to a single customer — so one person is one record, not a scatter of half-matching rows.

Provider-namespaced identities

Every external identifier keeps its source. A Shopify customer ID and a survey respondent ID live side by side, each labeled by where it came from.

Reversible merges

When two records join, the merge is recorded and reversible. If a match was wrong, you can split it back apart without losing history.

Customer facts

Facts Compass can compute, and attributes you define

Customer facts are the derived truths about a person — lifetime value, order count, days since last purchase — computed from the underlying data rather than typed in by hand. On top of those, extensible attributes let any connected application add its own fields to the profile without a database redesign.

  • Derived customer facts kept current as new data arrives
  • Extensible attributes new apps can add without migrations
  • Declared data from surveys sits alongside computed facts
  • Every attribute is queryable in the Audience Builder
A single timeline

Everything the customer did, in one place

Commerce, engagement, consent, and ecosystem activity all attach to the same record — so you never reconstruct a customer from four different exports.

Commerce history

Orders, products, values, and cadence — the purchase timeline that tells you what someone actually buys and how often.

Engagement history

Sends, opens, clicks, and campaign membership, so every message a customer received is part of their record.

Consent history

What a customer agreed to, when, and through which channel — kept as a durable record you can act on and audit.

Ecosystem activity

Signals from connected products — surveys, events, and other Compass-connected apps — flow into the same timeline.

Why it matters

A profile you can trust enough to act on

  • Audiences target real people, not duplicated rows
  • Consent travels with the customer, so sending stays safe
  • New applications enrich the same record instead of forking it
  • History is preserved, so you can always explain a decision

Your business already has customer intelligence. Compass helps you use it.

Start with Shopify, connect your ecosystem, and let Compass turn scattered activity into audiences, campaigns, and journeys.