Please adhere to our file formatting guidelines when sending Append data to Resonate to ensure efficient processing and highest possible match rates for your files.
How can you send us data?
Resonate accepts data through multiple secure channels. Choose the method that works best for your organization:
• Box
• AWS
• SFTP
• Snowflake Direct Share
Best practices for optimal match rates
Reference file format example
Please reference this file format example, which lays out the columns and formatting requirements for each column with examples. Adhering to this format ensures your file aligns to Resonate’s ingestion standards and avoids processing delays.
Run the hashing script
Resonate developed a hashing script that standardizes email formatting prior to hashing:
• Converts all emails to lowercase
• Removes leading and trailing spaces
• Ensures clean, hash-ready input
Review email hashing and data cleanliness
To maximize match after running the hashing script, review your file to verify:
• All emails are lowercase
• No leading and trailing spaces
After hashing, ensure hashes are valid alphanumeric outputs:
Hash Type | Length | Example |
MD5 (preferred) | 32 characters | ec55d3e698d289f2afd663725127 |
SHA-1 | 40 characters |
A94A8FE5CCB19BA61C4C0873D391E987982FBBD3
|
SHA-256 | 64 characters | 051f26bd6cde782239bf52e56854d3feeca75ae5a84508d1ff9a1868ba167ee5 |
It’s also best to review your file for general data cleanliness:
- Remove any duplicate, inactive, or low-quality records
- Suppress any rows missing critical IDs (e.g. customer ID + HEM, HEMType or MAID, or ZIP11/Address)
- Remove any rows containing missing key fields or lacking consent (e.g. improperly hashed emails, incomplete addresses)
- Suppress any international records and business addresses and P.O. boxes
See “Best Practices for Data Preparation” for detailed advice on data cleanliness.
Required Identifiers for Matching
Resonate uses a waterfall matching method, starting with the most precise identifier and cascading to others when necessary. This strategy enables us to deliver the highest match possible, even when some IDs are unavailable.
You must include Customer ID and at least one of the following identifiers:
ID type | Required fields | Notes: |
HEM + Customer ID |
HEM HEM Type |
Both columns required |
MAID + Customer ID | MAID | Single field |
Postal Address + Customer ID |
Address Line 1 Address Line 2 City State Zip Code (five digit) |
All fields required; incomplete addresses cannot be used |
ZIP + Customer ID | Zip11 | ZIP11 preferred. ZIP5+4 or other formats smaller than ZIP11 will not be accepted. |
IP Address + Customer ID | IP address | Supports IPv4 format |
Please note: For 60-80% match rate targets, a complete postal address is strongly recommended.
Match rate scenarios
Use this guide to anticipate your match rate based on the type and completeness of your data.
Objective | What to provide: |
For the best match rate with precise predictions on most records | Provide both:
|
For best match rate with predictions on relevant HEM in household | Provide one or the other:
|
For precise predictions only (40-60% match rate for HEMs) | Provide one or the other:
|
Save your file with the correct naming convention
To help us efficiently process your file, please use the following file naming format and file type:
- Files should be in a .csv format
- Files should named with this structure: <Clientname>_<Segment>_<yyyymmdd>
• Example: Clientname_ResonateAppend_20250201.csv
Need help?
If you’re unsure how to format your file or have any questions, contact your Customer Success Manager or email ResonateSupport@resonate.com for guidance prior to submitting. We’re happy to help ensure your data drives the best possible outcome.
Comments
0 comments
Article is closed for comments.