Resonate

Sync first-party audience data to Resonate for consumer intelligence enrichment and targeted advertising activation. Zeotap delivers audience files via SFTP to Resonate’s identity matching platform, where records are enriched with over 15,000 predictive consumer attributes spanning demographics, psychographics, media preferences, and purchase intent.

Prerequisites

A Resonate account with SFTP access enabled
SSH credentials (username and private key) provided by your Resonate account team
The SFTP hostname and upload directory path from Resonate

Authentication

Resonate uses SSH Key authentication for secure SFTP file delivery.

Contact your Resonate account representative to request SFTP access credentials
You will receive a username and an SSH private key (PEM format)
In Zeotap, navigate to Destinations and click Add Destination
Select Resonate from the destination list
Enter your Username and paste the Private Key in the authentication section
If your private key is encrypted, enter the Passphrase in the optional field

Configuration

Field	Type	Required	Description
SFTP Host	Text	Yes	Resonate SFTP server hostname. Defaults to `sftp.resonate.com`.
Port	Number	No	SFTP server port. Defaults to `22`.

Target Settings

Field	Type	Required	Description
Upload Directory	Text	Yes	The directory on the Resonate SFTP server to deliver files to. Defaults to `data-append/inbound`.
Remove Duplicates	Toggle	No	Eliminate rows with duplicate Customer IDs before uploading. Enabled by default.
Enable Gzip Compression	Toggle	No	Compress files with gzip before uploading. Recommended for large audience files. Enabled by default.

Supported Operations

Sync Modes

Mode	Supported
Insert	Yes
Upsert	—
Update	—
Mirror	—

Audience Sync Modes

Mode	Supported
Add	Yes
Remove	—
Mirror	Yes
Upsert	—

Features

Field Mapping: No
Schema Introspection: No

Default Destination Fields

Field	Type	Description
`customer_id`	String	Internal customer identifier. Used as the primary key for deduplication.
`email`	String	Email address for identity matching. Automatically hashed by Resonate.
`hashed_email`	String	Pre-hashed email address (SHA-256 lowercase).
`maid`	String	Mobile advertising identifier (IDFA or GAID).
`first_name`	String	User first name for address-based matching.
`last_name`	String	User last name for address-based matching.
`street_address`	String	Street address for identity matching.
`city`	String	City name.
`state`	String	State or region code.
`zip_code`	String	5-digit or ZIP+4 postal code. ZIP+4 improves match rates.
`ip_address`	String	IP address for identity matching.
`segment_name`	String	Audience segment name or identifier.

How It Works

Zeotap serializes your audience data as a CSV file with the mapped fields
If Remove Duplicates is enabled, rows with duplicate Customer IDs are eliminated (the last occurrence is kept)
If Gzip Compression is enabled, the CSV file is compressed before upload
The file is uploaded to the configured directory on Resonate’s SFTP server
Resonate processes the file and matches records against their identity graph using the provided identifiers (email, address, MAID, IP)
Matched records are enriched with Resonate’s predictive consumer attributes and made available for audience targeting

File Naming

Files are named using the pattern batch_{timestamp}_{YYYYMMDD}.csv (or .csv.gz if compression is enabled). Each sync run produces a new file in the upload directory.

Identity Matching

Resonate supports multiple identifier types for matching. Including more identifiers increases match rates:

Email — Automatically hashed for privacy. Use lowercase, trimmed values for best results.
Complete postal address (street, city, state, ZIP) — Most effective when ZIP+4 is available.
Mobile Ad ID (MAID) — IDFA or GAID device identifiers.
IP address — Used as a supplementary matching signal.

Resonate typically achieves a 60-80% match rate when high-quality identifiers are provided.

Best Practices

Include multiple identifiers — Providing email, address, and MAID together significantly improves match rates
Use lowercase trimmed emails — Ensures consistent hashing and higher match rates
Include ZIP+4 codes — Extends match precision beyond standard 5-digit ZIP codes
Enable compression — Reduces upload time for large audience files
Enable deduplication — Prevents duplicate processing costs from repeated Customer IDs
Suppress international records — Resonate’s identity graph primarily covers U.S. consumers
Suppress business addresses — Consumer-focused matching works best with residential data

Troubleshooting

SSH connection failed

Verify your SFTP hostname and port. Ensure your SSH private key matches the public key registered with Resonate. Check that outbound SSH traffic on port 22 is not blocked by your network firewall.

Private key parse error

Ensure the private key is in PEM format (starts with -----BEGIN OPENSSH PRIVATE KEY----- or -----BEGIN RSA PRIVATE KEY-----). If the key is encrypted, provide the passphrase in the configuration.

Permission denied on upload directory

Confirm the upload directory path with your Resonate account team. The default path is data-append/inbound. Your SFTP user may only have write access to specific directories.

File upload succeeds but no matches appear

Check that your records include valid identifiers (email, postal address, MAID, or IP). Verify that email addresses are lowercase and trimmed. International or business records may not match against Resonate’s U.S. consumer identity graph.

Low match rates

Improve match rates by including more identifier types per record. Use complete postal addresses with ZIP+4 codes. Ensure email addresses are well-formatted and not disposable or temporary domains.

Duplicate records in output

Enable the Remove Duplicates toggle in target settings. This deduplicates by Customer ID before uploading, which prevents redundant processing and reduces file sizes.