RudderStack supports sending event data to Adobe Analytics via the following connection modes:

Connection ModeWebMobileServer
Device ModeSupportedSupported-
Cloud ModeSupportedSupportedSupported
In the web device mode integration, that is, using JavaScript SDK as a source, the Adobe Analytics native SDK is loaded from https://cdn.rudderlabs.com domain. Based on your website's content security policy, you might need to allowlist this domain to load the Adobe Analytics SDK successfully.

Once you've confirmed that the source platform supports sending data to Adobe Analytics, follow these steps:

  • Choose a source for which you would like to add Adobe Analytics as a destination.
  • From the list of destinations, select Adobe Analytics. Assign a name to the destination and click on Next.
  • Enter the relevant Connection Settings by referring to the following section.

Connection Settings

This section lists all the relevant connection settings to successfully set up Adobe Analytics as a destination in RudderStack.

adobe 1 adobe 2
  • Tracking Server URL: The trackingServer variable determines the location an image request is sent. For example, jimsbrims.sc.omtrdc.net.
Do not include the hypertext transfer protocol, for example, http:// in the tracking server URL.
If this variable is defined incorrectly, your implementation may experience data loss.
For more information on this setting, refer to the Adobe Analytics documentation.
  • Tracking Server Secure URL: The trackingServerSecure variable determines the location an image request is sent over HTTPS. If this variable is not defined correctly, your implementation can experience data loss.

For more information on this setting, refer to the Adobe Analytics documentation.

  • Report Suite ID(s): The Report Suite ID can be found in your Adobe Analytics Settings page. Multiple IDs can be separated by commas. For example: ab.cd,ef.gh,ij.kl.
  • Check for Heartbeat calls to be made over HTTPS: If this setting is enabled and the Heartbeat Tracking Server URL is present, the SSL value will be set to true so that the calls go over HTTPs.
  • Heartbeat Tracking Server URL: If assigned, this will be used as tracking server URL instead of the URL assigned in the Tracking Server URL field. RudderStack will set all heartbeat configurations if this URL is present.

For more information on this setting, refer to the Adobe Analytics documentation.

Identity Resolution

image  110 adobe 3
  • Marketing Cloud Organization ID: If you want to use visitorAPI.js, enter this field. For example: 99887766ABC@AdobeOrg.
  • Drop Visitor ID: If enabled, RudderStack does not assign the userId to visitorID.

For more information on this setting, refer to the Adobe Analytics documentation.

Timestamps

  • Timestamp Option: Adobe Analytics has Report Suites that accepts timestamped, non-timestamped or hybrid data. Note that window.s.timestamp will be affected. Also depending on this value, visitorID will be set if the drop visitor id is off.
  • If the timestamp option is disabled, thenvisitorID will be set.
  • If timestamp option is set to hybrid and the Prefer Visitor ID setting is on, then visitorID will be set.
  • For all other cases, RudderStack does not set avisitorID.
Also note the following regarding timestamps:
  • If the timestamp option is enabled, then timestamp will be set.
  • If the timestamp option is hybrid and Prefer Visitor ID is off, then timestamp will be set.
  • Send Both Timestamp and VisitorID for Timestamp Optional Reporting Suites: This setting lets you choose whether to send both the timestamp and the visitor ID when sending server-side events, in case you are using the Timestamps Optional Reporting Suite.

Enabling this setting might lead the data to be out of order. Hence, it is not recommended by Adobe. In order to make it work, you need to enable the Optional Timestamp setting in Reporting Suites.

  • No Fallbacks for Visitor ID: Enabling this setting removes the fallbacks. However, it is applicable only for the server-side events when the Drop Visitor ID setting is disabled and marketingCloudId is sent in the Adobe Analytics integration object. The priority order of setting the Adobe Analytics visitor ID is the destination-specific setting for visitorId, followed by userId, then anonymousId.

  • Prefer Visitor ID: Adobe does not allow sending both visitorID and timestamp. Hence, this option is used when the timestamp option is set as hybrid. Also, note that if this option is enabled, visitorID will be set. If disabled, the timestamp value will be set.

For more information on this setting, refer to the Adobe Analytics documentation.
  • Enable pageName for Track Events: When enabled, RudderStack only tracks events by sending a pageName.

Mappings

image  111 mapping adobe
  • Map Rudder Events to Adobe Custom Events: This setting allows you to add one or multiple custom Adobe events separated by comma.
  • Map Rudder Context data to Adobe Context Data: Context data variables allow you to you define custom variables on each page that the processing rules apply and can read. Instead of explicitly assigning values to the analytics variables, you can send your data in via these context data variables. The processing rules take the values from the context data variables and pass them into the respective analytics variables.

This setting allows you to map the key present under the context/properties of the RudderStack message to the property name you want to send to the Adobe context data. An example is as shown below:

"context": {
"contextProperties": {
"prop1": "val1",
"prop2": "val2"
}
}

If you want to set prop1 to Adobe's context data property1, then map with contextProperties.prop1 --> property1.

If you want to send top level properties anonymousId, messageId, event then simply enter the key.

For more information on this setting, refer to the Adobe Analytics documentation.

  • Add Prefix for Context Data: If you would like to prefix your RudderStack properties before sending them as contextData, you can enter a prefix here which will be automatically appended.
  • Map Rudder Properties to Adobe eVars: eVars are custom variables that you can use as per your requirement. Each eVar is a string containing custom values specific to your organization, with a maximum length of 255 bytes. Note that values longer than 255 bytes are automatically truncated when sent to Adobe.

This setting lets you map any RudderStack property with the eVar you want.

Only enter the index number of the eVar you want to set.
For more information on this setting, refer to the Adobe Analytics documentation.
image  108
  • Map Rudder Properties to Adobe Hierarchy properties: Hierarchy variables are the custom variables that allow you to see a site’s structure. By default, Adobe supports up to 5 hierarchy variables in your implementation.

This setting lets you map any RudderStack property with the hierarchy variable you want.

Only enter the index number of the hierarchy variable that you want to set.
For more information on this setting, refer to the Adobe Analytics documentation.
  • Map Rudder Properties to Adobe list properties: List variables are custom variables that you can use as per your requirement. They work similarly to eVars, except they can contain multiple values. Also, list variables do not have a character limit.

This setting lets you map any RudderStack property with the list you want.

Enter only the index number of the list you want to set to. The list properties should be an array/string separated by commas. Otherwise, they will be dropped.

For more information, refer to the Adobe Analytics documentation.

  • Map Rudder Property with Delimiters for list properties: The list variables need to be sent as a string. So if there is a list of properties, it needs to be delimited. RudderStack lets you set any of the delimiters from , ; / : |.
image  109
  • Map Rudder Properties to Adobe Custom properties: Props are custom variables that you can use as per your requirement. This setting lets you map any RudderStack property with the prop you want to set it to.
Enter only the index number of the prop you want to set. For more information, refer to the Adobe Analytics documentation.
  • Map Rudder Property with Delimiters for Adobe Custom properties: The property variables need to be sent as a string. So if there is a list of properties, it needs to be delimited. RudderStack lets you set any of the delimiters from , ; / : |.

Merchandise Event Level Settings

  • Map Rudder Events to Adobe Merchandise events: This setting lets you map the RudderStack event with the currency/purchase type of the Adobe event. For example: event5.
  • Increment or Currency Properties to add to merchandise events at event level: The RudderStack property that has a currency/counter value should be added here. This will then be used to create the event string like purchase,event5=19.9. RudderStack automatically sets the currencyCode value. (The default value is USD).
For more information, refer to the Adobe Analytics documentation.

Merchandise Product Level Settings

image  107
  • Map Rudder Events to Adobe Merchandise events: This setting lets you map a RudderStack event with a currency/purchase type of an Adobe event.
  • Properties to add to merchandise events at product level: With this setting, the RudderStack property that has a currency/counter value should be added. This will be used to create a product string like [category][item][quantity][total][incrementor][merchString].
image  105
  • Map Rudder Properties to eVars at product level: Lets you map the RudderStack properties you want to set to eVars.
Set only the index. The eVars will be appended with | and sent along with the product string.

For more information, refer to the Adobe Analytics documentation.

  • Product Identifier: Adobe Analytics accepts only a single product identifier. This setting lets you choose from a SKU/ID/Name of the product.

Contact us

For more information on the topics covered on this page, email us or start a conversation in our Slack community.

On this page