Pull Experience Platform data back into Commerce

Sending your Commerce data to the Experience Platform using the Data Connection extension is one side of Commerce’s data sharing capabilities. The other side, which is an optional extension, is called Audience Activation. This extension allows you to build audiences in Real-Time CDP and deploy those audiences to your Commerce store to inform cart price rules, related product rules, and dynamic blocks.

At a high level, the flow of data from your Commerce store to the Experience Platform and back through the Audience Activation extension looks like the following:

Data Connection flow

After you set up the connection between Commerce to Experience Platform and Experience Platform to Commerce, the data continues to flow. You do not need to reconnect, unless required to do so by an upgrade.

Concepts

Sharing data between these two systems requires that you understand several concepts.

  • Data - The data that gets shared with the Experience Platform is data collected from browser events on your storefront, back office events on the server, and profile record data. Storefront events are captured from shoppers’ interactions on the site and include events such as addToCart, pageView, createAccount, editAccount, startCheckout, completeCheckout, signIn, signOut, and so on. See storefront events for the full list of storefront events. Server-side, or back office events, include order status information, such as orderPlaced, orderReturned, orderShipped, orderCancelled, and so on. See back office events for the full list of back office events. Profile record data contains information when a new profile is created, updated, or deleted. See profile record data to learn more.

  • Experience Platform and Edge Network - The data warehouse for most Adobe DX products. Data sent to the Experience Platform is propagated to Adobe DX products through the Experience Platform Edge Network. For example, you can launch Journey Optimizer, retrieve your specific Commerce event data from the edge, and build an abandoned cart email in Journey Optimizer. Journey Optimizer can then send that email if there are any abandoned carts in your Commerce store. Learn more about the Experience Platform and the Edge Network.

  • Schema - The schema describes the structure of the data that is being sent. Before Experience Platform can ingest your Commerce data, you must compose a schema to describe the data’s structure and provide constraints for the type of data that can be contained within each field. Schemas consist of a base class and zero or more schema field groups. The schema uses the XDM structure, which all Adobe DX products can read. The schema ensures that data sent to the Experience Platform is understood across all DX products. Learn more about schemas.

  • Dataset - A storage and management construct for a collection of data, typically a table that contains a schema (columns) and fields (rows). Datasets also contain metadata that describes various aspects of the data they store. All data that is successfully ingested into Adobe Experience Platform is contained within datasets. Learn more about datasets.

  • Datastream - 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. When you create this datastream, specify the XDM schema you created above. Learn more about datastreams.

Supported architecture

The Data Connection extension is available on the following architectures:

Prerequisites

To use the Data Connection extension, you must have the following:

  • Adobe Commerce 2.4.4 or newer
  • Adobe ID and Organization ID
  • Adobe Client Data Layer (ACDL), which is required to collect storefront event data
  • Entitlements to other Adobe DX products.

Onboarding steps

At a high level, enabling the Data Connection extension involves the following steps:

  1. Install the Data Connection extension.
  2. Sign in to your Adobe account and view to confirm your organization ID. The organization ID is the ID associated with your provisioned Experience Cloud company. This ID is a 24-character alphanumeric string, followed by (and must include) @AdobeOrg.
  3. Ensure you have permission for data collection in Experience Platform.
  4. Review the types of data you can collect and send.
  5. Create or update your time series event schema or profile record data schema with Commerce-specific field groups.
  6. Create a dataset based off the schema you created or updated. This dataset contains the Commerce data sent to the Experience Platform Edge.
  7. Create a datastream and select the XDM schema that contains the Commerce-specific field groups.
  8. Connect to Commerce Services.
  9. Connect to Adobe Experience Platform.

The remainder of this guide walks you through all of these steps in more detail so you can get to up to speed and begin using the power of Adobe DX products in your Commerce store.

NOTE
For mobile developers, learn how to integrate the Adobe Experience Platform Mobile SDK with Commerce.

HIPAA Readiness

The Data Connection extension allows you to share Commerce back office data with the Experience Platform and maintain HIPAA compliance. Learn more.

Audience

This guide is designed for the Adobe Commerce merchant who wants to enrich and personalize their Commerce store to enhance the shopping experience for their customers.

Support

If you need information or have questions that are not covered in this guide, use the following resources: