Disclaimer: This website requires Please enable JavaScript in your browser settings for the best experience.

The availability of features may depend on your plan type. Contact your Customer Success Manager if you have any questions.

Dev GuideAPI ReferenceUser Guide
Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideLegal TermsGitHubDev CommunityOptimizely AcademySubmit a ticketLog In
Dev Guide
Legal TermsGitHubDev CommunityOptimizely AcademySubmit a ticket

Akamai

Describes how to implement Optimizely Performance Edge with Akamai.

Suggest Edits

We recommend this approach to customers who use Akamai.

1. Add a <script> tag

Add the following script tag in the appropriate spot inside the <head> tag on your page.

📘

Note

Optimizely Performance Edge is only supported on pages served over HTTPS; it is not supported on pages that are served over insecure http://. If this is a problem for you, we want to hear about it! Contact Optimizely Support and let them know why you are interested in support for insecure HTTP.

The format of this snippet should be:

<script src="/optimizely-edge/<project_id>.js"></script>

To find <project_id>:

  1. Go to the Settings tab.
  2. Find the Project ID in the UI. You'll also need Account ID for the path rewriting configuration below.

2. Add a rule

In Akamai, create a new criteria that will apply the rule on paths that match your Performance Edge snippet. For example, /optimizely-edge/<project_id>.js. This is the same path you should have included in the snippet on your site.

3. Add two behaviors

Next, add two behaviors below:

  • Target the origin server
  • Modify outgoing request path behavior

Target the origin server

  1. Change the value of Origin Server Hostname field to optimizely-edge.com.
  2. Set the Forward Host Header value to Origin Hostname. This will modify the request going from the CDN to the browser.

Modify outgoing request path behavior

Replace part of the incoming path to ensure that the request from the snippet on your page is directed to its location in Optimizely.

Your configuration should match these specifications:

ActionRegular Expression Replacement
Find what^\/optimizely-edge\/<project_id>\.js
Replace with/edge-client/v1/<account_id>/<project_id>
OccurrencesAll
Keep the query parametersYes

This behavior looks for all requests whose paths start with /optimizely-edge/<project_id>.js and replaces that string with a new path: /edge-client/v1/<account_id>/<project_id>. In the screenshot below, this is configured for someone whose Account ID is 1234567 and Project ID is 0864213579.

TTL Setting Preservation

To ensure that Akamai respects the original TTL being set on your Optimizely project settings, you must create one additional behavior, for caching.

Configure your new caching behavior to match these options:

Caching optionHonor Origin Cache Control and Expires
Force Revalidation of Stale ObjectsAlways revalidate with origin
Default Max-age120 seconds
(This is the default on the Optimizely CDN.)
Honor PrivateNo
Honor Must-RevalidateNo

Add a downstream cacheability behavior to match this:

Caching OptionAllow Caching
Cache LifetimeFull edge TTL (max-age)
Send HeadersSend same headers as origin
Mark as PrivateOff

📘

Note about cookies

Customers who wish to filter the cookies that are shared with the Edge Decider for targeting purposes, may implement a whitelist approach by amending their CDN configuration to modify the outgoing "Cookie" request header sent to the optimizely-edge.com. If you implement a whitelist, make sure that the following cookies used by Optimizely are on that list:

  • optimizelyEndUserId
  • optimizelyRedirectData
  • optimizelyDomainTestCookie
  • optimizelyOptOut
  • Any other non-Optimizely cookie that you may need for experiment targeting

You can read more about the above cookies and their purpose here.

The end result:

4. Complete your setup

Save your new rule. You will now be able to leverage your HTTP/2 configuration to request Optimizely.

At the end of this process, your Akamai configuration options should look like this:

Verify your setup

To verify your setup and ensure that the correct data is received in the browser, start by checking that the Edge Decider returns a microsnippet to your browser.

  1. Load the webpage that has the <script> tag on it.
  2. In the JavaScript console, run optimizelyEdge.
  3. If optimizelyEdge returns defined, you've implemented Performance Edge successfully.

Congratulations! You're now ready to create an experiment.

Updated almost 2 years ago