Adobe Commerce & RTCDP

The Data Connection extension helps Adobe Commerce customers seamlessly integrate with Adobe Experience Platform to enrich the customer profile and personalize experiences in digital storefront and other channels.

Technical Capablities Enabled

• Storefront data (client side, such as add to cart, cart abandons, and so on) collected and sent into any Adobe Experience Cloud product.
• Back office order status to any Adobe Experience Cloud product
• Back office historical orders can be sent to Adobe Experience Platform
• Share and personalize RTCDP audiences to Adobe Commerce

Pre-requisites

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

• Adobe Commerce 2.4.4 or newer
• Adobe ID and Organization ID
• Adobe Experience Platform/RTCDP
• Adobe Client Data Layer (ACDL). The ACDL is required to collect storefront event data.

Onboarding steps

Data Collection from Adobe Commerce to Adobe Experience Platform

• Install the Data Connection extension.
• 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.
• Create or update your XDM schema with Commerce-specific field groups.
• Create a dataset based off the schema you created or updated. This dataset will contain the Commerce data you send.
• Create a datastream and select the XDM schema that contains the Commerce-specific field groups.
• Connect to Commerce Services.
• Connect to Adobe Experience Platform.

Connect to the Commerce Destination from Adobe Experience Platform for Audience Sharing

To connect to the Adobe Commerce destination:

• In the Adobe Experience Platform interface, go to Destinations > Catalog.
• Select Personalization.
• Select the Adobe Commerce destination to highlight it, then select Set up.
• Follow the steps described in the destination configuration tutorial.

Out-of-Box Data

• Storefront (Browser/App) Events
• Back office events
• Historical order data

For complete list of events supported, please refer to Commerce Events

Architecture

Related Implementation Guides