Routing
Edge Rules for Smarter Redirects
Device, geo, language, schedule, and weighted routing rules can personalize journeys without slowing down the click.
Lumen Editorial•
A rules engine belongs as close to the request as possible. Evaluating common rules at the edge keeps redirect latency low and reduces origin load.
The safest pattern separates fast, deterministic routing from durable event ingestion. The redirect should never wait for analytics to finish.
Fallback rules matter too: every smart branch needs a default destination that works when a condition cannot be resolved.