You are here:
Cookie and Identity SDK Differences
The Marketing Cloud Personalization and Salesforce Personalization SDK differ in what identity cookies they use and how cookie security is configured. Anonymous ID management configuration is identical for both SDKs.
SDK Identity Cookies
The Marketing Cloud Personalization SDK uses
various identity cookies, whereas the Salesforce Personalization uses only
_sfic_* identity cookies. When configuring the Data 360 sitemap, make
sure to update any cookie management logic referencing _evga_* or
_evgn_*
cookies.
Example: Marketing Cloud Personalization Web SDK Cookies_sfid_xxxx // Primary identity cookie (SalesforceInteractions module)
_evga_xxxx // MCIS visitor cookie (account/dataset specific)
_evgn_xxxx // MCIS secondary cookieExample: Data 360 Web SDK Cookie_sfid_xxxx // Single, unified identity cookieSDK Cookie Security Settings
This table describes how cookie security settings differ between the two SDKs.
| Marketing Cloud Personalization Web SDK | Data 360 Web SDK |
|---|---|
Sets _sfid_* with nosameSiteattribute, and
sets secure: true only when explicitly configured. |
Sets _sfid_* with secure: true and
sameSite: "strict" by default. Both settings are
configurable. |
Anonymous ID Management
Both the Marketing Cloud Personalization and Data 360 Web SDKs use the same configuration for getting and setting anonymous identification.
// Get anonymous ID
const anonId = SalesforceInteractions.getAnonymousId();// Set anonymous ID
SalesforceInteractions.setAnonymousId('custom-id');