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 build audience segments from offline-only customer data, and send them to People-Based Destinations.
The first step creating audience segments in this scenario is to bring your offline customer data into Audience Manager.
Before continuing, make sure that the customer activity that you are about to onboard is already defined in Audience Manager with corresponding onboarded traits.
Regardless of whether your existing Audience Manager customer IDs (DPUUIDs) are hashed emails or not, you must perform the trait onboarding against the data source that contains your DPUUIDs.
You want to qualify the customer IDs from the table below for the corresponding onboarded trait IDs. Let’s consider that your DPUUIDs are stored in a data source with the ID 999999, and your Audience Manager data source ID is 123.
|Customer ID (DPUUID)||Onboarded Trait ID|
|89159024796760343733111707646026765593||11223, 93342, 27341|
To qualify the customer IDs in the example above for the corresponding onboarded traits, you must upload an inbound data file with the following contents:
68079982765673198504052656074456196039<TAB>d_sid=12345,d_sid=23456 67412682083411995725538770443620307584<TAB>d_sid=45678 89159024796760343733111707646026765593<TAB>d_sid=11223,d_sid=93342,d_sid=27341
The file name would look like this:
See Amazon S3 Name and File Size Requirements for Inbound Data Files for detailed information on the file name structure.
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:
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.
This step only applies to Scenario 2 described above. If your existing DPUUIDs are already hashed email addresses, skip to Step 4 - Create a Profile Merge Rule for Segmentation.
Let’s say you want to match your existing DPUUIDs from the example at Step 1 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 2 - Configure Data Source Settings.
As a reminder, you would now have two data sources:
|Data source ID||Data source contents|
|999999||Existing DPUUIDs (CRM IDs)|
|987654||Hashed email addresses|
|DPUUIDs (CRM IDs)||Email address||Hashed email address|
In our example, 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:
In the example above, the file name would look like this:
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.
To create new segments from offline-only data, use the Segment Builder and make sure you use the new profile merge rule that you created in the previous step when creating the segment.
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.