Snowflake is a cloud data platform for storing, processing, and analyzing data with SQL. This workflow shares selected customer history with Amperity through Secure Data Sharing. Amperity resolves identity and prepares subscriber identifiers for segment delivery to Attentive using its SFTP upload process.

Attentive is a customer messaging platform for SMS and email. Subscriber segments organize eligible customers for marketing use, while subscriber status determines permission to message them. This workflow supplies segment membership through SFTP; your team manages campaign content, messaging decisions, and current subscription status in Attentive.

Snowflake to Attentive

Q: How does Snowflake data reach Attentive subscriber segments?

An inbound Amperity Bridge accesses selected Snowflake history through Secure Data Sharing. Amperity defines the audience and exports Phone or Email values with segment_name. Its Attentive audience destination delivers the CSV through SFTP, where Attentive processes the file and updates the named subscriber segment.

Q: Does uploading an Attentive segment subscribe new customers?

No, the Subscriber Segment Upload process ignores identifiers that do not match active, opted-in subscribers in your Attentive program. Segment delivery does not establish messaging consent or change subscription status. Attentive remains the source of truth for those permissions, and the team configures messaging separately.

Q: How do Attentive segment updates work?

Reusing an existing segment name replaces that segment’s membership list, so send the full current list rather than only additions. Allow up to 24 hours after Amperity finishes sending for updates to appear. Verify the resulting segment in Attentive before using it for a campaign.

Prepare Attentive subscriber segments from Snowflake customer history through Amperity, using Snowflake Secure Data Sharing inbound, identity resolution and audience selection in Amperity, and Attentive Subscriber Segment Upload over SFTP outbound.

See the Attentive docs Snowflake Bridge docs

How to send Snowflake data to Attentive

Share selected Snowflake history. Configure secure views and an inbound Amperity Bridge using Snowflake Secure Data Sharing.
Select eligible subscribers. Use customer history available in Amperity to prepare Phone or Email values with the destination segment_name.
Upload the full segment. Send the configured CSV through SFTP and verify the processed membership in Attentive before preparing messaging.

Prepare Attentive subscriber segments from customer history

Build lapsed-buyer segments from available purchase history.

Prepare store-buyer segments for eligible subscriber follow-up.

Refresh named segments with their full current membership.

Separate phone-based and email-based subscriber audiences.

What the Snowflake to Attentive connection supports

Audience or field	Mapping and behavior	Documentation
Subscriber identifier	Send Phone or Email with segment_name; use one identifier type per file.	Amperity docs; Vendor reference
Eligibility	Unmatched identifiers and subscribers who are not active and opted in are ignored.	Amperity docs; Vendor reference
Segment replacement	Reusing a segment name replaces its membership; send the full current list.	Amperity docs; Vendor reference
CSV delivery	Use the required filename and no header; maximum 500,000 rows per file. Confirm multi-file processing before splitting a segment.	Amperity docs; Vendor reference
Availability	Allow up to 24 hours after Amperity finishes sending; verify the segment in Attentive.	Amperity docs; Vendor reference

Use customer history to choose eligible Attentive subscribers

Find lapsed buyers worth re-engaging

Use available purchase history to define a lapsed-buyer audience in Amperity. Send the subscriber identifiers through the configured SFTP process. Attentive retains only matching active, opted-in subscribers; the team reviews that segment and prepares a relevant re-engagement message there.

Follow up after a store purchase

Select eligible store buyers using transaction history shared from Snowflake. Deliver the full list under a clear segment name so the team can review membership in Attentive before messaging. Refresh the complete segment as customers enter or leave the chosen audience.

Set up the Snowflake to Attentive workflow

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

Ask Attentive Support to enable subscriber segment uploads and confirm the identifier, SFTP folder and file format. Validate a sandbox sample and processed membership before production; Attentive retains subscription authority. Follow the Attentive audience destination setup.

Snowflake to Attentive integration FAQs

What is Snowflake?

What is Attentive?

How does Snowflake data reach Attentive subscriber segments?

Does uploading an Attentive segment subscribe new customers?

How do Attentive segment updates work?

Put customer context to work in Attentive

Explore how purchase history can help your team choose the next Attentive subscriber audience.

Get a demo