This article covers what you submit, how to submit it, and what happens through delivery. Standard timeline is within two weeks of receipt and validation of your file.
Scoping
Before you submit your file, your Resonate contact will scope the engagement with you:
Use case — how you intend to apply the segments shapes how they are described at delivery
Industry context — informs the archetype labels
Input type — first-party file (standard) or a specific decile band from a prior Resonate Predictive Modeling output
Delivery destination — Box, SFTP, Snowflake, or Amazon S3
What you submit
Supported input types:
First-party file containing hashed emails (HEMs), mobile ad IDs (MAIDs), or IP addresses
A specific decile band from a prior Resonate Predictive Modeling output
Supported ID types:
| ID Type | Format |
|---|---|
| HEM (Hashed Email) | Lowercase hex hash — SHA256 (64 chars, default), SHA1 (40 chars), or MD5 (32 chars) |
| MAID (Mobile Ad ID) | Standard UUID, lowercase, hyphenated. 36 characters. IDFA (iOS) and AAID (Android) both supported |
| IP Address (IPv4) | Dotted-decimal IPv4. US residential only |
If your file contains unhashed emails, contact your Customer Success Manager for Resonate's hashing script and instructions.
File format:
CSV with header row, or Snowflake table for Snowflake delivery
Column 1: ID Type (
HEMMD5,HEMSHA1,HEMSHA2,MAID, orIP). Column 2: the ID.One row per record, no duplicates
No null values in the ID Type or ID columns
File name:
<client name>_<use case>_<yyyymmdd>.csv
Minimum size: 20,000 matched records. Match rates run 40–60% on HEM-only files and 60–80% on multi-ID files, so plan raw submissions accordingly.
How to submit your file
Signature Segmentation supports four delivery destinations, selected at engagement initiation.
Box. Your Resonate contact provisions a designated Box folder. You'll receive an email invitation; accept it, then upload your file to the Input folder within your engagement folder. Notify Resonate once uploaded. Outputs are placed in the Output folder within the same engagement folder.
SFTP. Uses a Resonate-hosted SFTP endpoint. Provide your SSH public key (RSA 4096) to your Resonate contact. You'll receive back the hostname, username, and folder path. Upload to the inbound folder; retrieve outputs from the outbound folder.
Snowflake. Uses Snowflake data sharing. Load your file into a Snowflake table in your account. Create a Direct Share to the Resonate account identifier provided by your contact. Outputs appear in your Snowflake account under Private Sharing.
Amazon S3. Provide your AWS user/role ARN and account ID to your Resonate contact. You'll receive a Resonate role ARN and external ID. Attach an IAM policy allowing your role to assume the Resonate role, then configure an AWS CLI profile with the Resonate credentials. Upload with aws s3 cp to the inbound path; retrieve outputs from the outbound path.
Full step-by-step setup instructions for each destination are available from your Customer Success Manager.
What happens after your file arrives
Match validation — your IDs are matched against Resonate's identity graph. Match rate is shared with you.
Statistical viability check — if the matched universe is below the minimum threshold for reliable clustering, the engagement pauses and the team advises on supplementing the file.
Segmentation build — clustering runs on your matched population.
Segment naming — each segment is analyzed and given a name and description.
Delivery — outputs are placed in your chosen destination and you're notified.
What you receive
Segmented customer file
Named segment report (PowerPoint)
Questions? Contact your Customer Success Manager or resonatesupport@resonate.com.
Comments
0 comments
Article is closed for comments.