Some Adobe Commerce and Magento Open Source features are powered by Commerce Services and deployed as SaaS (software as a service). To use these services, you must connect your Commerce instance using production and sandbox API keys, and specify the data space in the configuration. You only need to set this up once.
The following lists the Commerce features you can access through the Commerce Services Connector:
|Product Recommendations powered by Adobe Sensei||Adobe Commerce|
|Live Search powered by Adobe Sensei||Adobe Commerce|
|Payment Services||Adobe Commerce and Magento Open Source|
|Channel Manager||Adobe Commerce and Magento Open Source|
|Site-Wide Analysis Tool||Adobe Commerce|
At a high level, the Commerce Services Connector is made up of the following core elements:
The following sections discuss each of these elements in more detail.
The production and sandbox API keys are generated from the Commerce account of the license holder, which is identified by a unique Commerce ID (MageID). To pass entitlement validation for services such as Product Recommendations or Live Search, the license holder of the merchant’s organization can generate the set of API keys as long as the account is in good standing. The keys can be shared on a “need to know” basis with the systems integrator or development team that manages projects and environments on behalf of the license holder. Additionally, solution integrators are also entitled to use Commerce Services. If you are a solution integrator, the signer of the Commerce partner contract should generate the API keys.
Log in to your Commerce account at https://account.magento.com.
Under the Magento tab, select API Portal on the sidebar.
From the Environment menu, select Production or Sandbox.
Enter a name in the API Keys section and click Add New.
This opens a dialog for downloading the new key.
This is the only opportunity that you have to copy or download your keys.
Click Download then click Cancel.
Repeat the above steps for each environment (production and sandbox).
The API Keys section now displays your API keys. You need both the production and sandbox keys when you select or create a SaaS project.
Commerce instances must be configured with a SaaS Project and a SaaS Data Space so that Commerce Services can send data to the right location. A SaaS Project groups all SaaS Data Spaces. The SaaS Data Spaces are used to collect and store data that enables Commerce Services to work. Some of this data may be exported from the Commerce instance and some may be collected from shopper behavior on the storefront. That data is then persisted to secure cloud storage.
For Product Recommendations, the SaaS data space contains catalog and behavioral data. You can point a Commerce instance to a SaaS data space by selecting it in the Commerce configuration.
Use your production SaaS data space only on your production Commerce installation to avoid data collisions. Otherwise, you risk polluting your production site data with testing data, which causes deployment delays. For example, your production product data could be mistakenly overwritten from staging data, such as staging URLs.
If you do not see the Commerce Services Connector section in the Commerce configuration, you must install the Commerce modules for your desired Commerce service.
To select or create a SaaS project, request the Commerce API key from the Commerce license holder for your store.
On the Admin sidebar, go to System > Services > Commerce Services Connector.
In the Sandbox API Keys and Production API Keys sections, paste your key values.
Private keys must include
----BEGIN PRIVATE KEY--- at the beginning of the key and
----END PRIVATE KEY---- at the end of the private key.
Any SaaS projects that are associated with your keys appear in the Project field in the SaaS Identifier section.
If no SaaS projects exist, click Create Project. Then in the Project field, enter a name for your SaaS project.
When you create a SaaS project, Commerce generates one or more SaaS data spaces depending on your Commerce license:
Select the Data Space to use for the current configuration of your Commerce store.
If you generate new keys in the API Portal section of My Account, immediately update the API keys in the Admin configuration. If you generate new keys and do not update them in the Admin, your SaaS extensions no longer work and you lose valuable data.
To change the SaaS project or data space names, click Rename.
(This feature is for future integration with the Adobe Experience Platform). To connect your Adobe Commerce instance to the Adobe Experience Platform, sign in to your Adobe account using your Adobe ID. After you sign in, the IMS organization associated with your Adobe account is displayed in this section.
When your Commerce instance successfully connects to Commerce Services, the catalog sync process exports product data from your Commerce server to Commerce Services. Learn more about the catalog sync process.