The Trailblazer Community in Slack is now in Open Beta—join and connect in real time. [Join us in Slack]
Developers can set up two ways for customers to send shopper profile attributes to Einstein: bulk upload and real-time activity tracking. You can use either method (or both) to send shopper profile data to Einstein.
When submitting data to Einstein, keep the following in mind:
Salesforce offers a secure bulk upload endpoint for customers to upload any historical shopper profile data they have collected.
The bulk upload option is intended for:
Uploading data in bulk can have a major impact on Einstein data. For this reason, we allow only authorized users to upload large quantities of data. In addition, each upload API call must pass a required authorization header (bearer) access token obtained from Account Manager.
Note: To reduce load on the Account Manager server, avoid generating any new tokens until the current token expires. Refer to the API Specification for more information on bulk upload API calls.
To prepare bulk upload data for Einstein consumption, make sure of the following:
login_id identification field, email_address identification field, or both.orange|yellow.To help generate relevant product recommendations for each shopper, the Profile Connector API needs either of these user identifiers for shopper identification in bulk upload.
| Field | Description |
|---|---|
| login_id | Shopper’s login ID. In some cases this is the same as the email_address value. |
| email_address | Shopper’s full email address. For example, shopper1@somewhere.com. |
Here is an example of shopper profile bulk upload TSV data with random column names:
| login_id | email_address | gender | colors | brand_list |
|---|---|---|---|---|
| shopper1 | shopper1@somewhere.com | male | orange|yellow | brandA|brandB |
| shopper2 | shopper2@somewhere.com | female | blue|black | brandD |
| shopper3 | shopper3@somewhere.com | female | red|black|violet | brandB|brandE |
When performing shopper profile bulk upload, keep the following endpoint limitations in mind:
After you prepare the shopper profile bulk data files, gzip each individual file and upload it to Einstein’s shopper profile bulk upload endpoint. For more information, refer to the Send bulk profile endpoint.
Use the activity updateProfile tracking endpoint to call and send real-time shopper profile data updates and preferences. Capturing information that a shopper provides in your storefront in real time enables recommendations to reflect these changes immediately.
The real-time activity tracking option is intended for:
To help generate relevant product recommendations for each shopper, the Profile Connector API provides two user identifiers for shopper identification in real-time tracking.
cookieId (required) - Unique identifier of an anonymous shopper. Typically, the cookieId is the value of a first-party cookie.
cqcid cookie value to match the automatic activity tracking on the traditional storefront. For more information, see Browser-Based Local Data Storage.visit_id value from the guest login response to match automatic activities. For more information, see the OCAPI Customer Document.userId (encouraged) - Unique identifier of a logged-in shopper. This parameter enables Einstein to link the same logged-in user across multiple devices.
cquid cookie value to match automatic activity tracking on the traditional storefront. For more information, see Browser-Based Local Data Storage.hashed_login value from the registered login response to match automatic activities. For more information, see the OCAPI Customer Document.To avoid potential malicious activity, user identifier parameters must be non-sequential. The parameters should not include sequences, patterns, IP addresses, email addresses, names, or anything linked to a specific person. All user identifier parameters must comply with General Data Protection Regulation (GDPR) through hashing or other methods.
Note