ComposableStack.AI CDP
Back to agent
Latency Tierlatency-tier.inter-page

Inter-page (100 ms – 10 s)

Edge-decisioned next-page personalization. The challenge is propagation across modalities, since the edge response may not yet be reflected in batch systems.

confidence 90%v1reviewed Apr 26, 2026latency, edge, decisioning, personalization

Inter-page (100 ms – 10 s)

Example. Next-page personalization. Transactional emails like password reset. Room-key delivery for online hotel check-in.

Technical approach. Edge decisioning (e.g. Fastly, AEP Edge Decisioning). The event emitted interacts with edge resources and immediately responds with varying behavior.

Operational consideration — propagation across modalities. When the same activation needs to surface across multiple channels with different latency budgets, the architecture must reconcile them. Example: an edge interaction yields a Free Ice Cream Cone coupon that's immediately visible on the user's mobile phone, but the Point-of-Sale terminal at the redemption location updates only every 30 minutes. The architecture must make the disparity acceptable to the use case.

Historical note. This was a key role of Adobe Audience Manager — the combination of traits and trait state changes implies customer progression through a journey (e.g. Mortgage Interest → Mortgage Product Selection → Info Submission → Mortgage Quote).

Common use cases. Transactional emails (password reset), online hotel check-in room-key delivery, next-page personalization.

Sources

Related

This node →

← Referenced by

  • instance-ofconcept.signal-to-activation-time— Latency taxonomy enumerates this tier
  • affects-cost-oflatency-tier.intra-page— Moving up one tier ≈ 10× cost increase per Real-Time Clarity rule of thumb
  • applies-to-latency-tieruse-case.transactional-email— Password reset / receipt expects sub-10s delivery
  • applies-to-latency-tiermodality.web— Web supports edge-decisioned inter-page
  • applies-to-latency-tiermodality.mobile-app— Mobile apps support fast next-screen activations
  • prerequisite-oftech-dim.dev-team.backend-stream-processing— Streaming or edge team is required for inter-page
  • applies-to-latency-tiervendor.fastly— Fastly is reference architecture for inter-page edge decisioning
  • applies-to-latency-tiermodality.email— Transactional email at inter-page tier
  • applies-to-latency-tieruse-case.hipaa-safe-performance-marketing— OC-116. The tracking-layer PHI suppression operates server-side synchronously with page events. De-identified conversion events forwarded via Google/Meta CAPI are delivered within seconds of the originating page event — consistent with the inter-page latency tier. Pattern: same as use-case.transactional-email (server-side event → near-immediate delivery = inter-page). The downstream batch audience export (lookalike seeds, suppression lists) is secondary to the primary real-time tracking architecture.