Customer Event-Based Engine (CEBE)

An event-driven, unified data layer that consolidates customer identity, attributes, and behavioral events from every Qontak module into a single authoritative Central DB — the foundation for intelligent segmentation, marketing automation, Agentic AI memory, and customer health scoring. Today customer data lives in silos (each module writes its own DB), so every new intelligence feature re-solves cross-module data access from scratch. CEBE is a multi-phase, cross-squad initiative: Q3 2026 stands up the core infrastructure with CDP customer-data and Marketing (Broadcast + Ads) events as the first two sources; Q4 2026 adds Communication/Service/Loyalty; Q1 2027 adds B2B Sales/Commerce.

Scope Changes

Engineering surfaces this initiative touches (controlled vocab: Backend · Frontend · Mobile · Infra · Data · Design · Docs · None). Aggregate of this initiative's PRDs; mirrors the scope_changes frontmatter above.

• Backend — contact-service: Event Adapter Layer (ingestion + ContactResolver identity resolution keyed on qontak_customer_id + idempotency + PII masking); CDP emits customer.created/updated + segment.entered/exited; Broadcast/Ads service emits standardized campaign.* + ad.* events to the adapter contract.
• Data — Central DB schema (event-level + customer-level aggregation), retriever/metrics materialization (e.g. % reply rate, % ads conversion, ROAS), documented query approach for segmentation + marketing automation, 12-month historical backfill, joint BI/Data feasibility assessment.
• Infra — streaming/queue capacity + async buffer to hold the <5s p99 propagation SLA with zero loss; monitoring & alerting on propagation latency and loss reconciliation.
• Docs — standardized event-schema spec + event-push guide socialized to all squads at end of Q3 (squads self-serve like Mixpanel).

QA Lane

Lane B — keeps a human QA gate. The 2026-Q3 scope is research/assessment/analysis rather than shippable feature work, and the downstream engine is real-time event streaming. No E2E test specs exist for this initiative yet, so the Lane-A entry bar (100% E2E, spec-mapped coverage) is unmet regardless. Classified 2026-06-29.

Contents

• prds/ — Product Requirements Documents (1 anchor + 2 child Phase-1 PRDs)
• rfcs/ — Request for Comments (joint Eng + Data RFC — TBD)
• tests/ — Test plans
• delivery/ — Timeline, status updates, decisions

Knowledge Graph

• prds/prd-customer-event-based-engine-cebe-anchor.md is anchor of → prds/prd-cebe-core-infrastructure-cdp-customer-event.md (TECH — CDP + BI/Data lead) + prds/prd-cebe-marketing-event-source-broadcast-ads.md (SUPPORT — Broadcast squad).
• Phase 1 ships under one shared Jira Epic TF-3302; the Broadcast contribution is filtered via the Owning Squad field.
• Marketing SUPPORT track depends on → the Core Infrastructure TECH track (standardized event schema + Event Adapter must be stable in staging before Broadcast/Ads emission can finalize).
• Confluence source of truth: CEBE — ANCHOR · Core Infra (TECH) · Marketing Broadcast & Ads (SUPPORT).

Test specs not yet authored. RFC (joint Eng + Data) is pending — required before BUILD.