Standardize names and addresses and mint deterministic match keys
When the same customer appears three different ways across systems and mail bounces on half the addresses.
- Transformation
Larger outcome
8 RecipesCustomer 360 is not one Recipe. It is too broad to have a single acceptance contract, so it is assembled: standardise, resolve identity, then add the measures the view is actually for. Adopt the ones you need and add your own source, privacy and survivorship requirements on top — the Recipes below stay exactly what they are in the rest of the Cookbook.
When the same customer appears three different ways across systems and mail bounces on half the addresses.
When three source systems each carry their own customer id and every report double-counts the same person.
When revenue by customer is split across a dozen subsidiaries and nobody sees the group total.
When "what's our churn rate" gets three different answers depending on who is asked.
When segmentation runs in an analyst's notebook and nobody else can rerun it.
When the acquisition-payback conversation lacks an LTV figure anyone trusts.
When a customer who opted out of email still gets a marketing send from a different system.
When product analytics can't be reproduced outside the vendor's own dashboard.