Module quiz

1. To unify disparate data sources into a single customer profile for activation and engagement.
2. To manage customer loyalty programs across multiple platforms.
3. To create marketing campaigns based on demographic data only.
4. To replace CRM systems entirely.

1. To store customer purchase history.
2. To map relationships between different identity namespaces and unify customer interactions across channels.
3. To generate marketing campaigns based on customer preferences.
4. To enforce data governance policies.

1. The data is stored in a relational database for manual processing.
2. The data is automatically deleted after 30 days.
3. The data is centralized and standardized into a unified profile view, accessible in JSON format.
4. The data is only available for offline analysis.

1. To replace manual segmentation processes.
2. To aggregate profile behavior data into values for personalized communication and audience segmentation.
3. To enforce data governance policies.
4. To create new identity fields for customer profiles.

1. Labels that classify data based on privacy considerations and contractual obligations.
2. Policies that describe allowed or restricted marketing actions for specific data.
3. Identity graphs that unify customer profiles across multiple channels.
4. Enforcement mechanisms that prevent non-compliant data usage.