Adobe Commerce on Cloud infrastructure

  1. Enable the ENABLE_EVENTING global variable in .magento.env.yaml. Learn more.

        stage:
            global:
                ENABLE_EVENTING: true
    
  2. Commit and push updated files to the Cloud environment. When deployment is finished, enable sending events with the following command:

        bin/magento config:set adobe_io_events/eventing/enabled 1
    

Adobe Commerce on-premises installation

Execute the following commands in order to enable code generation and Adobe Commerce Events:

   bin/magento events:generate:module
   bin/magento module:enable Magento_AdobeCommerceEvents
   bin/magento setup:upgrade
   bin/magento setup:di:compile
   bin/magento config:set adobe_io_events/eventing/enabled 1

Confirm you enabled profile data to be captured and sent to Experience Platform

In the Commerce Admin, make sure that the following fields are set:

  • In System > Services > Data Connection, verify that the Back office events and Customer profiles checkboxes are enabled.
  • Ensure that the Profile Dataset ID field is correct and is a different dataset than what you are currently using for behavioral and back-office event data.

Check if events are routing to staging or production

  1. Run the following command to show the current Adobe Developer environment:

    Copy code
    bin/magento config:show
    adobe_io_events/integration/adobe_io_environment
    
  2. If the environment is set to Stage, change it to Production with the following command:

    Copy code
    bin/magento config:set adobe_io_events/integration/adobe_io_environment
    production
    

Query Event Data SaaS table

Connect and execute the following SQL query to verify customer profile records appear in the
event_data_saas table and that there are no errors:

Copy code
select * from event_data_saas;

Handle event publishing errors

  1. If you encounter the following error, ensure that the sandbox and production SaaS connector keys are correct:

    Copy code
    2024-06-07 14:37:57 | 2024-06-07 14:38:03 | 1 | 0 | Event publishing
    failed: Error code: 403; reason: Forbidden { "error": { "code":
    "Forbidden", "message": "Client ID is invalid", "details": {
    "error_code": "403003" } } }
    
  2. Go to the Commerce Services Connector page in the Admin and ensure that the sandbox/production keys specified are correctly configured. Also, confirm that the Commerce account sandbox/production settings match those shown in the Commerce Services Connector. Learn more.

Check if the Service ID is in the allowlist and confirm with Adobe Commerce support

  1. Verify that the Commerce Services Connector serviceId appears in allowlist in Adobe Commerce.
  2. Contact Adobe Commerce support to confirm the allowlist status.
Previous pageLive Search facets are not alphabetically sorted
Next pagePWA Studio: browser cannot resolve the .local.pwadev site

Commerce


Connect with Experience League at Summit!

Get front-row access to top sessions, hands-on activities, and networking—wherever you are!

Learn more