Adobe Analytics Ecommerce Events

This destination does not strictly adhere to the RudderStack Ecommerce Event Spec.

RudderStack broadly classifies ecommerce events (Merchandizing) as shown in the following sections:

Product Viewed

• Adobe Event Name: prodView
• RudderStack Events: Product Viewed, Product List Viewed
• Properties used:

Product Added

• Adobe Event Name: scAdd
• RudderStack Event: Product Added
• Properties used:

Product Removed

• Adobe Event Name: scRemove
• RudderStack Event: Product Removed
• Properties used:

Order Completed

• Adobe Event Name: purchase
• Rudder Events: Order Completed
• Properties used:

Cart Viewed

• Adobe Event Name: scView
• Rudder Events: Cart Viewed
• Properties used:

Checkout Started

• Adobe Event Name: scCheckout
• Rudder Events: Checkout Started
• Properties used:

Cart Opened

• Adobe Event Name: scOpen
• Rudder Events: Cart Opened
• Properties used:

Workflow for sending ecommerce events to Adobe Analytics

1. The channel, campaign, state, and zip window properties are updated.
2. RudderStack sets the timestamp according to the dashboard settings.
3. The currencyCode window property is set.
4. The Event string (if mapped on the dashboard) is set.
5. The Product string (if mapped on the dashboard) is set.
6. contextData, eVars, lists, hiers, and props are set.
7. linkTrackVars is set.
8. The mapped Adobe event is set.
9. Finally, tl() is called. The tl() method is a core component of Adobe Analytics. It takes all analytics variables defined in the page, compiles them into an image request, and sends that data to the Adobe data collection servers. It works similarly to the t() method, except this method does not increment page views.

The tl() method is useful for tracking links and other elements that would not otherwise be considered in a full page load.

Questions? Contact us by email or on Slack