Guide
Multi-region deployments
Quick answer
Treat local, staging, and production as separate key and browser-origin configurations in each deployment region.
Measure placement latency from each requesting region and keep the user flow responsive when a decision is delayed.
Use regional infrastructure deliberately and keep keys, origins, and observability aligned per environment.
Environment boundaries
Use separate test and live keys. Treat local, staging, and production origins as separate configuration entries.
Latency
Measure API v1 endpoint latency from every region that requests placements. Keep fallbacks fast when decisions are delayed.
Data minimization
Do not add region-specific data to job requests unless the config model documents it.
Need rollout review?
Start with the Server API. Use contact only when you need rollout review, enterprise coordination, or non-standard integration help.