Connect Commerce data to Adobe Experience Platform

When you install the Experience Platform connector, two new configuration pages appear in the System menu under Services in the Commerce Admin.

• Commerce Services Connector
• Experience Platform Connector

To connect your Adobe Commerce instance to the Adobe Experience Platform, you must configure both connectors, starting with the Commerce Services connector then finishing with the Experience Platform connector.

Update the Commerce Services connector

If you have previously installed an Adobe Commerce service, you probably have already configured the Commerce Services connector. If not, then you must complete the following tasks on the Commerce Services connector page:

1. Log in to your Commerce account to retrieve your production and sandbox API keys.
2. Select a SaaS data space.
3. Log in to your Adobe account to retrieve your Organization ID.

After you configure the Commerce Services connector, you then configure the Experience Platform connector.

Update the Experience Platform connector

In this section, you connect your Adobe Commerce instance to the Adobe Experience Platform using your organization ID. You can then specify the type of data - storefront or back office - to send to the Experience Platform edge.

General

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

   NOTE

   If you previously configured the Commerce Services connector, you can skip this step as your organization ID has already been selected.

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, verify 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

In this section, you specify the type of data you want to send to the Experience Platform edge. There are two types of data: client-side and server-side.

Client-side data is data captured on the storefront. This includes shopper interactions, such as View Page, View Product, Add to Cart, and requisition list information (for B2B merchants). Server-side data, or back office data, is data captured in the Commerce servers. This includes information about the status of an order, such as if an order was placed, canceled, refunded, shipped, or completed.

In the Data collection section, select the type of data you want to send to the Experience Platform edge. To ensure that your Adobe Commerce instance can begin data collection, review the prerequisites.

See the events topic to learn more about storefront and back office events.

1. Select Storefront events if you want to send storefront behavioral data.

   NOTE

   The Storefront events checkbox is automatically enabled if the AEP Web SDK and Organization ID are valid.

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

   NOTE

   If you select Back office events, 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.

3. To ensure back office event data updates based on a schedule according to a cron job, you must change the Sales Orders Feed index to Update by Schedule.

   1. On the Admin sidebar, go to System > Tools > Index Management.

   2. Select the checkbox for the Sales Orders Feed indexer.

   3. Set Actions to Update by Schedule.

   4. If you are enabling back office data for the first time, run the following commands to reindex and trigger a resync. Subsequent resyncs occur automatically as long as the cron job is set up correctly.

      bin/magento index:reindex sales_order_data_exporter_v2
      

      bin/magento saas:resync --feed orders
      

4. (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.

5. (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

Confirm that event data is collected

To confirm that data is being collected from your Commerce store, use the Adobe Experience Platform debugger to examine your Commerce site. After you confirm that data is being collected, you can verify that your storefront and back office event data appears at the edge by running a query that returns data from the dataset you created.

1. Select Queries in the left navigation of Experience Platform and click Create Query.

   

2. When the Query Editor opens, enter a query that selects data from the dataset.

   

   For example, your query might look like the following:

   SELECT * from `your_dataset_name` ORDER by TIMESTAMP DESC
   

3. After the query runs, the results are displayed in the Results tab, next to the Console tab. This view shows the tabular output of your query.

   

In this example, you see event data from the commerce.productListAdds, commerce.productViews, web.webpagedetails.pageViews, and so on. This view allows you to verify that your Commerce data arrived at the edge.

If the results are not what you expect, open your dataset and look for any failed batches imports. Learn more about troubleshooting batch imports.

Business.Adobe.com resources