Skip to content

Customer Data use cases
Preview

These guides show common patterns for integrating with the Customer Data Service from your application. They capture visitor activity even before an account is created, and unify it into a single profile that follows the user across sessions, devices, and applications.

Note

The Customer Data Service is currently in Preview. Some features may be subject to changes in future releases.

Before you begin

  • Enable Customer Data Service for your organization.
  • A machine-to-machine (M2M) application is registered for your backend to call the Customer Data Service APIs, granted the internal_cds_profile_create, internal_cds_profile_update, and internal_cds_profile_view scopes and configured to issue tokens with the iam-cds audience.
  • The profile attributes that your activity maps to are defined, each with the merge strategy it should use.
  • The unification rules that decide when two profiles are the same person are defined.

Use cases

Read Use this when
Unify anonymous and registered profiles A visitor interacts anonymously, then signs up, and their activity is consolidated into the new profile.
Accumulate data across multiple devices A user interacts anonymously across multiple devices and then signs in, and their activity is consolidated into a single profile.
Stitch user profiles across websites A visitor interacts anonymously across multiple applications or domains, and their activity is consolidated into a single profile based on a shared identifier.