Customer Data Platform

A customer data platform that earns its licence: use cases first, a tracking plan and identity rules, consent that follows the profile, governed audiences and destinations, and measured personalisation.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Customer Data Platform, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

207

Starter tasks

📊 Data & Analytics

Customer Data Platform

Collecting customer events and profiles into one platform for segmentation, personalisation and consistent identity across channels.

  1. Customer data use case inventory
  2. Customer data source and touchpoint map
  3. Packaged versus composable CDP decision
  4. CDP vendor shortlist and proof of concept
  5. Customer event tracking plan
  6. Identity resolution rules and identifier priority
  7. Consent signals mapped to profiles and destinations
  8. CDP ownership and operating roles
  9. Profile trait naming and schema conventions
  10. Identifiable customer share baseline
  11. Weekly audience request queue
  12. Weekly tracking plan violation review
  13. Monthly identity graph health check
  14. Destination sync failure triage
  15. Monthly consent reconciliation across destinations
  16. Quarterly audience and trait pruning
  17. Tracked profile volume and licence cost review
  18. Tracking plan change control for releases
  19. Access and erasure requests across the CDP
  20. Quarterly CDP stakeholder review
  21. Deterministic and probabilistic identity stitching
  22. Writing computed traits and audience logic
  23. Client-side versus server-side collection
  24. Browser tracking prevention and first-party identifiers
  25. Consent and lawful basis basics for CDP users
  26. Querying CDP event and profile tables in the warehouse
  27. Testing an audience before it goes live
  28. Server-side event forwarding migration
  29. Mobile app SDK instrumentation
  30. Offline and in-store purchase ingestion
  31. Support tickets and CRM history in profiles
  32. Existing customer suppression in paid media
  33. Website personalisation from live traits
  34. Retiring legacy tags and duplicate pixels
  35. Trait retention and expiry rules
  36. Historical customer data backfill
  37. CDP go-live for the first two use cases
  38. First personalised campaign launch with a holdout
  39. Annual CDP contract renewal
  40. Annual CDP value readout to sponsors
  41. Starter CDP for a marketing team without engineers
  42. Multi-brand and multi-region CDP rollout
  43. Migrating from one CDP to another
  44. Account-level profiles for B2B buying groups
  45. Loyalty programme members in the CDP
  46. Onboarding a new CDP user
  47. Real-time profile lookups for in-session decisions
  48. Incrementality testing for CDP audiences
  49. Data clean room collaboration with partners
  50. Household and shared-device identity

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Customer data use case inventory

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most CDP programmes that disappoint were bought for a capability rather than a problem, and end up as an expensive event pipe.

First tasks

  • Book thirty-minute interviews with the leads of marketing, product, service and analytics
  • Write each use case as an outcome in a named channel with a requesting owner
  • Score each use case for value and for data you do not yet collect
  • Get sign-off on the two or three launch use cases from their owners
  • Rescore the use case list against what has launched and what was learned @recurring(yearly)

Customer data source and touchpoint map

Customer data usually sits in eight to fifteen places: the website, apps, the email platform, the e-commerce or billing system, the CRM, support desk, point of sale and ad platforms. A single map of every source, the identifiers each holds and how often it can send data shows which launch use cases are realistic and which need new collection first.

First tasks

  • List every tool your teams log into that holds customer names, emails or IDs
  • Ask each system owner which identifiers their records carry
  • Record whether each source offers a native connector, an API, a file drop or a warehouse table
  • Mark the data each launch use case needs that no source provides yet
  • Update the source map for added and retired tools @recurring(yearly)

Packaged versus composable CDP decision

A packaged CDP stores its own copy of profiles and comes with collection, identity and audiences built in, while a composable setup keeps profiles in your warehouse and adds collection and activation tools around it.

First tasks

  • Ask the data team how many customer tables in the warehouse are tested and documented
  • Note which launch use cases need profile updates within seconds rather than hours
  • Sketch the components each architecture needs for the launch use cases
  • Estimate three-year licence, infrastructure and staffing costs for both options
  • Write the decision and the triggers that would reopen it

Make it yours.

Install Customer Data Platform, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.