This article contains product documentation meant to guide you through the setup and usage of this feature. Nothing contained herein is legal advice. Please consult your own legal counsel for legal guidance.
This page includes step-by-step guidance on how to combine offline CRM data with real-time behavioral data for authenticated users to create audience segments, then send these audience segments to People-Based Destinations.
Depending on whether your DPUUIDs are lowercase, hashed email addresses, you might need to configure the data source that will store the hashed email addresses.
Scenario 1: your DPUUIDs are already lowercase, hashed email addresses.
In this case, skip to Step 5 - Configure People-Based Platform Authentication.
Scenario 2: your DPUUIDs are not lowercase, hashed email addresses.
In this case, you need to create a new cross-device data source that will store your hashed email addresses. Here’s how to do this:
Log in to your Audience Manager account and go to Audience Data -> Data Sources, and click Add New.
Enter a Name and Description for your new data source.
In the ID Type drop-down menu, select Cross Device.
In the Data Source Settings section, select both the Inbound and Outbound options, and enable the Share associated cross-device IDs in people-based destinations option.
Use the drop-down menu to select the Emails(SHA256, lowercased) label for this data source.
This option only labels the data source as containing data hashed with that specific algorithm. Audience Manager does not hash the data at this step. Make sure the email addresses that you plan on storing in this data source are already hashed with the SHA256 algorithm. Otherwise, you won’t be able to use it for People-Based Destinations.
See Data Onboarding for frequently asked questions about how you should bring your offline data into Audience Manager for People-Based Destinations.
Watch the video below for a video tutorial of how to create a data source for People-Based Destinations.
To qualify authenticated users for rule-based traits, you need to send the trait qualification through declared IDs.
Let’s say you have created the following two data sources.
|Data source ID||Data source contents|
|999999||Existing DPUUIDs (CRM IDs)|
|987654||Hashed email addresses|
Then, you want to qualify the CRM IDs below for the trait in the table.
|DPUUID (CRM ID)||Email address||Hashed email address||Trait|
||55e79200c1635b37ad31a378c39feb12f120f116625093a19bc32fff15041149||location = US|
Your declared ID should follow this syntax:
In the example above, the declared ID call should look like this:
The next step is creating a new merge rule that will help you create the audience segments to send to your People-Based Destinations.
If you already have a rule defined with the Current Authenticated Profiles or Last Authenticated Profiles options, you can skip to Step 4 - Create Audience Segments.
To create new segments, use the Segment Builder. If you have existing audience segments that you want to send to People-Based Destinations, skip to Step 5 - Configure People-Based Platform Authentication.
Audience Manager handles the integration with social platforms through authentication tokens that expire after a certain amount of time. See Authentication Token Renewal for details on how to renew the expired tokens.