Why batch segments are too slow for some personalization
Section titled “Why batch segments are too slow for some personalization”Traditional personalization uses segments computed from historical data. A visitor browses products today, gets added to a segment overnight, and sees personalized content on their next visit tomorrow. For many use cases, this delay is acceptable.
But some moments demand instant response. A visitor reads three articles about enterprise security in a single session — they should see enterprise-focused CTAs on the next page, not after their next visit. A shopper adds a high-value item to the cart — cross-sell recommendations should update immediately, not after a batch segment refresh.
Real-time personalization requires ODP to evaluate behavioral signals within the active session and CMS to render personalized content based on those signals without waiting for batch processing.
Architecture overview
Section titled “Architecture overview”┌────────────────────────────────────────────────┐│ Visitor Session: Live Behavior ││ Page views, clicks, cart actions, searches │└───────────────────────┬────────────────────────┘ │ events stream in real time ▼┌────────────────────────────────────────────────┐│ ODP: Real-Time Segment Evaluation ││ Evaluate segment rules against live events: ││ "3+ product views this session" = true ││ Updated within seconds, not overnight │└───────────────────────┬────────────────────────┘ │ current segment membership ▼┌────────────────────────────────────────────────┐│ CMS: Visitor Group Resolution ││ Visitor groups query ODP real-time segments ││ Content blocks swap based on live state │└────────────────────────────────────────────────┘Step 1: Instrument real-time event tracking
Section titled “Step 1: Instrument real-time event tracking”Configure the ODP JavaScript SDK to send behavioral events as they happen:
- Page view events with content category and page type metadata
- Product interaction events — view, add to cart, wishlist
- Engagement events — video play, document download, form start
- Search events — query terms and result interactions
Each event should fire within milliseconds of the user action. Batching delays (common in analytics tools) defeat the purpose of real-time personalization.
Step 2: Create real-time segments in ODP
Section titled “Step 2: Create real-time segments in ODP”Build ODP segments with rules that evaluate within-session behavior:
| Segment | Rule | Evaluation |
|---|---|---|
| Active Product Browser | 3+ product views in current session | Real-time |
| Content Consumer | 2+ article reads in current session | Real-time |
| High-Intent Shopper | Cart value > $200 in current session | Real-time |
| Search-Driven | 2+ search queries in current session | Real-time |
Configure these segments for real-time evaluation in ODP. The segment membership updates within seconds of qualifying behavior.
Step 3: Map real-time segments to CMS visitor groups
Section titled “Step 3: Map real-time segments to CMS visitor groups”Create CMS visitor groups that reference the ODP real-time segments. When a visitor qualifies for a segment mid-session, the next CMS page load evaluates their updated segment membership and renders the appropriate content variation.
Key consideration: the personalization takes effect on the next page load after the qualifying behavior, not on the current page. For single-page applications, trigger a re-evaluation of visitor groups after significant user actions.
Step 4: Design the personalized content blocks
Section titled “Step 4: Design the personalized content blocks”Create content variations that make sense for in-session context changes:
- Active Product Browser: Show a “Continue browsing” section with recently viewed products
- Content Consumer: Surface a related content sidebar or newsletter signup
- High-Intent Shopper: Display financing options, loyalty program benefits, or free shipping thresholds
- Search-Driven: Offer guided navigation or filtered category pages
Keep variations subtle and helpful. Abrupt layout changes mid-session can feel intrusive.
Step 5: Monitor latency and accuracy
Section titled “Step 5: Monitor latency and accuracy”Track two metrics for your real-time personalization:
- Segment evaluation latency — the time between the qualifying event and segment membership update (target: under 5 seconds)
- Personalization accuracy — the percentage of page loads where the visitor group correctly reflects the visitor’s current segment
If latency exceeds your threshold, review event batching configuration and ODP processing settings.
When to use this pattern
Section titled “When to use this pattern”Real-time personalization adds value when in-session behavior strongly predicts intent and when the content response to that intent is meaningfully different from the default. For most content pages, batch segments from prior visits are sufficient. Reserve real-time personalization for high-value conversion paths where seconds matter.