# E-commerce Events

RudderStack broadly classifies the E-commerce events (Merchandizing) as shown in the following sections:

## Product Viewed

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

| RudderStack property | Adobe Property | Default Value |
| -------------------- | -------------- | ------------- |
| currency             | currencyCode   | "USD"         |

## Product Added

* Adobe Event Name: `scAdd`
* RudderStack Event: `Product Added`
* Properties used:

| RudderStack property | Adobe Property | Default Value |
| -------------------- | -------------- | ------------- |
| currency             | currencyCode   | "USD"         |

## Product Removed

* Adobe Event Name: `scRemove`
* RudderStack Event: `Product Removed`
* Properties used:

| RudderStack property | Adobe Property | Default Value |
| -------------------- | -------------- | ------------- |
| currency             | currencyCode   | "USD"         |

## Order Completed

* Adobe Event Name: `purchase`
* Rudder Events: `Order Completed`
* Properties used:

| RudderStack property | Adobe Property                                                           |
| -------------------- | ------------------------------------------------------------------------ |
| currency             | currencyCode. Default "USD"                                              |
| purchaseId           | purchaseID                                                               |
| transactionId        | transactionID                                                            |
| order\_id            | purchaseID/transactionID (if purchaseId or transactionId is not present) |

## Cart Viewed

* Adobe Event Name: `scView`
* Rudder Events: `Cart Viewed`
* Properties used:

| RudderStack property | Adobe Property | Default Value |
| -------------------- | -------------- | ------------- |
| currency             | currencyCode   | "USD"         |

## Checkout Started

* Adobe Event Name: `scCheckout`
* Rudder Events: `Checkout Started`
* Properties used:

| RudderStack property | Adobe Property                                                           |
| -------------------- | ------------------------------------------------------------------------ |
| currency             | currencyCode. Default "USD"                                              |
| purchaseId           | purchaseID                                                               |
| transactionId        | transactionID                                                            |
| order\_id            | purchaseID/transactionID (If purchaseId or transactionId is not present) |

## Cart Opened

* Adobe Event Name: `scOpen`
* Rudder Events: `Cart Opened`
* Properties used:

| RudderStack property | Adobe Property | Default Value |
| -------------------- | -------------- | ------------- |
| currency             | currencyCode   | "USD"         |

## Workflow for Sending E-commerce 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**](https://rudderstack.com/docs/destinations/analytics/adobe-analytics/setting-up-adobe-analytics-in-rudderstack/).
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 the 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.

## Contact Us

For more information on any of the sections covered in this guide, you can [**contact us**](mailto:%20docs@rudderstack.com) or start a conversation in our [**Slack**](https://rudderstack.com/join-rudderstack-slack-community) community.
