Back to agent
Latency Tierlatency-tier.inter-session

Inter-session (5 min – 30 min)

Audience segment membership refresh on downstream activation systems; common floor for high-throughput programmatic systems where streaming cache updates are uneconomic.

confidence 90%v1reviewed Apr 26, 2026latency, micro-batch, audience, programmatic

Inter-session (5 min – 30 min)

Example. Audience segment membership update on a Demand Side Platform for an existing campaign.

Technical approach. Micro-batch updates. Systems with billions of events of throughput — like real-time programmatic bidding — periodically update because streaming updates of cache are complex (think dollars for design, operation, and infrastructure) compared to micro-batch approaches.

When this tier is the right floor. When the activation system itself enforces a refresh cadence (DSP audience uploads, partner data syncs), or when the cost of streaming cache invalidation exceeds the marginal value of sub-5-minute freshness.

Sources

Related

← Referenced by

  • instance-ofconcept.signal-to-activation-timeLatency taxonomy enumerates this tier
  • affects-cost-oflatency-tier.intra-sessionMoving up one tier ≈ 10× cost increase
  • applies-to-latency-tiermodality.posPOS typically batch-updates at 5-30 minute cadence
  • applies-to-latency-tiercapability.audience-segmentationMicro-batch segmentation (CDW SQL query running every 15–60 minutes) achieves inter-session segment membership latency — the standard freshness floor for composable CDP architectures without a dedicated stream processor.
  • applies-to-latency-tieruse-case.abandoned-cartOC-052. Abandoned cart activation is by definition inter-session: the cart is abandoned when the user ends their session without checking out. The first-reminder activation window (30–60 minutes post-abandonment) fires between the cart-add session and the user's next session. Source: use-case.abandoned-cart node body; cdp-recommendation-agent-md.