ComposableStack.AI CDP
Back to agent
Latency Tierlatency-tier.intra-day

Intra-day (30 min – 6 h)

Transactional follow-ups tied to a single-day journey; classic batch-processing window.

confidence 90%v1reviewed Apr 26, 2026latency, batch, transactional

Intra-day (30 min – 6 h)

Example. Trip receipt.

Technical approach. Batch processing — typically scheduled jobs running on the cloud data warehouse with downstream activation via reverse-ETL or vendor-native destinations.

Why this is comfortable territory. Most cloud data-warehouse-based composable stacks naturally land here without exotic infrastructure. Cost-per-activation drops sharply versus streaming tiers above.

Sources

Related

← Referenced by

  • instance-ofconcept.signal-to-activation-time— Latency taxonomy enumerates this tier
  • applies-to-latency-tiermodality.email— Marketing email at intra-day tier
  • applies-to-latency-tieruse-case.loyalty-program-personalization— OC-054. Loyalty personalization requires intra-day freshness: POS spend events must reach the CDW profile and trigger tier/points recalculation within hours so that offer-presentation (in-app, next visit) reflects current loyalty status. Daily-batch loyalty is below-acceptable for modern programs where members expect same-day acknowledgment of qualifying spend; intra-session latency exceeds the architecture requirements (triggers are cross-channel, not within the active session).