How to use this library
Illustrative designs. Each entry is a planning pattern, not evidence of a delivered client project, and lists metrics to track, not results achieved. Validate identity, consent, latency and data quality against your own environment before building.
Pick a trigger, check the governance column, then define a baseline and holdout for the KPI before launch.
Use cases by trigger
| ID | Use case | Industry | Real-time trigger | Illustrative flow | Governance and validation | KPIs to measure |
|---|---|---|---|---|---|---|
| UC-01 | Real-time product interest | Retail | Product view without add-to-cart | Web SDK → AEP/XDM → RTCDP audience → AJO or approved channel | Check identity, consent, latency, and suppression | Qualified audience; eligible delivery; incremental conversion |
| UC-02 | Cart abandonment | E-commerce | Cart created without purchase | Commerce events → profile/audience → AJO journey | Exclude completed orders; deduplicate cart events | Recovery rate vs holdout |
| UC-03 | Checkout friction | E-commerce | Repeated checkout error or drop-off | Web/app events → CJA funnel → approved help content | Validate event taxonomy and error definitions | Checkout completion; support contacts |
| UC-04 | New customer onboarding | Banking | Account opened but onboarding incomplete | CRM/core feed → AEP profile → AJO | Eligibility, consent, identity, regulatory review | Completion rate; time to first value |
| UC-05 | Card activation | Financial services | New card issued but not activated | Approved status feed → audience → journey | Exclude blocked/fraud-flagged accounts | Activation rate; time to activation |
| UC-06 | Subscription renewal | SaaS | Renewal window opens | Billing + product events → profile → journey | Validate billing state; suppress cancelled accounts | Renewal rate; churn by cohort |
| UC-07 | Churn risk | Telecommunications | Usage decline plus service friction | Usage/CRM/service data → CJA + RTCDP | Use holdouts; correlation is not causation | Retention vs holdout; complaint rate |
| UC-08 | Service outage alert | Utilities | Confirmed outage in customer region | Operations event → affected segment → notification | Authoritative status, regional relevance, deduplication | Time to notify; repeat contacts |
| UC-09 | Flight disruption | Travel | Confirmed booking delay/cancellation | Booking status → profile → support journey | Fresh booking status and valid alternatives | Notification latency; self-service resolution |
| UC-10 | Pre-arrival journey | Hospitality | Booking enters pre-arrival window | Reservation feed → profile → AJO | Timezone, language, consent, booking changes | Check-in completion; add-on engagement |
| UC-11 | Appointment reminder | Healthcare | Appointment approaching or changed | Scheduling system → minimal approved data → reminder | Privacy review and minimum necessary data | Delivery; no-show rate vs baseline |
| UC-12 | Insurance document reminder | Insurance | Required document missing | Policy workflow → segment → notification | Avoid sensitive details in message | Completion rate; processing time |
| UC-13 | B2B lead follow-up | B2B | High-intent form and account-fit signal | Form + CRM → lead score → CRM task | Consent/contact policy; duplicate prevention | Speed to lead; qualified meetings |
| UC-14 | Buying committee insights | B2B technology | Several contacts engage with a topic | CRM + consented events → account analytics | Validate identity/account matching | Buying-group coverage |
| UC-15 | Loyalty tier recognition | Retail | Verified loyalty threshold crossed | Loyalty feed → profile → personalized experience | Validate points and effective date | Repeat purchase; tier engagement |
| UC-16 | Price-drop alert | Retail | Watched item price changes | Price event → preference lookup → notification | Fresh price, stock, market availability | Conversion; unsubscribe rate |
| UC-17 | Back-in-stock alert | Retail | Opted-in item returns to stock | Inventory event → preference → notification | Dedupe; stock race conditions | Purchase after alert |
| UC-18 | Content recommendation | Media | Recent consumption and declared preferences | Content events → profile → recommendation surface | Avoid sensitive inferences | Engagement; completion |
| UC-19 | Cross-channel path analysis | Multi-industry | Web/app/email/store transitions | AEP → CJA data view → journey analysis | Identity stitching and timezone checks | Path completion; channel insights |
| UC-20 | Consent withdrawal | Multi-industry | Preference changes to opt-out | Preference center → consent event → suppression | End-to-end propagation and audit trail | Suppression latency |
| UC-21 | Identity collision detection | Multi-industry | Unexpected profile merges | Identity diagnostics → data quality alert | PII controls and confidence thresholds | False merge rate |
| UC-22 | Schema drift monitoring | Data platform | Unexpected event field/type change | Ingestion validation → alert → owner | Version schema; trace dropped fields | Detection time; invalid-record rate |
| UC-23 | Streaming ingestion lag | Data platform | Event latency exceeds threshold | Pipeline telemetry → monitoring alert | Define SLA by source and event class | P95 latency; recovery time |
| UC-24 | Audience freshness | MarTech operations | Audience refresh deviates from expected timing | Job metadata → anomaly rule → alert | Account for seasonality and campaign changes | Freshness SLA; false alerts |
| UC-25 | Journey entry deduplication | Marketing operations | Repeated event tries duplicate entry | Event validation → entry policy → monitoring | Idempotency and re-entry rules | Duplicate entries |
| UC-26 | Frequency caps | Marketing operations | Customer approaches contact limit | Contact history → eligibility/suppression | Consistent cross-channel contact policy | Over-contact and opt-out rates |
| UC-27 | Post-purchase suppression | Retail | Purchase while promotion is pending | Purchase event → audience update → journey exit | Latency and retry testing | Irrelevant sends; suppression latency |
| UC-28 | Mobile-to-web identity | Digital product | Authenticated user changes devices | ECID + authenticated identity → identity graph | Consent, logout, shared devices | Journey completeness |
| UC-29 | Anonymous-to-known merge | Digital product | Visitor logs in or submits identifier | Web SDK identity event → merge policy | Test pre/post-login association | Profile completeness |
| UC-30 | Attribution reconciliation | Marketing analytics | Ad and analytics conversions differ | AEP/CJA + CRM/ad data → reconciliation | Align windows, identity, definitions | Variance explained |
| UC-31 | A/B test audience | Digital optimization | Eligible visitors enter experiment | RTCDP audience → test platform → CJA | Randomization, sample size, holdout | Incremental lift with interval |
| UC-32 | Service routing | Customer service | Verified priority case appears | CRM/profile → routing rules | Fairness, explainability, access controls | Resolution time; satisfaction |
| UC-33 | Fraud-safe suppression | Financial services | Approved risk flag blocks marketing | Risk status → suppression audience | Freshness and security boundary | Suppression accuracy |
| UC-34 | Branch appointment follow-up | Banking | Appointment booked, changed, or missed | Appointment system → profile → reminder | Timezone and status synchronization | Attendance; self-service rescheduling |
| UC-35 | Warranty onboarding | Manufacturing | Product registered with consent | Registration event → profile → onboarding | Validate product/customer linkage | Registration completion |
| UC-36 | Parts availability | Manufacturing | Requested part becomes available | ERP/inventory → service case → notification | SKU/location accuracy | Time to service completion |
| UC-37 | Energy usage insight | Utilities | Usage pattern reaches threshold | Meter feed → analytics → consented insight | Data quality and explainability | Insight engagement |
| UC-38 | Donation journey | Nonprofit | Donation completes or recurring gift fails | Donation platform → profile → acknowledgement/recovery | Payment status and respectful frequency | Gift recovery; donor retention |
| UC-39 | Course progression | Education | Learner completes module or stalls | LMS event → learning path → approved nudge | Student privacy and opt-in | Completion; time to milestone |
| UC-40 | Learner lab progress | Training | Learner finishes AEP/AJO/CJA checkpoint | LMS/lab status → trainer dashboard | Use cohort records only with permission | Lab completion; assessment change |
| UC-41 | Trainer capacity | Academy operations | Enrollment forecast exceeds mentor capacity | Enrollment + schedule → capacity dashboard | Forecast uncertainty; no placement promises | Mentor coverage; wait time |
| UC-42 | Campaign QA gate | MarTech operations | Configuration changes before release | Checklist/config export → validation → approval | Human approval and rollback | Pre-release defects |
| UC-43 | Data quality remediation | Data platform | Invalid records exceed threshold | Quality rules → quarantine/replay → owner alert | Preserve raw payload and traceability | Invalid rate; remediation time |
| UC-44 | Warehouse-CDP reconciliation | Data engineering | Warehouse counts differ from profile dataset | SQL checks → discrepancy report → issue ticket | Compare grain, window, exclusions, late data | Variance; time to explain |
| UC-45 | Event taxonomy governance | MarTech architecture | Team proposes new event | Schema review → approval → deployment | Naming, owner, version, privacy review | Reuse; breaking changes avoided |
| UC-46 | Personalized help | SaaS | User repeatedly hits known error | Telemetry → approved segment → contextual help | Validate error code; avoid sensitive inference | Self-service resolution |
| UC-47 | Renewal risk dashboard | Subscription | Renewal cohort enters risk window | Billing + usage + support → analytics dashboard | Transparent definitions and freshness | Renewal visibility |
| UC-48 | Campaign holdout | Marketing analytics | Campaign launches with randomized holdout | Assignment → delivery logs → outcome analysis | Prevent contamination; document exclusions | Incremental impact |
| UC-49 | AI incident triage | MarTech operations | Pipeline alert creates incident context | Monitoring → governed agent/MCP → human-approved ticket | Least privilege; no destructive autonomous action | Triage time; routing accuracy |
| UC-50 | Profile deletion workflow | Privacy operations | Verified deletion request approved | Privacy workflow → system inventory → confirmation | Identity verification and retention exceptions | Completion time; coverage |
Build one of these
Frequently asked questions
Are these client results?
No. They are illustrative design patterns for planning. We publish real client work only with written approval.
Which platforms do the flows use?
Mostly Web SDK, Adobe Experience Platform, Real-Time CDP, Journey Optimizer and Customer Journey Analytics, with approved delivery channels.