Introduction

Experian Enrichment allows you, as our client, to enrich your first-party data with demographic and behavioral data attributes from Experian Marketing Data.  Experian Enrichment allows you to get more value from your first-party data by gaining context around each of your consumers, subscribers or prospects. With the additional demographic and behavioral data insights, you can build smarter segmentation and more robust audience insights. 

This article will take you through details on how to send and receive data for enriching your first-party data sets with Experian Enrichment. 

Quickly jump to a section using these links:

Experian points of contact

Main project point of contact: Experian Project Manager (PM). They will be your main point of contact during Experian Enrichment, they will help facilitate the data transfers and answer any questions you have regarding data append processing.

Interest in other Experian products or services: Experian Account Executive or Relationship Manager. Please work with your sales team for data append contracting or if you are interested in using more Experian products or services.

Experian Enrichment process

  1. When the contract for Enrichment is signed, an Experian Project Manager (PM) will introduce themselves and be your main point of contact during the project.
  2. Select your delivery location and work with Experian to enable transfers.
  3. Format your data input file based on the guidelines in this article below.
  4. Name the data file using this structure:
  • Ideal file name structure: Client name_Unique identifier_Date file was added to delivery location
  • Sample file name: PetesStores_123456_11.7.23 
  • Note: Unique identifier could be the project name, internal project number, or any other identifier used to describe the input data. Outside of client name, unique identifier, and date that the file was added to delivery location, you can add any additional naming conventions as needed to the file name.
  1. Transfer the data input file to the delivery location and email your assigned PM with the below information
  • For the email subject line, include your business name and the project name
  • In the body of the email, include the data input file name and quantity of records in the file
  • If using Experian Secure Transport, attach the ST file transfer email notification that you received to this email as well
  1. Experian will perform enrichment as detailed in the contract.
  2. If enrichment match rates fall outside our expected thresholds, your PM will provide initial match results for your review before moving forward.
  3. Experian will format the output data file(s) based on the guidelines in this article below, returning Client Unique Sequence Number followed by the new Experian data attributes (what we enriched your file with). 
  4. Experian will transfer the data output file to the delivery location.
  5. Experian will send a notify email to the client which includes the data output file name, file layout, enrichment match rate reports, and the Experian Marketing Data data dictionary.

Standard delivery locations & cadence

Standard delivery locations that we support for you to send and receive Experian data inputs and outputs:

  • Experian Secure Transport (aka Client SFTP, STS)  
  • Amazon (AWS) S3  
  • Google Cloud Platform (GCP)   

Standard delivery cadences that we support for you to send Experian data inputs for resolution:

  • One-time
  • Monthly 
  • Quarterly
  • Annually

Data inputs

Experian supports receiving the offline and digital identifiers listed below from your first-party data set to be enriched with Experian data attributes. These IDs can be sent separately or in combination.  
 
Quickly jump to an ID section using these links:
 

Standard data input file details

  •  U.S. records only  
  •  Record count < 300MM 
  •  Delimiter = Pipe (|)  

PII *Preferred data input*

We can accept the following PII from you to enable enrichment:

  • Postal address
  • Name
  • Email in the raw
  • Phone number in the raw

Delivery standards

The customer record ID is a required field and then you would send accompanying PII fields that have been determined previously. Data fields should be formatted based on standards below.

Field name Field description Field formatting
Unique_seq Customer record ID *Required field* A sequence number unique to each record on the file used for post-collaboration matchback.  Client Account Number could be utilized if unique across the file.  
prefix  Name Prefix
 1 to 15 characters (truncates after 15) such as “Ms.”
fname First Name  1 to 20 characters (truncates after 20)   
mname  Middle Name  1 to 20 characters (truncates after 20)  
lname  Last Name  Address Standardization allows up to 30 characters   
suffix   Name Suffix  1 to 15 characters (truncates after 15) such as “Jr”   
fullname  Full Name  1 to 40 characters (truncates after 40)   
addr1  Address Line 1   1 - 30 (truncates after 30) Address 
addr2  
 Address Line 2 
 1 - 30 (truncates after 30) Address
addr3  Address Line 3    1 - 30 (truncates after 30) 
city    City   1 to 40 characters (truncates after 40)  
state  State  2 alphabetic characters for most services  
zip   ZIP Code  4 or 5 numbers (if 4 numbers, then assume a leading zero)   
email   Email in the raw  50 with '@' and '.' within string  
phone  Phone number in the raw 10 numbers  

Sample data input file with PII

Unique_seq
 fname 
 lname
 addr1 
 city
 state 
 zip
 email 
 phone
00458480 Mike Evans 123 Main Chicago IL 60193 mike@att.net 8476531234 
00371889 Bob  Hoff 377 Eagle Ave  Denver CO  80026 bob@gmail.com  3031235687
03a5978  Hank  Orr 789 Main St Costa Mesa CA 92614 hank@aol.coc 7149893388 

MAID

We can accept MAIDs from you to enable enrichment in these forms:

  • Raw MAID
  • SHA1 MAID
  • SHA256 MAID
  • MD5 MAID
  • Across apple or Android (Google) 

Delivery standards

The customer record ID is a required field and then you would send accompanying fields that have been determined previously. Data fields should be formatted based on standards below.

Field name  Field description   Field formatting  
Unique_seq  Customer record ID *Required field* A sequence number unique to each record on the file used for post-collaboration matchback.  Client Account Number could be utilized if unique across the file.  
maid  MAID Raw MAID (36 bytes)  
md5_maid  md5 MAID  This is the MAID hashed using md5  
sha1_maid  sha1 MAID This is the MAID hashed using sha1  
sha256_maid sha256 MAID This is the MAID hashed using sha256  

Sample data input file with MAIDs

Unique_seq
 maid 
00458480 67dfdbe7-acdb-4177-b885-3f49f6782eb4      
00371889 7452903A-E184-4846-A378-69E15ACBD11D      
03a5978 8200A84D-EF54-4DF5-9A48-3A937C02E71F     

HEM

We can accept HEMs from you to enable enrichment in these forms:

  • SHA1 HEM 

  • SHA256 HEM

  • MD5 HEM 

Note: If you are looking to send email in the raw, that is considered PII.

Delivery standards

The customer record ID is a required field and then you would send accompanying fields that have been determined previously. Data fields should be formatted based on standards below.

Field name  Field description   Field formatting  
Unique_seq  

Customer record ID 

*Required field*

 A sequence number unique to each record on the file used for post-collaboration matchback.  Client Account Number could be utilized if unique across the file.  
md5email md5 Email Address    This is the email address hashed using md5 lower case and trimmed prior to hash  
sha1email  sha256 Email Address This is the email address hashed using sha1 lower case and trimmed prior to hash   
sha256email sha256 Email Address    This is the email address hashed using sha256 lower case and trimmed prior to hash  

Sample data input file with HEMs

Unique_seq
 sha1email
00458480 71581ddec6248362dc418157c1773c967c7bfb7f
00371889 9736c9f074c812b4fad888453d782506f22aa5a8
03a5978 92c3575f4be087b8872c0d84360754f2751179c3

Hashed phone number

The customer record ID is a required field and then you would send accompanying fields that have been determined previously. Data fields should be formatted based on standards below.

  • SHA1 phone 

  • SHA256 phone

  • MD5 phone 

Note: If you are looking to send phone number in the raw, that is considered PII.

Delivery standards

The customer record ID is a required field and then you would send accompanying fields that have been determined previously. Data fields should be formatted based on standards below.

Field name 
 Field description   
 Field formatting  
Unique_seq   

Customer record ID 

*Required field* 

 A sequence number unique to each record on the file used for post-collaboration matchback.  Client Account Number could be utilized if unique across the file. 
md5phone    md5 Phone Number     
 This is the phone number hashed using md5   
sha1phone  
 sha1 Phone Number    This is the phone number hashed using sha1  
sha256phone   sha256 Phone Number   This is the phone number hashed using sha256   

Sample data input file with hashed phone number

Unique_seq
 sha1PhoneNumber 
00458480
 82581fdec6348372dc428157d1723c957c7cfb7f 
00371889 5736c3f064c872b4cad889453e782536f22ba5a8 
03a5978 32b3545f2aa083b8842c0b84460764f2751179c3 

IP

We can accept IPs from you to enable enrichment in these forms:

  • Raw IPV4 

  • Raw IPV6

  • SHA1 IP 

  • SHA256 IP

  • MD5 IP 

Delivery standards

The customer record ID is a required field and then you would send accompanying fields that have been determined previously. Data fields should be formatted based on standards below.

Field name 
 Field description   
 Field formatting  
Unique_seq   

Customer record ID

*Required field* 

 A sequence number unique to each record on the file used for post-collaboration matchback.  Client Account Number could be utilized if unique across the file. 
ip_address  
 IP Address 
 Raw IPv4 or IPv6  
sha1_ip  
 sha1 IP   
 This is the IP hashed using sha1  
sha256_ip   
 sha256 IP  
 This is the IP hashed using sha256   
md5_ip  
 md5 IP   
 This is the IP hashed using md5  
ip_start_date 
 IP Address Start Date  

Client defined first seen activity date for   

IP. format: YYYY-MM-DD or YYYY-MM-DD %  
ip_end_date   
 IP Address End Date  
 Client defined last seen activity date for IP. format: YYYY-MM-DD or YYYY-MM-DD %   
ip_state_code
 IP Address State Code   
 Two byte state abbreviation  

Sample data input file with IPs

Unique_seq
 ip_address 
00458480
 216.59.183.63 
00371889 24.11.50.221   
03a5978 24.18.184.226 

Data Outputs

Quickly jump to section using these links:

Enrichment output file

Experian will deliver the Enrichment output file to the client in the delivery location previously determined in a pipe delimited file format.

Delivery standards

Field name Field description Field formatting
Unique_seq   Customer record ID A sequence number unique to each record on the file used for post-collaboration matchback.  Client Account Number could be utilized if unique across the file.