Managing Traffic Routing Flows as Production Configuration

Put visits in one flow when they share the same public route, incoming source fields, page pair, rules, and owner. Create separate flows when a market or connected system needs its own release schedule, while avoiding needless copies that leave staff unsure which setup is live.

Record White Page and Target Page ownership, health expectations, variant weights, and delivery constraints. Validate both destinations before activation because a sound rule cannot compensate for an unavailable or incompatible page.

List deterministic filters, allow and deny exceptions, ML scoring, fallback behavior, and any target distribution in the order they affect a request. Event reasons should expose the decisive step and the configuration version.

Prepare a diff, acceptance cases, owner, monitoring window, and rollback state before editing a live flow. Avoid simultaneous changes to links, pages, and thresholds when the team needs to determine which adjustment caused a shift.

Stop acquisition first, observe late visits, preserve required records, and choose the response for old public links. Remove domain mappings and dependent assets only after the owner confirms that rollback or audit needs have ended.