Question 1

What can I sync from Snowflake into Customer.io?

Accepted Answer

People and their attributes, custom objects, segments, person events and people devices. That covers most of what a messaging tool needs: who someone is, what they did, and which group they belong to. Devices are append only, so they are added rather than matched and updated. Everything else follows the usual matching rules, where you map a field from your Snowflake model to the identifier Customer.io uses.

Question 2

Do I need to create attributes in Customer.io before syncing?

Accepted Answer

No. New attributes and properties can be declared directly in the mapping for people, events and custom objects, so you can push a new field from your model without setting it up on the Customer.io side first. This is genuinely useful, because it means adding a churn score or a plan tier to your messaging is a change in one place rather than two.

Question 3

What happens if a person in my Snowflake model does not exist in Customer.io?

Accepted Answer

It depends on the mode you choose. Update or create will create them. Update only will skip them. Create only will create them and leave existing matches untouched. Pick based on whether Customer.io or your data warehouse should be the source of new people. If a related record referenced in a mapping cannot be found, Customer.io can optionally ignore the bad relationship and still write the base record rather than failing it.

Question 4

What happens when a record fails to sync?

Accepted Answer

One bad record does not stop the run. The failure is isolated and logged while the rest continue, and it shows up in Sync History with the identity value and the error message, which you can usually download. Temporary failures get retried automatically. For anything that needs a fix first, you can retry records by hand from History, or switch on the setting that retries failed records automatically on the next run.

Question 5

Why use reverse ETL to power Customer.io campaigns?

Accepted Answer

Because the segments worth messaging rarely live in the messaging tool. Things like usage trends, account health or predicted churn get built in your data warehouse from several systems at once, and rebuilding that logic inside Customer.io would mean maintaining it twice. Reverse ETL pushes the model you already trust into Customer.io, so campaigns fire on the same definitions your reporting uses.

Sync Snowflake to Customer.io

Sync Snowflake to Customer.io with Polytomic

People, events and objects

New attributes on the fly

Create, update or both

Trusted by businesses worldwide

Step-by-step integration guide

Connect Snowflake in Polytomic

Connect Customer.io in Polytomic

Create a sync between Snowflake and Customer.io

Map fields and enable the sync

Frequently asked questions

The sync and ETL platform that does it all

Powerful data sync

Advanced analytics

Enterprise security

Easy setup

Ready to connect Snowflake with Customer.io?