Real time performance monitoring tools provide the capabilities needed for detailed performance and advanced error analysis and the ability to correlate the results directly to business metrics, such as conversions, page views, and revenue.
This article covers the following topics:
Table of Contents Placeholder
How it Works
Use the following steps to add and configure the tag:
In Tealium iQ, click the Tags tab.
Click + Add Tag.
Enter Akamai in the search field.
Next to Akamai mPulse, click + Add.
In the Vendor Configuration field, enter the API key supplied by Akamai. This key is the unique identifier for your data.
Expand Advanced Settings. These settings are not required for most tags, but are needed for Akamai.
Set the Wait Flag to No. This means that the tag will be triggered as soon as the Tealium utag.js library file loads.
Set the Synchronous Load Type to No.
If set to Yes, the tag will not fire.
Use the following steps to apply load rules:
Click Next to advance to the Load Rules tab.
From Load Rules, click the Load on All Pages checkbox. This step is required to enable the tag to be bundled when configuring the Publish settings in the following steps.
Click Save in the upper right corner but do not publish.
Configure and Publish Settings to Optimize Performance
Use the following steps to configure and publish settings that will optimize tag performance:
Click Save/Publish in the upper right corner. The Save/Publish dialog displays.
In the upper right corner of the Save/Publish dialog, click Configure Publish Settings. The Publish Configurations dialog displays.
There are many Publish Settings options described on the Tealium support site. For Akamai mPulse, you can activate the following two (2) optional settings for Akamai to improve tag performance.
From the Publish Configurations dialog, click the General Publishing tab.
Scroll down to Performance Optimization and set the following to ON.
Bundle Tags Loaded on All Pages Setting this option to On ensures that any tags that load on the All Pages load rule are included inline in your utag.js file instead of in a separate, numbered file. Although your utag.js file will be larger, it will remove one (1) http request (server call) as the page loads.
Click Apply to close the Publish Settings dialog. You are now back at the Save / Publish dialog.
Publishing and Testing
As a final step, publish and test your new tag as follows:
From the Save/Publish dialog, click Save As.
Using Save As saves your change as a new version, which enables you to roll back your changes if needed.
Once the updated utag.js hits the CDN, you can see Akamai firing in the browser.
You can test that the tag is performing as expected by using a tag monitor, such as Ghostery, or you can view tag activity using your browser network monitoring tool. You will know that the tag is firing correctly if you see the following request firing:
Look for the request at http://c.go-mpulse.net/boomerang. The key displayed will match the API key you entered when you configured the Akamai mPulse tag.
... View more