Use cache tag nomenclature
Cache tags are scoped at an account level. If you have multiple groups using functionality within your account or you’re testing on multiple local environments, follow some kind of nomenclature that helps distinguish tags created by these different groups.
This will primarily benefit in preventing cache tag collisions such as a scenario where multiple groups create the same tag and purge the content of others.
For example, consider an online apparel store that sells both clothes and shoes
through two different departments, both of which fall within the same Akamai
account. Assume both departments run a promo and tag some of their content as
SALE. Now if the clothing department
decides to purge all content tagged as
SALE, this will also purge content tagged by the shoes department.
To avoid this scenario, use a nomenclature within departments. This could be as simple as
starting each tag with
<DepartmentName>. So in this case, to prevent any
tag collision, there are two different tags, one for
CLOTHES_SALE and the
Similarly, you may want to test purging content on different local origins. We’ve seen power
users leverage tag appending mechanisms on their end. For example, an object to be tagged with
SALE can now have multiple tags associated with it such as
relevant tags can be purged in the relevant environments.