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 behavioral data that you already have in Audience Manager to create new 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, you need to need to label the corresponding data source as such:
Go to Audience Data -> Data Sources.
Find the data source that contains your DPUUIDs, and click it.
In the ID Type drop-down menu, select Cross Device.
Make sure the option Cannot be tied to personally identifiable information is unchecked.
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.
Save the data source settings.
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.
Save the data source settings.
Watch the video below for a video tutorial of how to create a data source 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.
This step only applies to Scenario 2 described above. If your existing DPUUIDs are already hashed email addresses, skip to Step 3 - Create a Profile Merge Rule for Segmentation.
Let’s say you want to match your existing DPUUIDs to the hashed email addresses from the table below (right column), and store the hashed email addresses in the new data source that you created at Step 1 - Configure Data Source Settings.
DPUUID (CRM ID) | Email address | Hashed email address |
---|---|---|
68079982765673198504052656074456196039 | johndoe@example.com |
55e79200c1635b37ad31a378c39feb12f120f116625093a19bc32fff15041149 |
67412682083411995725538770443620307584 | janedoe@email.com |
16d72e3edbeb089b299e0d12fc09522fdc5ece2d11dcb1304ecdd6fab4f7193a |
89159024796760343733111707646026765593 | name@mydomain.com |
feec5debcea411f54462a345a0d90c9975415d2d4862745ff8af00c49b6b4ae6 |
You can link up to 10 hashed email addresses to a single DPUUID. To do this, separate the hashed email addresses with a <TAB>
, inside the synchronization file.
In our example, you would now have two data sources.
Data source ID | Data source contents |
---|---|
999999 | Existing DPUUIDs (CRM IDs) |
987654 | Hashed email addresses |
Your ID synchronization file would have the following contents:
68079982765673198504052656074456196039<TAB>55e79200c1635b37ad31a378c39feb12f120f116625093a19bc32fff15041149
67412682083411995725538770443620307584<TAB>16d72e3edbeb089b299e0d12fc09522fdc5ece2d11dcb1304ecdd6fab4f7193a
89159024796760343733111707646026765593<TAB>feec5debcea411f54462a345a0d90c9975415d2d4862745ff8af00c49b6b4ae6
The ID synchronization file must follow this naming structure:
c2c_id_<DPUUID_DATA_SOURCE_ID>_<HASHED_EMAIL_DATA_SOURCE_ID>_TIMESTAMP.sync
In the example above, the file name would look like this:
c2c_id_999999_987654_1560431657.sync
Once you’ve created your ID synchronization file, you need to upload it to an Amazon S3 bucket. To learn how to upload ID synchronization files, see Send Batch Data to Audience Manager.
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 audience 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.
A udience 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.