AAM to Analytics Cookie Destination


Before you start:

Please be aware that this integration is not officially supported by Adobe Systems.  This solution is provided "as is".


  • Access to Adobe Audience Manager
  • Sufficient privileges to create destinations within the AAM User Interface


Setup Steps:

1. Set up the cookie destination in AAM:

The first step is to create a cookie destination in the AAM User Interface.  While the name and descriptive information can be determined by you, for this walkthrough we will set up the destination as follows:

Name: AAM to Analytics

Description: Sends Segment information to Analytics

Cookie Name: aam_aa

Data Format: Single Key

Key: aamaa

Note: Auto-fill Destination Mapping - When setting up the destination you have the option to enable the destination mapping auto fill.  If you wish to pass the AAM segment IDs to Analytics, check the Auto Fill box and specify the use of Segment IDs.  In order to more easily work with Adobe Analytics, you may consider creating unique segment classifications to use as the mapping value.


2. Modify the appMeasurement file:

There are two changes that need to be made to the appMeasurement (or DTM) code in order to utilize the AAM destination.  The first change is in the "doPlugins" function.

doPlugins section:

//Get AAM Segments

Plugins section:

  Gets the AAM segments out of a cookie. Requires replace (repl)
s.getAamSegments=new Function("a","b",""
+"var s=this;var c=s.c_r(a);if(c){c=s.repl(c,b+'=','');}ret"
+"urn c");

  Plugin Utility: Replace v1.0
s.repl=new Function("x","o","n",""
+"var i=x.indexOf(o),l=n.length;while(x&&i>=0){x=x.substring(0,i)+n+x."
+"substring(i+o.length);i=x.indexOf(o,i+l)}return x");

3. Setting up the Analytics List Var:

The final step is to enable list var 1 in the Analytics Admin console.  This should be configured to be pipe delimited.  You can also configure it to use "hit" expiration, since they should be set on every hit and pulling the IDs from the cookie.