Connect Commerce data to Adobe Experience Platform

To connect your Adobe Commerce instance to the Adobe Experience Platform, you must provide an organization ID and a datastream ID.

Experience Platform connector configuration

General

  1. Sign in to your Adobe account in the Commerce Services Connector and select your organization ID.

  2. In the Admin, go to System > Services > Experience Platform Connector.

  3. In the Scope drop-down, set the context to Website.

  4. In the Organization ID field, you see the ID associated with your Adobe Experience Platform account, as configured in the Commerce Services Connector. The organization ID is global. Only one organization ID can be associated per Adobe Commerce instance.

  5. (Optional) If you already have an AEP Web SDK (alloy) deployed to your site, enable the checkbox and add the name of your AEP Web SDK. Otherwise, leave these fields blank and the Experience Platform connector deploys one for you.

    NOTE

    If you specify your own AEP Web SDK, the Experience Platform connector uses the datastream ID associated with that SDK and not the datastream ID specified on this page (if any).

Data collection

NOTE

For merchants already enrolled in our back office beta program, you will see a checkbox to enable back office events. If you would like to participate in the back office beta program, contact drios@adobe.com.

In the Data collection section, you specify what types of data to collect and send to the Experience Platform edge. By default, storefront events are automatically sent as long as the AEP Web SDK and Organization ID are valid. See the events topic to learn more about storefront and back office events.

Beta Experience Platform connector configuration

NOTE

All fields in the Data collection section apply to the Website scope or higher.

  1. Select Back office events if you want to send order status information, such as if an order was placed, cancelled, refunded, or shipped.

    NOTE

    By default, all back office data is sent to the Experience Platform edge. If a shopper chooses to opt out of data collection, you must explicitly set the shopper’s privacy preference in the Experience Platform. This is different from storefront events where the collector already handles consent based on shopper preferences. Learn more about setting a shopper’s privacy preference in the Experience Platform.

  2. (Skip this step if you are using your own AEP Web SDK.) Create a datastream in the Adobe Experience Platform or select an existing datastream you want to use for collection.

  3. (Skip this step if you are using your own AEP Web SDK.) In the Datastream ID field, paste the ID of that new or existing datastream.

Field descriptions

Field Description
Scope Specific website where you want the configuration settings to apply.
Organization ID (Global) ID that belongs to the organization that purchased the Adobe DX product. This ID links your Adobe Commerce instance to Adobe Experience Platform.
Is the AEP Web SDK already deployed to your site Select this checkbox if you have deployed your own AEP Web SDK to your site
AEP Web SDK Name (Global) If you already have an Experience Platform Web SDK deployed to your site, specify the name of that SDK in this field. This allows the Storefront Event Collector and Storefront Event SDK to use your Experience Platform Web SDK rather than the version deployed by the Experience Platform connector. If you do not have an Experience Platform Web SDK deployed to your site, leave this field blank and the Experience Platform connector deploys one for you.
Storefront events Is checked by default as long as the Organization ID and datastream ID are valid. Storefront events collect anonymized behavioral data from your shoppers as they browse your site.
Back Office events (Beta) If checked, event payload contains anonymized order status information, such as if an order was placed, cancelled, refunded, or shipped.
Datastream ID (Website) ID that allows data to flow from Adobe Experience Platform to other Adobe DX products. This ID must be associated to a specific website within your specific Adobe Commerce instance. If you specify your own Experience Platform Web SDK, do not specify a datastream ID in this field. The Experience Platform connector uses the datastream ID associated with that SDK and ignores any datastream ID specified in this field (if any).

With the Experience Platform connector extension installed, the link between Adobe Commerce and Adobe Experience Platform created, and the Datastream ID specified, Commerce data begins to flow to the Adobe Experience Platform edge and to other Adobe DX products.

NOTE

The amount of time it takes for data to flow from the edge to other Adobe DX products can vary.

Commerce data at the edge

When Commerce data is sent to the Adobe Experience Platform edge, you can build reports like the following:

Commerce Data in Adobe Experience Manager
Commerce Data in Adobe Experience Manager

On this page