Delivery
Cache variations
The same URL can legitimately need different cached responses for different visitors. Variations make that split explicit instead of letting one region, device, or campaign accidentally receive another's cached copy. This topic covers variation rules, the per-domain scoping of both variation and cache rules, and how to clear a single variation.
How it works
- Variations can key on cookie, country, header, or other request conditions you define
- Cache rules are scoped per domain, so one domain's variation setup doesn't affect another
- Each variation is tracked as its own entry so it can be purged independently
Good to know
- Getting variation keys right up front avoids subtle bugs like a country-specific page being cached and served to the wrong region
- At most eight bounded variation rules can be active at once
- Matched header, cookie, IP, or user-agent values require a matching condition, otherwise delivery bypasses cache
- Query strings already vary cache keys by default — ignore tracking parameters instead of duplicating raw values
- Variations decide which cached copy is used; Cache rules decide whether it is stored and for how long