Connect Salesforce Commerce Cloud
Connect your Salesforce Commerce Cloud store so Tapper Vantage learns the value of each order and ties it to the ad click behind it.
Salesforce Commerce Cloud is the Salesforce product many online stores run on. Connecting it lets Tapper read your store's orders, so Vantage learns what each order was worth and which ad click it came from. To learn more about Vantage, see Tapper Vantage.
Tapper only reads. It asks for one permission, the orders read scope (sfcc.orders), and cannot change anything in your store.
This page is for Commerce Cloud, your online store. For Salesforce as your CRM, see Connect Salesforce Sales Cloud. For your customers and email, see Connect Salesforce Marketing Cloud Engagement.
Before you start
- In Commerce Cloud, you need an Account Manager administrator to create the API client, and access to Business Manager to look up your short code, organisation ID and site IDs.
- In Tapper, you need the Owner or Admin role, with two-step sign-in, to connect, test, change or disconnect Commerce Cloud.
- Your order confirmation page should send the order number to the Tapper purchase tag. That is how Tapper ties an order to the ad click behind it. See Install the conversion script.
Create an API client for Tapper
Do this in Account Manager.
Sign in to Account Manager as an administrator, open API Client and click Add API Client.
Give it a display name, for example Tapper, and enter a password twice. The password is the client secret you will enter in Tapper.
Add your organisation. Under Roles, add Salesforce Commerce API, and set its tenant filter to your tenant, for example abcd_prd.
Under Allowed Scopes, enter sfcc.orders and nothing else. Set Token Endpoint Auth Method to client_secret_basic.
Click Save, then copy the API client ID shown for the new client.
Find your store's details
In Business Manager, go to Administration > Site Development > Salesforce Commerce API Settings and copy the short code and the organisation ID. The organisation ID starts with f_ecom_ and ends with your tenant ID, for example f_ecom_abcd_prd. Then copy the ID of each store site you want Tapper to read.
Connect from Tapper
In Tapper, open Setup > Data sources in the sidebar. Commerce Cloud is in the Sales group. If your workspace has more than one protected entity, first pick the one your store belongs to in the switcher under the workspace name.
Click Connect Commerce Cloud and enter the API client ID, the API client secret, the tenant ID, the short code, the organisation ID and the site IDs. Separate several site IDs with commas, up to 20. Tapper stores the secret encrypted and never shows it again.
Click Test connection. Tapper signs in with your API client and reads one order from each site. Each site shows Passed, No orders yet or Failed, and a failed test says why in plain words, for example a wrong client ID or secret. You can run up to 30 tests an hour.
What Tapper reads
| Data | What |
|---|---|
| Orders | Order number, status, payment and shipping status, order dates, currency, order total, tax, shipping and the product total before tax. |
| Customer | Customer number, whether it was a guest order, and the email address. |
| Order lines | Item ID, product ID, quantity and price. |
The email is hashed the moment it arrives. The original address is never stored: not in our database, not in logs, not in our warehouse.
Tapper never reads the customer's name, billing or shipping address, phone number, order notes, payment details or your custom attributes.
Keeping it in sync
Tapper first reads your order history, then keeps up with new and changed orders, including cancellations. To change which sites Tapper reads, edit the site IDs on the Commerce Cloud tab and save.
Disconnecting
Click Disconnect on the Commerce Cloud tab. Tapper deletes the stored secret and stops reading. To end the access on Salesforce's side too, delete Tapper's API client in Account Manager.