Custom Data Onboarding
Implementation guide to send custom audiences
This guide walks you through the steps to securely upload your customer data to Experian for audience activation to supported destinations. It provides all the details needed to prepare and format your audience files.
Who to contact:
Contact |
When to reach out |
Experian Project Manager |
Primary contact for data onboarding set-up and questions |
Experian Account Executive/Relationship Manager |
Primary contact for Experian products and services |
General Onboarding Questions |
Your Data > Secure Transfer Service (STS) > Experian Activation
Acceptable file transfer methods:
Ask your Project Manager for the STS User Guide for step-by-step instructions.
You will create one file for each audience you want to onboard. The file and field requirements are outlined below. Several file types are accepted. Please follow these guidelines closely to avoid errors.
Audience files consist of a header row containing column names, followed by rows of data that identify the audience members. See Section 6 for the complete list of allowed column names and descriptions for each. Supported columns are:
To build an audience file,
Note: The Column reference section is a full reference for every possible column name. Only include columns that match the identifiers you have (e.g., name, email, IP). Don’t include unused columns. See File examples. |
Pipe (the “|” character) and comma (the “,” character) delimited files are accepted.
Example of a comma-delimited file:
| Type | Example |
| Header row of column names | prefix, fname, lname, email_1 |
| Data row | Mr, John, Smith, jsmith@example.com |
| Data row with some values missing | , , Doe, |
Note: None of the data values you provide should contain either of these delimiter characters (known as “embedded delimiters”). However, if a data value does include embedded delimiters, you must put double quotes (″) around that value or the data on that row will not be read correctly. |
The naming convention you use for your audience file will define how the audience is displayed within our system. Each file must include your company name and the audience name. Each file must include the company name as the prefix to ensure it lands in the properly location in our system. The underscore (_) should be used to separate the company name prefix and your audience name. The company name should also be included in the audience name & both can be separated with a space.
| Example | Description |
| 3PC_Joes Computers High LTV.psv | 3PC_–Prefix Joes Computers – Company Name High LTV – Audience Name |
| 3PC_ShoppersStore July Coupon Campaign.csv |
3PC_–Prefix ShoppersStore – Company Name July Coupon Campaign – Audience Name |
Keep file names under 100 characters. Only letters, numbers, and underscores after the company name prefix (_) are allowed.
Examples shown are in comma-delimited (.csv) format.
Let’s say your audience data contains only email addresses and for some people you have two emails. Your audience file would look like this:
email_1,email_2 |
john.smith@example.com, |
jane.doe@example.com,jdoe@example.com |
fname,lname,addr1,addr2,city,state,sha1_maid |
John,Smith,"123 Main Street, South",,Anytown,IL,4dfaa92388699ac6539885aef1719293879985bf |
ip_address,md5_ip_address |
127.0.0.1, |
,f528764d624db129b32c21fbca0cb8d6 |
2603:8001:f0:da0::, |
We ask that you create a test file once you have established your file transfer method and understand the file requirements. Once delivered to Experian, your PM will review the file, help you correct any errors, and provide approval to start sending real files for Onboarding.
Only include the columns for the identifiers you are submitting in the file. Your file cannot contain the same column name multiple times; they must be unique.
Column Name |
Max Length |
Description |
Example |
luid |
10 |
Living Unit ID-client specific
Clients that already have an Experian LUID can use as input For the consumer identifier.
Should be the only column included |
6975435801 |
prefix |
20 |
Prefix |
Mr, Mrs, Dr |
fname |
100 |
First Name |
John |
mname |
100 |
Middle Name |
Quincy |
lname |
100 |
Last Name |
Smith |
suffix |
20 |
Suffix |
Jr, Sr, II, III |
fullname |
300 |
Full Name |
Dr. John Q Smith III |
addr1 |
50 |
Address 1 |
123 Main Street |
addr2 |
50 |
Address 2 |
Apt 204 |
addr3 |
50 |
Address 3 |
|
city |
50 |
City |
Anytown |
state |
2 |
2-character state abbreviation |
IL |
zip |
10 |
ZIP Code |
60000, 60000 1234 , 60000-1234, 600001234 |
maid |
50 |
Mobile Ad Id, either IDFA or GAID |
38400000-8cf0-11bd-b23e-10b96e40000d |
md5_maid |
32 |
md5-hashed MAID |
5756ae9022b2ea1e47d84fead75220c8 |
sha1_maid |
40 |
sha1-hashed MAID |
4dfaa92388699ac6539885aef1719293879985bf |
sha256_maid |
64 |
sha256-hashed MAID |
d4181bb455a74b3bc8b37c75ac9b2c702eb6b9930bd040b861403b31ca85634d |
ip_address |
50 |
IPv4 or IPv6 |
127.0.0.1, 2603:8001:f0:da0:: |
md5_ip_address |
32 |
md5-hashed ip |
f528764d624db129b32c21fbca0cb8d6 |
sha1_ip_address |
40 |
sha1-hashed ip |
4b84b15bff6ee5796152495a230e45e3d7e947d9 |
sha256_ip_address |
64 |
sha256-hashed ip |
12ca17b49af2289436f303e0166030a21e525d266e209267433801a8fd4071a0 |
email_1 |
50 |
Email address 1 |
jsmith@example.com |
md5_email_1 |
32 |
md5 hash of email 1 |
765d64036cc8ec496f31dd0c242dbeca |
sha1_email_1 |
40 |
sha1 hash of email 1 |
5e62708376848a09125987b9c439c58cb3df74b6 |
sha256_email_1 |
64 |
sha256 hash of email 1 |
6e3913852f512d76acff15d1e402c7502a5bbe6101745a7120a2a4833ebd2350 |
email_2 |
50 |
Email address 2 |
jsmith@example.com |
md5_email_2 |
32 |
md5 hash of email 2 |
765d64036cc8ec496f31dd0c242dbeca |
sha1_email_2 |
40 |
sha1 hash of email 2 |
5e62708376848a09125987b9c439c58cb3df74b6 |
sha256_email_2 |
64 |
sha256 hash of email 2 |
6e3913852f512d76acff15d1e402c7502a5bbe6101745a7120a2a4833ebd2350 |
email_3 |
50 |
Email address 3 |
jsmith@example.com |
md5_email_3 |
32 |
md5 hash of email 3 |
765d64036cc8ec496f31dd0c242dbeca |
sha1_email_3 |
40 |
sha1 hash of email 3 |
5e62708376848a09125987b9c439c58cb3df74b6 |
sha256_email_3 |
64 |
sha256 hash of email 3 |
6e3913852f512d76acff15d1e402c7502a5bbe6101745a7120a2a4833ebd2350 |
email_4 |
50 |
Email address 4 |
jsmith@example.com |
md5_email_4 |
32 |
md5 hash of email 4 |
765d64036cc8ec496f31dd0c242dbeca |
sha1_email_4 |
40 |
sha1 hash of email 4 |
5e62708376848a09125987b9c439c58cb3df74b6 |
sha256_email_4 |
64 |
sha256 hash of email 4 |
6e3913852f512d76acff15d1e402c7502a5bbe6101745a7120a2a4833ebd2350 |
NPI |
10 |
National Provider Identifier
Can’t be included with LUID |
1598841058 No hyphens, periods, or letters. Numeric values can’t be too short or too long & must start with a 1 or 2 |
There are no special formatting rules for names and addresses, just
Email addresses must be in the standard format local-part@domain.
You may include up to four plain text emails and four hashed emails of each type in one row. Each email must appear in a separate column and correspond to the column keyword.
Mobile Ad IDs come in two popular forms, IDFA (typically used with Apple devices) and GAID or Google Ad ID (previously known as AAID).
Both IDs are 36 characters long and look like this:
38400000-8cf0-11bd-b23e-10b96e40000d
Before hashing a MAID, you must normalize it by trimming leading and trailing white space and by changing all characters to lowercase. See Hashing Data for more details.
IP addresses may be provided in IPv4 or IPv6 format.
Example: 2001:0db8:85a3:0000:0000:8a2e:0370:7334
Hashed IPv6 values
IPv6 values must be formatted prior to hashing.
Note: formatting is not necessary if you are not hashing the IPv6.
A hextet is a group of four characters in the address (“25fa”). An IPv6 address is a series of hextets separated by colons (:).
To format prior to hashing, follow these steps:
Example
Original value: 2603:0000:0000:0DA0:7cd1:6410:25fa:7bf8
Formatted value: 2603::da0::
| Step | Rule | Example |
| 1 | Remove spaces and make lowercase | 2603:0000:0000:0DA0:7cd1:6410:25fa:7bf8 2603:0000:0000:0da0:7cd1:6410:25fa:7bf8 |
| 2 | Remove the last four hextets | 2603:0000:0000:0da0:7cd1:6410:25fa:7bf8 2603:0000:0000:0da0 |
| 3 | Remove consecutive 0000s | 2603:0000:0000:0da0 2603::0da0 |
| 4 | Remove leading zeros from each hextet | 2603::0da0 2603::da0 |
| 5 | Append :: | 2603::da0:: |
Let’s say the last name for a consumer has a value of Smi,th, maybe because someone typed their name in wrong. In a comma-delimited file, this value must be enclosed in double quotes: "Smi,th" and it would look like this:
fname, lname, email_1
John,"Smi,th",jsmith@example.com
For email, MAID and IP hashing:
For example, “ JSmith@Example.com ” becomes “jsmith@example.com”
Do not include raw and hashed versions of the same value in a row.
Updating an audience means replacing the individuals that make up the audience while retaining the existing audience name.
You can refresh existing audiences by sending a new file with the same file name. This will fully replace the previously uploaded audience data.
Audiences expire 180 days after their creation, or after the last refresh, and will be deleted from the platform.
If you want to create your audience file using Excel, it’s easy to convert the Excel file to a comma-delimited file.
You can view your comma-delimited file by opening it with “TextEdit”.
A filled-out Deal Sheet should be sent to your PM when sending an audience file. If you need a copy, please reach out to your PM.
If the audience is being delivered to multiple destinations, destination information can be captured in one Deal Sheet.