Experience Analytics captures and manages visitor interactions on your websites and mobile apps. Any of your applications that have data in the Akamai Content Delivery Network (CDN) can be configured in to receive session traffic for customer behavior analysis.

Configuring the Akamai service

When you use the Akamai CDN with Experience Analytics, be mindful of the following prerequisites and best practices:

• To use the Akamai connector, you must already be using Akamai or you must have already purchased the connector as an offering (OEM). Akamai permissions must be signed.
• Include your Akamai stakeholder in all meetings and correspondence that is related to the -Akamai integration. Akamai stakeholder input is crucial throughout the sales, sizing, and onboarding effort and can improve the likelihood of a successful integration.
• Remain engaged with the Akamai stakeholder even after the integrated environment is up and running. The volume and type of data that flows through the Akamai CDN can fluctuate at anytime. Knowing about increased volume and load can help you adjust as needed.
• When you use the Akamai Console (LUNA portal), you must identify the DOMAINS, URLs, and TRAFFIC TYPES to be sent from Akamai to Experience Analytics (Tealeaf). To do this, you must opt in to the DOMAINS, URLs, and TRAFFIC TYPES in the Akamai Console (LUNA portal).
• The type of traffic that is sent from Akamai to can impact system performance. In general, the following types of traffic do not have a negative impact on system performance:
  • Non JavaScript™ traffic
  • Non-Document Object Model (DOM) traffic
  • Ajax calls
  Some traffic types can have a negative impact on system performance. Do not send the following types of traffic from the Akamai CDN to :
  • Static content such as:
    • images
    • PDF files
    • JPG files
  • Domains with PCI data

    is not PCI-compliant. PCI data must be filtered out of the domain before it is sent from Akamai to .

  • UISDK, DOM, or browser files.
• Session sampling

  Use the session sampling capability to test a subset (10 percent for example) of the traffic that flows from Akamai to . Testing a subset, rather than all of the Akamai traffic at once, allows you to assess and fine-tune traffic flow capacity before you go to production.

Map URLs to applications

For each application that receives data from Akamai, you enter the URLs from which the application receives the data. This might be all of the URLs for an application or subset of the URLs for the application.

Use operator conditions to enter URLs

You can enter the URLs by using operator conditions:

Tracking billable hits

comes with a ready-to-use event (Akamai content distribution network (CDN) Event). You can use this event to manually track billable hits that flow from the Akamai CDN to .

also provides a ready-to-use report for automatically tracking billable hits.

Enabling the Akamai Connector

If you use the Akamai connector, you must enable the application to receive data from it. If you fail to enable the application to receive Akamai data, the data collector does not process the CDN data from Akamai, which results in a drop in data for that application.

1. Log in to Experience Analytics.
2. Select Manage accounts for your Organization.
3. Select the Applications tab.
4. Select the application that is to receive data from Akamai.
5. Set Receive Akamai data to True.
6. Click Save.

Setting up applications for the Akamai service

For each application that receives data from Akamai, you must set the type of data that the application receives and enter the URLs for the applications that send data to Acoustic Experience Analytics (Tealeaf).

• You must know what type of data the application will receive, either Akamai, regular, or both.
• You must have a list of all of the URLs to map to the application.

You can enter the URLs by using operator conditions:

• is equal to
• is not equal to
• contains
• starts with

1. Log in to Acoustic Experience Analytics (Tealeaf).
2. Select Manage accounts for your Organization.
3. Select the Applications tab.
4. Select the application for which you are setting the type of data to receive and to which you are mapping URLs.
5. Select Map URL.
6. For the first URL that you are mapping to the application, select the condition and enter the URL.
7. Optional: For each additional URL that you are mapping to the application:
   1. Select Add another URL.
   2. Select the condition for the URL.
   3. Enter the URL.
8. Click Save.

Configuring Akamai data routing when a single domain is used by multiple applications

If your site employs a single domain across multiple applications, and you want Akamai to route data to multiple applications, you must set the TLAppKey appropriately.

Experience Analytics clients with the Akamai Data Connector can set the TLAppKey cookie as the 32-bit appkey of "Tealeaf® SaaS application" in their server's request/response. When configured this way, the Akamai connector honors that value and sends the data to the "Tealeaf SaaS application" using that appkey value.

Note: If the hit includes the TLAppKey cookie, use the applicationID from the cookie. Otherwise, use the Acoustic Experience Analytics (Tealeaf) UI configured appkeyID for the domain in the hit.