ÃÛ¶¹ÊÓƵ Commerce Connection adobe-commerce
Overview overview
The ÃÛ¶¹ÊÓƵ Commerce destination connector lets you select one or more Real-Time CDP audiences to activate to your ÃÛ¶¹ÊÓƵ Commerce account to deliver a dynamic personalized experience for your shoppers. Within ÃÛ¶¹ÊÓƵ Commerce, you can then select those Real-Time CDP audiences to personalize unique offers in the cart such as ‘buy 2 get 1 free,’. You can also display hero banners and modify product pricing through promotional offers, all customized to ÃÛ¶¹ÊÓƵ Real-Time CDP audiences.
Prerequisites prerequisites
This connector is available in the destinations catalog for customers who have purchased Real-Time CDP Prime or Ultimate and ÃÛ¶¹ÊÓƵ Commerce.
To use this destination connection, make sure that you have access to:
- . With access to the developer console, you can view service account and credential information that is needed to complete the configuration of the extension in ÃÛ¶¹ÊÓƵ Commerce.
In Experience Platform, create the following:
- Schema. The schema you create represents the data you plan to ingest from ÃÛ¶¹ÊÓƵ Commerce. Learn more about how to create a schema that contains Commerce-specific field groups.
- Dataset. A dataset is a storage and management construct for a collection of data. You create this dataset from the schema that you created above.
- Datastream. ID that allows data to flow from ÃÛ¶¹ÊÓƵ Experience Platform to other ÃÛ¶¹ÊÓƵ DX products. This ID must be associated to a specific website within your specific ÃÛ¶¹ÊÓƵ Commerce instance. When you create this datastream, specify the XDM schema you created above.
After you complete the prerequisites, connect to the Commerce destination.
Connect to the destination connect
To connect to the ÃÛ¶¹ÊÓƵ Commerce destination:
- In the , go to Destinations > Catalog.
- Select Personalization.
- Select the ÃÛ¶¹ÊÓƵ Commerce destination to highlight it, then select Set up.
- Follow the steps described in the destination configuration tutorial.
Connection parameters parameters
While setting up this destination, you must provide the following information:
- Name: Fill in the preferred name for this destination.
- Description: Enter a description for your destination. For example, you can mention which campaign you are using this destination for. This field is optional.
- Integration alias: This value is sent to the Experience Platform Web SDK as a JSON object name.
- Datastream ID: This determines which Data Collection datastream contains the audiences that are included in the response to the page. The drop-down menu shows only datastreams that have the destination configuration enabled. See Configuring a datastream for more details.
Enable alerts enable-alerts
You can enable alerts to receive notifications on the status of the dataflow to your destination. Select an alert from the list to subscribe to receive notifications on the status of your dataflow. For more information on alerts, see the guide on subscribing to destinations alerts using the UI.
When you are finished providing details for your destination connection, select Next.
Activate audiences to the Commerce destination activate
Read Activate profiles and audiences to profile request destinations for instructions on activating audiences to the Commerce destination.
Next steps in ÃÛ¶¹ÊÓƵ Commerce
Now that you have configured the Commerce destination within Experience Platform, you need to install the Audience Activation extension in Commerce and configure the Commerce Admin to import the Real-Time CDP audiences you created. See the Commerce documentation to learn more.
Validate audience activation in Commerce exported-data
After you activate Real-Time CDP audiences to your ÃÛ¶¹ÊÓƵ Commerce account, you will see those audiences available when you go to the Admin sidebar, then go to Customers > Real-Time CDP Audience.
Data usage and governance data-usage-governance
All ÃÛ¶¹ÊÓƵ Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how ÃÛ¶¹ÊÓƵ Experience Platform enforces data governance, read the Data Governance overview.