Adobe Analytics cloud mode

RudderStack lets you send your event data to Adobe Analytics via cloud mode.

Find the open source transformer code for this destination in the GitHub repository.

Track

RudderStack categorizes the track events sent to Adobe into the following three types:

1. User tracking events
2. Ecommerce events
3. Heartbeat (video) events

A sample track call is as shown:

rudderanalytics.track("User clicked link", {
  category: "click",
  label: "URL click"
})

Note that:

• Before sending the user tracking and heartbeat track events, you must map them in the RudderStack dashboard.
• RudderStack sends the ecommerce events to Adobe if they conform to the following mapping:

Page

RudderStack sends a page view event to Adobe Analytics whenever you make a page call.

A sample page call is as shown:

// Passing page category, name and properties
rudderanalytics.page("category", "name", {
  path: "path",
  url: "url",
  title: "title",
  search: "search",
  referrer: "referrer",
})

If this call is made, the pageName of the window.s variable will be set as Viewed Page name. RudderStack also sends other information like referrer,url, etc.

For every page call, RudderStack sets the mappings done in the dashboard as contextual data, eVars, hiers, lists and props. It calls the t() method to compile all the set variables and sends them to Adobe Analytics.

Overriding Adobe parameters

When sending data to Adobe Analytics via cloud mode, RudderStack lets you override the values of certain Adobe parameters in the final XML payload by passing the following event properties:

{
  “evar1”: “value1”,
  “evar2”: “value2”,
}

{
  “hier1”: “oh1”,
  “hier2”: “oh2”,
}

{
  “list1”: “bike, fazer90”
}

{
  “property1”: “somevalue”
}

";product1;Games;event1=1"

Questions? Contact us by email or on Slack