Omnichannel Loyalty Profile Identity Resolution Verification
Cleanse and verify customer identity merges across physical point-of-sale, e-commerce, and loyalty club databases.
Use this checklist when executing a customer master data consolidation or CDP identity resolution job. It validates contact formatting, deduplication confidence, and consent state preservation.
Role: Principal Customer Data Platform (CDP) Architect with specialization in retail identity resolution and consumer privacy compliance.
Context
- Merchant Brand: {{merchant_brand}}
- Upstream Identity Silos: {{crm_data_sources}}
- Identifier Precedence Hierarchy: {{matching_key_hierarchy}}
- Data Cleansing Standard: {{pii_sanitization_standard}}
- Regulatory Policy: {{consent_policy_version}}
- Resolution Match Threshold: {{merge_confidence_cutoff}}
Task
Develop a pre-merge and post-merge data cleaning checklist to eliminate duplicate shopper profiles, format consumer identifiers, and preserve customer state for {{merchant_brand}}.
Method
- Validate standardized normalization across all email addresses, physical postal codes, and phone numbers in accordance with {{pii_sanitization_standard}}.
- Detect and isolate invalid placeholder phone numbers (e.g., 000-000-0000) and throwaway email domains across {{crm_data_sources}}.
- Execute deterministic match checks across primary keys specified in {{matching_key_hierarchy}} before running probabilistic models.
- Evaluate probabilistic merge candidates against {{merge_confidence_cutoff}}, flagging edge cases for manual review.
- Separate shared household accounts from unique individual identities based on first name and birth date discrepancy rules.
- Audit consent flags and opt-out statuses under {{consent_policy_version}} to verify that the most restrictive opt-out survives the merge.
- Check points balance, tier status, and transaction history continuity across merged survivor master records.
Constraints
- Merge criteria MUST NOT consolidate records with active consent contradictions without defaulting to the opt-out state.
- Verification items MUST include explicit roll-back and survivor record assignment rules.
- Exclude all unmasked live PII examples from documentation output.
- Format checklist items into clear inspection gates with defined pass metrics.
Output format
Generate a four-phase Markdown verification checklist: Phase 1: Contact Field Standardization, Phase 2: Deduplication & Merge Evaluation, Phase 3: Privacy & Preference Reconciliation, and Phase 4: Master Record Integrity Sign-off. Use checkbox format (- [ ]) with columns or inline labels for 'Verification Objective', 'Validation Logic', and 'Threshold'.
Self-review
- Ensure all variables ({{merchant_brand}}, {{crm_data_sources}}, {{matching_key_hierarchy}}, {{pii_sanitization_standard}}, {{consent_policy_version}}, {{merge_confidence_cutoff}}) are referenced.
- Confirm clear guidance is given for surviving master record selection.
- Check that consent preservation rules strictly adhere to the constraints.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.