Akamai is the primary external hosting option. Akamai provides you with a reliable hosting experience and is the simplest option to implement. Akamai provides the greatest third-party infrastructure dependencies, such as DNS lookup, faster load times, and faster round-trip delivery times.

The Akamai hosting option allows you to store your web property library files on Adobe’s Edge CDN, which sits on the Akamai architecture. This option allows you to install the Embed codes in your page templates and quickly get up and running with dynamic tag management without involving your internal IT teams and servers.

Note: After July 31, 2015 Adobe will no longer support Amazon S3. Your dynamic tag management libraries on Amazon S3 will continue to be served until December 31, 2015, but in a read-only state. Any changes made in dynamic tag management will no longer be reflected in these files.

To deploy additional changes to your site after July 31, 2015, you must select one of our other hosting options. Self-hosting (FTP Delivery or Library Download) is always the suggested best practice, but our 3rd-party Akamai hosting is a world-class option as well.

Akamai Cache Control Headers

Cache control headers are automatically set for libraries hosted on Akamai (assets.adobedtm.com).

  • Production builds: Cache control headers are set to 60 minutes
  • Staging builds with "-staging" in the filename: Cache control headers are set to 0 minutes
Note: It is up to browsers to receive and respect the cache control headers. Some browsers might ignore them.

Why Choose Akamai Hosting for Library Files?

When you choose the Akamai option in the Embed section of dynamic tag management, it means that your dynamic tag management library files are served to your visitors from Adobe’s Edge CDN, which runs on Akamai architecture.

Akamai is robust when serving content to a global, high-volume audience of Web visitors. Akamai runs redundant networks of load-balanced, geo-optimized nodes to serve content as quickly as possible to visitors wherever they are located throughout the world.

Specifically, Akamai runs more than 137,000 servers in 87 countries within more than 1,150 networks. In terms of redundancy, Akamai does not just route from one server to another, Akamai routes from one node of servers to another node of servers as-needed. In other words, each node consists of multiple servers for redundancy within a node, so a box going down is not an issue because he other boxes in the node take over. If a node goes down, Akamai serves from the next closest one, with the same cached content. Nodes are dynamically selected based on visitor location, traffic load, and other factors so content is consistently served from the best local node for each visitor.

Can I Avoid Errors in Case of Akamai Unavailability?

No. Dynamic tag management can do nothing from the client side if the library is unavailable. However, it is extremely unlikely that Akamai would be unavailable.