Cache Tag

Tag your cached content to purge it with a single request.

How it works

Cache tags are a convenient way to update cached content on the edge servers. If you have a collection of objects that are refreshed at the same time, you can associate them with a single cache tag. With cache tags you can label cached content, and delete or update that content by referencing a tag, rather than a URL or CP code. This gives you a new level of control while making the purge process simpler, faster, and more efficient.

Features and options

Each instance of the Cache Tag behavior can only take a single value, which can be a variable. If you want to specify more cache tags for a property, add multiple instances of this behavior to a rule. Values of all Cache Tag behavior instances specified for a property are combined.


You can't tag content that's already cached or when using NetStorage as your origin.

FieldWhat it does
Tag nameSpecifies the cache tag name for the content that's about to be cached. A tag can contain alphanumeric characters (a-z, A-Z and 0-9), and the following special characters: &, ', ^, -, $, !,

Caveats and best practices

Consider these points before you add this behavior to your property:

  • Cache Tag doesn't work with Quick Retry. Cache Tag is not compatible with the multi-threaded store entry functionality that the Quick Retry behavior uses. Don't include both behaviors in a rule for the same request.

  • You can use this behavior in one of two ways. You can either use it to directly add a cache tag to the object when it's first put into the edge servers' cache, or define tags at the origin server level with an Edge-Cache-Tag header.

Related topics

See Purge content by cache tag and Variables overview.