Skip to main content

​
Overview

Resonate is an audience intelligence platform that helps brands activate first-party data for targeting and match enrichment. With the Resonate destination, you can sync customer data from your data warehouse to Resonate via SFTP, enabling audience matching and activation.

​
Supported syncing

  • All: Sends all records in your model every time the sync runs.
  • Insert: Sends only new records added since the last sync.
For more information about sync modes, refer to the sync modes docs.

​
Connect to Resonate

Go to the Destinations overview page and click the Add destination button. Select Resonate and click Continue. You will need the following credentials from Resonate:
  • Username: Your Resonate SFTP username.
  • Private Key: The SSH private key for SFTP authentication. Provide the full private key including the header and footer.
  • Private Key Passphrase (optional): The passphrase for your private key, if applicable.
Resonate uses SSH key-based authentication. Contact your Resonate account representative to obtain your SFTP credentials and private key.
Hightouch connects to Resonate’s SFTP server at sftp.resonate.com on port 22. Files are automatically placed in the data-append/inbound/ directory.

​
Sync configuration

Once you’ve set up your Resonate destination and have a model to pull data from, you can set up your sync configuration. Go to the Syncs overview page and click the Add sync button. Select the relevant model and the Resonate destination.

​
Field mapping

Map columns from your model to Resonate’s required fields. Customer ID is required for every sync. You must also include at least one identifier group:
HEM and HEM Type must be mapped together — you cannot map one without the other. Similarly, if you map any postal address field, all required address fields (Address Line 1, City, State, Zip Code) must be mapped.
Hightouch automatically hashes email values in the HEM field using MD5 (preferred), SHA-1, or SHA-256. You do not need to pre-hash emails before syncing.

​
Data quality options

Remove Duplicates: When enabled, duplicate rows based on Customer ID are automatically removed before writing to the file. Skip Invalid Rows: When enabled, rows missing required identifiers (Customer ID + at least one identifier group) are skipped rather than causing sync errors.

​
File format

Resonate requires CSV files. Hightouch automatically handles file naming and placement:
  • Directory: data-append/inbound/
  • File naming: {ModelName}_{SegmentName}_{YYYYMMDD}_{syncRunId}.csv

​
Tips and troubleshooting

To see the exact API requests and responses from each sync run, use the live debugger. To get notified by Slack, PagerDuty, SMS, or email when a sync fails, set up sync alerts. If you run into an issue this page doesn’t cover, .

​
Match rate

Resonate targets a 60–80% match rate. To maximize match rates:
  • Include complete postal address (Address Line 1, City, State, Zip Code) when available — this is Resonate’s strongest identifier.
  • Ensure email addresses are lowercase and trimmed before syncing. Hightouch handles hashing automatically.
  • Remove inactive, duplicate, and low-quality records from your model before syncing.
  • Suppress international records, business addresses, and P.O. boxes.

​
Data requirements

Resonate enforces the following data quality requirements:
  • Emails must be lowercase with no leading or trailing spaces (Hightouch hashes them automatically).
  • Records missing consent should be excluded from your model.
  • International records, business addresses, and P.O. boxes should be suppressed.
Last modified on March 30, 2026