Problem Statement & CDP Context
Problem Statement & CDP Context for Customer Segmentation — understanding phase.
What we are designing
Retail marketers need audiences that react within minutes, not after tomorrow's warehouse job.
You are designing a customer segmentation platform for a multi-brand retailer with 50M known profiles, 200M anonymous device IDs, and 500M behavioral events per day. Marketers define audiences using rules (RFM, category affinity, cart abandonment) and ML scores (churn risk, LTV decile). Downstream systems—email, push, paid media, in-app personalization—need fresh membership with explicit consent.
Core capabilities interviewers expect
- Segment builder DSL with versioned definitions and audit history
- Real-time traits (last 24h behavior) plus batch traits (365-day aggregates)
- Identity resolution linking device → account without unsafe merges
- Activation via REST, streaming exports, and partner sync (Meta/Google)
- Suppression lists honoring opt-out within seconds
Scale anchors (state these aloud)
| Signal | Assumption |
|---|---|
| Active segment definitions | 12,000 (10% change weekly) |
| Membership evaluations/day | 2B profile-segment pairs (materialized incrementally) |
| Activation lookups/sec (peak) | 180k (Black Friday email send) |
| Trait catalog | 4,000 attributes (60% event-derived) |
Why this beats a generic "analytics" answer
Segmentation is operational, not exploratory. Wrong membership costs campaign spend; stale membership erodes trust. Your design must show evaluation semantics and failure degradation, not only storage boxes.
Key Highlights
- •Designing a customer segmentation platform for a multi-brand retailer: 50M known profiles, 200M anonymous device IDs, 500M behavioral events/day; marketers define audiences via rules (RFM, category affinity, cart abandonment) + ML scores (churn, LTV decile), downstream email/push/paid-media/in-app need FRESH membership with explicit consent
- •Core capabilities: a segment-builder DSL (versioned + audit history), real-time traits (last 24h) + batch traits (365-day), identity resolution (device -> account without unsafe merges), activation (REST + streaming + Meta/Google partner sync), suppression honoring opt-out within seconds
- •Scale anchors: 12K active segment definitions (10% change weekly), 2B profile-segment evaluations/day (materialized incrementally), 180K activation lookups/sec peak (Black Friday send), 4K trait catalog (60% event-derived)
- •Why this beats a generic 'analytics' answer: segmentation is OPERATIONAL not exploratory — wrong membership costs campaign spend, stale membership erodes trust; the design must show evaluation semantics + failure degradation, not just storage boxes
Section Rescue Kit
Buzzwords to use:
Safe statements:
- "For problem, I would measure freshness and membership accuracy before optimizing cost."
- "If load doubles, I degrade on-demand segments first while protecting paid activation caches."