Can Safari users be targeted natively – on desktop or mobile?
No – by default, Safari blocks 3rd-party cookies, such as Salesforce DMP.
Can you build segments from Safari users?
Yes for analysis.
What Solutions does the Salesforce DMP support in order to target users on Safari browsers?
The Salesforce DMP offers two options to target users on Safari browsers:
1. Hashed Device Management
2. 1st-party cookie
What are the different Safari solutions available in Salesforce DMP?
How time-consuming is it to enable the two solutions?
The work to enable Hashed Device Identification is entirely on Salesforce's side and should be relatively quick to enable for a client. First-party cookies require development work on the client’s end, and thus, timing will be dependent on their deliverables. Once the client has set up the first party ID, enabling it on Salesforce's side is reasonably quick as well.
What’s the difference in how the KUID is created in the two approaches?First-party kuid generates the KUID in the browser. Fingerprinting generates a fingerprint and then gets an id for that fingerprint from the user data service.
Can you use Google PPID as a first-party ID for Safari?
Yes, but the client must first work with Google to enable PPID for their Google account. The client will then need to provide Salesforce with the google cloud storage location for which we should upload the user lists.
Additional information is available on Google’s support pages
Can you generate Hashed Device IDs on pages that do not carry a Salesforce DMP ControlTag?
No. The ControlTag is essential for Hashing.
Is there any difference in the how 1st-party cookies and Hashed Device IDs treat opt-outs?
Yes, if the client is utilizing a first-party cookie and has multiple domains, a dedicated opt-out will need to be configured and maintained for each site. Alternatively, if hashed device management is employed a single opt-out link will be applicable for a given client.
Can users opt-out of Hashed ID tracking?
Absolutely – unlike other providers of so-called Fingerprinting techniques, the Salesforce DMP actually can manage fingerprinting users through an opt-out.
Does Fingerprinting adhere to PII rules?
Yes, our hashed device management solution is fully compliant with PII protocols.
Do both approaches lose uses when they clear their cookies?
No, first-party cookies can be cleared, while the hashed ID will persist even if cookies are emptied.
What makes Salesforce's Hashed ID different from competitive offerings?
There are a few vendors outside of Salesforce who provide Hashed Device IDs, however, they do not couple it with a CDIM solution. This enables Salesforce to associate Safari activity within a larger, holistic set of that individual’s data and utilize Safari activity within a larger conversion path.
How can you tell if other providers offering Hashed Device Management solutions are accurate or employing CDIM?
If or when you hear really high numbers of unique users (UUs) reported against Safari, it often means that they are not resolving the browser down to a single user; each page view counts as a UU in Safari if you don't have a CDIM solution.
Does Salesforce use Canvas Fingerprinting to generate Hashed Device IDs?
No, Salesforce utilizes a proprietary approach to hashed device management and does not leverage canvas fingerprinting.
Can you user-match with 3rd-party data providers when utilizing a first-party cookie?
Clients will issue a 1st-party cookie to the Salesforce DMP, which we then take as our ID. Since it's not a 3rd party cookie – even though we are acting as an agent of our clients – it means that we are unable to sync those users with a 3rd party data provider unless the 3rd party fires a match pixel.
Where can I see the IDs once they’ve been enabled?
You can view the hashed device ID in the pixel.gif call from beacon.krxd.net under kfuid, which serves as the user’s KUID on Safari. The kxfp value is also a corresponding hashed ID that comes from the user data service.
Are Hashed IDs written to LocalStorage?
Yes, you can view your browser’s ID, as noted above, in localStorage corresponding to “kxfp_id” and “kxfp”