Snowflake is a cloud data platform for storing, processing, and analyzing data with SQL. In this workflow, it supplies selected customer history through Secure Data Sharing. Amperity resolves identity and prepares audience records before delivering them to data extensions in Salesforce Marketing Cloud.

Snowflake to Salesforce Marketing Cloud

Q: What is Salesforce Marketing Cloud?

Salesforce Marketing Cloud Engagement provides tools for customer messaging and marketing automation. Data extensions store records and fields that teams can use in their marketing workflows. This connection prepares and imports audience data; campaign configuration, subscription controls, and message sends remain in Salesforce.

Q: How does Snowflake data reach Salesforce Marketing Cloud?

An inbound Amperity Bridge accesses selected Snowflake data through Secure Data Sharing. Amperity builds customer context and prepares an audience with the required subscriber identifier. Its Salesforce Marketing Cloud destination delivers CSV data with API-managed imports into the configured data extension, where the team validates the result.

Q: Does the connector append or replace data extension rows?

The managed destination's Append data setting controls this behavior: enabled, it upserts new rows and updates existing rows. Disabled, it deletes the extension's existing data and replaces it with rows sent from Amperity. Review the selected mode before sending an audience to an existing extension.

Q: Can I deliver files using SFTP only?

Yes: Amperity documents an SFTP-only option that places CSV files in the configured location. Your team must separately configure the data extension, import definition, and process that loads the file into Salesforce. Validate the completed import; successful file delivery alone does not prove the extension was updated.

Bring customer history from Snowflake to Salesforce Marketing Cloud through Amperity, using Snowflake Secure Data Sharing inbound, identity resolution and audience selection in Amperity, then CSV delivery with API-managed data extension imports.

See the SFMC docs Snowflake Bridge docs

How to send Snowflake data to Salesforce Marketing Cloud

Share selected Snowflake data. Configure secure views and an inbound Amperity Bridge using Snowflake Secure Data Sharing.
Select customer records. Resolve identity in Amperity and prepare fields matching the target data extension, preserving its existing subscriber identifier.
Deliver the audience. Send CSV data through the Salesforce Marketing Cloud destination and verify the imported data extension before messaging.

Prepare Salesforce Marketing Cloud data extensions from customer history

Populate loyalty-audience data extensions with eligible customer records.

Refresh recent-buyer data extensions using available purchases.

Preserve subscriber identifiers in exported data extension rows.

Supply purchase-context fields for Salesforce audience selection.

What the Snowflake to Salesforce Marketing Cloud connection supports

Audience or field	Mapping and behavior	Documentation
Data extension	Set a unique name and target business unit for the managed audience.	Amperity docs; Vendor reference
Contact rows	Exported field names and values must match the data extension schema.	Amperity docs; Vendor reference
Subscriber identity	Align subscriber_key with Subscriber Key, or an email variant with Email Address.	Amperity docs; Vendor reference
Managed row updates	Append data enabled upserts rows; disabled deletes existing contents and replaces them with sent rows.	Amperity docs; Vendor reference
SFTP-only alternative	File delivery requires a separately configured data extension, import definition and loading process.	Amperity docs; Vendor reference

Make Snowflake customer context usable in Salesforce

Prepare a loyalty audience

Use loyalty and purchase history available in Amperity to select customers for a Salesforce Marketing Cloud audience. Export the subscriber identifier and relevant attributes into the configured data extension, where the team can review the records and apply its sending controls.

Identify recent buyers for different treatment

Build a recent-buyer audience from history shared through Snowflake and deliver it to a dedicated data extension. The Salesforce team can query those records when deciding whom to include or exclude from messaging. Choose row-update behavior deliberately as the audience changes.

Set up the Snowflake to Salesforce Marketing Cloud workflow

Create a Snowflake share with secure views and the correct Amperity account locator for your stack and region. Check supported data types before configuring the inbound bridge. Follow the Snowflake Bridge setup.

Configure destination credentials, business-unit access, data extension fields and matching subscriber identifiers; disabling Append data replaces the managed extension's existing rows. Validate a sandbox sample and retain Salesforce subscription controls before production. Follow the Salesforce Marketing Cloud destination setup.

Snowflake to Salesforce Marketing Cloud

How to send Snowflake data to Salesforce Marketing Cloud

Prepare Salesforce Marketing Cloud data extensions from customer history

What the Snowflake to Salesforce Marketing Cloud connection supports

Make Snowflake customer context usable in Salesforce

Prepare a loyalty audience

Identify recent buyers for different treatment

Set up the Snowflake to Salesforce Marketing Cloud workflow

Snowflake to Salesforce Marketing Cloud integration FAQs

What is Snowflake?

What is Salesforce Marketing Cloud?

How does Snowflake data reach Salesforce Marketing Cloud?

Does the connector append or replace data extension rows?

Can I deliver files using SFTP only?

Put customer context to work in Salesforce Marketing Cloud