Offline Identity Append

Offline Identity Append can resolve more offline data points to your customer profiles. In doing so, it will help you better resolve data, increase offline reach, and more accurately measure and attribute consumers’ actions.

You need to send us any combination of the following data points to successfully achieve the above use cases:

• Name and postal address 

                   - Note: This is not as common a use-case. Although, you can send us customer name and postal address to receive telephones appended to your customer data. 

• Name and zip code 
• Name and zip code (with radius) 

                   - Note: Radius can be a parameter selected during setup, where the same radius value is used for all records. Alternatively, radius can be a field on the client input file and the radius value can be different for each record. The radius field is only required on the client input file if the values are different for each record.   

• Name and/or Email (raw or hashed)

                   - Note: Name not required but will improve the level of data accuracy. 

• Name and/or Telephone

                   - Note: Name not required but will improve the level of data accuracy. 

Then, Offline Identity Append resolves these data points and appends the below offline data points, based on your data selection:

• Telephone (landline and in the clear, “raw”) 
• Name (first, middle, last, and prefix)
• Postal address (postal, state, zip code, etc.) 

This document will take you through details on how to send and receive data to receive the Offline Identity Append product. 

• Standard data input file details
• Standard data input for resolution
• PII
• MAID
• HEM
• IP

• Main project point of contact: Experian Project Manager (PM). They will be your main point of contact from the start of your engagement with Experian to the end, helping you understand what data to send, how to send it, and where to send it to among other items.  
• Interest in other Experian products or services: Please contact your Experian Account Executive or Relationship Manager. Often, our clients license Enrichment with Offline Identity Append, accessing Experian’s Marketing Attributes for their first-party data along with the additional offline identity data points they receive from Offline Identity Append.

• When the contract for Offline Identity Append is signed, an Experian Project Manager (PM) will introduce themselves and be your main point of contact during the project.
• Select the data points you would like to send to Experian: Name and postal address, Name and zip code, Name and zip code (with radius), Email (raw or hashed), and/or Telephone
• Select your delivery location and work with Experian to enable transfers.
• Format your data input file based on the guidelines in this article below.
• 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.

• 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

• Experian will perform Offline Identity Append as detailed in the contract, which will include address standardization on PII to ensure the highest match level is reached.
• Your PM will provide initial match results for the Offline Identity Append product so that you can review and provide approval before moving forward.
• Experian will format the output data file(s) based on the guidelines in this article below.
• Experian will transfer the data output file to the delivery location.

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

***Larger quantities require additional design discussions.  

***Snowflake shares and API (transaction and micro-batch) require additional design discussions.

These are the standard delivery locations that we support for you to send Experian data inputs for Offline Identity Append.

• Client API endpoint
• Experian Secure Transport (aka Client SFTP, STS)
• AWS S3
• Google Cloud Platform (GCP)*
• Snowflake*

*Disclaimer: Data ingestion from and delivery of the Offline Identity Append output to Snowflake and Google Cloud have an extended set up time of 3-4 weeks. If the data is needed sooner, we can ingest the input data or deliver the first output via one of the other delivery locations, like SFTP or S3.

These are the standard delivery cadences that we support for you to send Experian data inputs for Offline Identity Append.

• One-time
• Monthly 
• Quarterly
• Annually
• On-demand

Quickly jump to a section using these links:

• Standard data inputs for resolution
• HEM

You can send us a data file containing any of the following data points for your first-party data:

• Name and postal address
• Name and zip code
• Name and zip code (with radius)
• Name and/or Email (raw or hashed)
• Name and/or Telephone

These IDs can be sent separately or in combination.  

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.

We can accept HEMs from you to perform this service. Experian accepts:

• SHA1 HEM
• SHA256 HEM
• MD5 HEM

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

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.

Sample data input file with HEMs

• Standard data outputs
• Offline Identity Append output file

We can return any of the following data points appended to your first-party data:

• Name (first, middle, last, and prefix)
• Postal address (postal, state, zip code, etc.)
• Telephone (landline and in the clear, “raw”)

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

Delivery standards

Sample data output file