Understanding Your Resonate Append Deliverables

Turn first-party data into competitive advantage with enriched, person-level intelligence that fuels deeper audience understanding, precision targeting, personalized engagement, and more predictive models—delivering higher ROI and stronger performance across every stage of the customer journey.

This article provides details on the deliverables you will receive and guidance on joining your appended records to your customer database with confidence.

Note: Deliverables vary by delivery method. This article covers three sections: Standard File Append, Enrichment API, and Snowflake Clean Room. Jump to the section that matches your implementation.

• Standard File Append Deliverables
• Enrichment API Deliverables
• Snowflake Clean Room Deliverables

Standard File Append Deliverables

What will Resonate deliver and where?

We provide three files to help your data science or analytics team join the enriched records to your database, interpret and analyze them:

• Output File – A compressed CSV of your enriched customer records with attributes appended to each matched Customer ID. Available in Standard or Pivoted format. Attributes are represented as “Survey_value_Key” numeric strings (e.g., 422753) to keep file sizes efficient for ingestion.
• Key Definitions File – A reference guide mapping each survey_value_key to its human-readable definition (e.g., 422753 = “age group 18–24”).
• Summary Report – An overview of attribute counts and percentages to support QA and verify that your Output and Key Definitions files are correctly aligned.

The Output File will be delivered to the location you used to send us your files (Snowflake, AWS, Box, or SFTP):

• Snowflake: output file is located under the “Data Sharing” section of the account used to share the input table.
• AWS: output file is available in the same folder used to send input data.
• SFTP: follow the Resonate SFTP delivery steps.
• Box: follow the Box delivery steps.

The Key Definitions File and Summary Report are delivered via email.

Deliverable 1: Your Output File

Resonate returns your enriched file with the selected attributes appended to each matched record. You can choose to receive either a Standard or Pivot file format:

• Standard Output File: one row per matched ID with comma-separated attribute keys. Ideal for direct integration into analytics environments, dashboards, or downstream workflows.
• Pivoted Output File: one row per matched ID with each attribute in its own column. Best for flexible ingestion into systems that prefer event-style data or a single-column-value structure.

Standard Output File Format

The Standard Append Output File is a .csv with 4 columns:

• Column 1: Customer IDs from your input file that were matched to Resonate IDs. Only matched IDs are returned.
• Column 2: Match type — “Direct Match” (HEM or MAID matched directly) or “Household” (predictions from relevant HEM found in the household).
• Column 3: Comma-separated list of survey value keys for attributes that are TRUE for that ID. False attributes are excluded.
• Column 4: Comma-separated list of redacted survey value keys for sensitive attributes in restricted states.

Pivoted Output File Format

The Pivoted Append Output File is a .csv with one column per attribute:

• Column 1: Matched Customer IDs.
• Column 2: Match type (“Direct Match” or “Household”).
• Column 3+: One column per survey value key. A 1 indicates TRUE, 0 indicates FALSE, and NULL indicates a redacted sensitive attribute for a restricted state.

Deliverable 2: Your Key Definitions File

This file maps survey value keys to their human-readable attribute names and definitions.

• Map keys from Column 3 of the Standard output (or Column 3+ of the Pivoted output) to the “survey_value_keys” column in this file.
• Lists all clusters or attributes purchased and all possible attribute values.
• Example: key 422753 = “age group 18–24”
• Indicates whether each attribute was derived from a single-select or multi-select question.

Deliverable 3: Your Summary Report

Use this file to verify that your Output and Key Definitions files are correctly aligned. After receiving and formatting the files, perform a QA check by comparing your formatted data against the metrics in the Summary Report.

Note: since sensitive data is redacted for individuals in restricted states, percentage values for mutually exclusive answers may no longer sum to 100%.

The Summary Report includes:

• Columns A–E: Full taxonomy of each attribute value.
• SURVEYVALUEKEY: The key corresponding to each attribute as reflected in the output file.
• DISTINCT_COUNT: Total number of IDs for which the attribute is true.
• PERCENTAGE: Percentage of records for which the attribute is true.

Joining the Output File Back to Your Customer Database

Resonate output files are best ingested with the help of your analytics or data science team. Due to file size and data volume, these files require more advanced technical resources and are difficult to analyze in tools like Excel.

Example: Standard Output File

After referencing the Key Definitions File:

In the Standard Output File, only keys where the attribute value = TRUE are included. To see all possible attribute values (including FALSE), refer to the Key Definitions File.

Example: Pivoted Output File

In the Pivoted Output File, both TRUE (1) and FALSE (0) values are included for all attributes. NULL indicates a redacted sensitive attribute.

What’s Next?

Once you’ve reviewed your enriched file, you can begin applying the insights across targeting, segmentation, or model scoring. If you have questions about how to best apply or activate your data, your Resonate team is here to help.

Need more help? Please contact your Customer Success Manager or reach out to resonatesupport@resonate.com.

Enrichment API Deliverables

The Enrichment API returns enriched attribute data in real time—there are no batch files to download or merge. Instead of receiving a separate output file, your application receives enriched attribute values directly in the API response at the moment of the call. This section explains what the API returns, how to interpret it, and how to validate your integration. For full technical setup, see the Enrichment API documentation.

What will Resonate deliver?

Because the Enrichment API is real-time and record-level, deliverables differ from file-based append. The following summarizes what you will receive:

Deliverable 1: The API Enrichment Response

Each API call returns a JSON response containing the enriched attribute values for the matched record. Sensitive attributes subject to state-level privacy restrictions will be redacted as “null” from the response.

Key fields in the response include:

• attributes - 1 for true and 0 for false
• type - IP, HEM
• lastUpdated - last time the attributes for this id was updated.
• sensitive attributes are null under attributes

Deliverable 2: Attribute Key Definitions File

Resonate will provide an Attribute Key Definitions File that maps survey_value_keys to human-readable attribute definitions. Use this guide to interpret the keys returned in your API responses.

Example: a survey_value_key of 422753 in the API response maps to “age group 18–24” in the Attribute Reference Guide.

This guide is shared by your Resonate team and should be stored and referenced by your engineering or analytics team when processing API responses.

How to Interpret API Responses

Interpreting API responses:

• attributes - 1 for true and 0 for false
• sensitive attributes are “null” under attributes

Use the Attribute Reference Guide to translate any survey_value_key to its full human-readable definition, exactly as you would with the Key Definitions File in standard append.

What’s Next?

Once your integration is validated and live, enriched attributes are returned in real time and can be written directly into your CRM, CDP, or application database. From there, you can activate the data for targeting, personalization, and analytics.

If you have questions about your API integration or need help interpreting results, contact your Customer Success Manager or reach out to resonatesupport@resonate.com.

Snowflake Clean Room Deliverables

The Snowflake Clean Room enables privacy-safe, Snowflake-native enrichment without your data ever leaving your Snowflake environment. Instead of receiving files externally, your enriched output is delivered directly as a table within your Snowflake account. This section explains what Resonate delivers, where to find it, and how to interpret and QA the results. For full setup details, see the Snowflake Clean Room documentation.

What will Resonate deliver?

Clean Room deliverables combine a Snowflake-native output table with supporting reference files delivered via Snowflake:

Deliverable 1: Your Enriched Output Table

Resonate delivers an enriched output table directly into your Snowflake environment. This table contains your matched records with attributes appended.

Key characteristics of the output table:

• Customer ID
• Survey Value Key
• “True” if the customer has the attribute value, “Null” if redacted (could be true or false)
• Whether the customer matched on HEM, MAID, or IP

Your team can query the output table directly within Snowflake and join it back to your customer database using the Customer ID column, without ever exporting the data from your environment.

Deliverable 2: Key Definitions File

The Key Definitions File for Clean Room delivery is identical in structure and purpose to the one provided in standard file append. It maps each survey_value_key to its human-readable attribute definition.

This file is delivered via Snowflake. Use it to interpret the attribute keys in your Snowflake output table.

Example: a survey_value_key of 422753 in your output table maps to “age group 18–24” in the Key Definitions File.

Deliverable 3: Summary Report

The Summary Report for Clean Room delivery is slightly different to the one provided in standard file append. It provides match rate and attribute coverage counts to support QA.

Use the Summary Report to:

• Verify that the number of matched records in your Snowflake output table aligns with the report counts
• Confirm attribute coverage percentages match expectations for your customer file
• Identify any attributes with unexpectedly low coverage that may warrant follow-up with your Resonate team

Note: because sensitive attributes are redacted for individuals in restricted states, percentage values for mutually exclusive attributes may not sum to 100%.

How to Interpret Your Clean Room Output

Interpreting the Clean Room output table follows the same logic as the Standard and Pivoted Output Files in file-based append. The key difference is that your data lives in Snowflake and can be queried directly rather than ingested from a downloaded file.

Example:

After joining with the Key Definitions File:

You can join the Snowflake output table back to your customer database directly within Snowflake using a SQL JOIN on the Customer ID column. No file download or external merge step is required.

What’s Next?

Once your enriched output table is available in Snowflake, your team can query it directly to power analysis, segmentation, targeting, and predictive modeling within your existing Snowflake workflows. If you have questions about your Clean Room deliverables or need help interpreting results, contact your Customer Success Manager or reach out to resonatesupport@resonate.com.