Most companies don't have a customer data problem in the abstract. They have it at specific moments: when a prospect becomes a buyer, when a buyer calls support, when a loyal customer churns quietly. At each stage, a different system captures different data, under different definitions, with no guarantee the records ever resolve to the same person.
That's the core MDM problem in customer data, and documenting the customer journey is one of the clearest ways to surface it.
What the journey stages reveal about your data
Each stage of the customer journey tends to live in a different system with a different data model. In the awareness stage, marketing platforms like Marketo or HubSpot capture anonymous activity and email addresses with no stable unique identifier, making duplicates common. By consideration, a CRM like Salesforce has created a Lead record -- but the Lead and Contact models often don't match, and the link to the original marketing record is fragile. At purchase, an ERP or eCommerce system creates an Account or Order record, frequently without connecting back to the CRM record that preceded it. Post-purchase, service platforms like ServiceNow or Zendesk open cases tied to an order or account number, not to the person. And in advocacy stages, NPS scores and referral data sit in survey or loyalty tools that are rarely joined back to any customer record at all.
When these systems don't share a common customer identifier, the journey exists only in the customer's experience -- not in your data. You can't answer basic questions: How many touches before first purchase? What's the support load for high-value customers? Which acquisition channel produces advocates?
What MDM documentation actually requires
Documenting the customer journey from an MDM perspective means more than drawing a journey map. It means defining "customer" at each stage -- is a lead a customer? Is a contact tied to an account? These aren't semantic questions; they determine what gets a golden record and what doesn't. It means mapping source systems to journey stages: for each stage, which system creates the record, what attributes does it capture, and what identifier does it use? It means establishing survivorship rules across stages -- when a lead converts to a contact in Salesforce, which attributes carry forward, and when does the MDM hub update? And it means identifying unresolved identity gaps: where in the journey does the record break? Anonymous web visitor to known lead is a common one. So is a phone support caller who can't be matched to a CRM account.
Why this matters operationally
Inconsistent customer data doesn't just produce reporting problems. It creates operational failures: support agents who can't see purchase history, sales reps who don't know a prospect already filed three complaints, marketing that re-acquires existing customers as if they're new.
MDM's job is to make the record follow the customer through the journey, not stop at the edge of each system's ownership. Documenting the journey is the first step to knowing where the record breaks