Question 1

What can I write from Snowflake into Front?

Accepted Answer

Accounts and contacts. Everything else in Front is source only, including conversations, channels, contact lists, inboxes, tags, teammates, teams and events, so those can be read into your data warehouse but not written to. Accounts and contacts are the practical targets anyway, since they are the records that carry the context someone needs when a message arrives.

Question 2

How does Polytomic avoid creating duplicate contacts in Front?

Accepted Answer

By matching on an identity field you choose. You map one field from your Snowflake model, usually an email address, to the identity field on the Front object. Polytomic looks the record up on that pair, and a match is treated as an existing contact to update rather than a new one to create. Getting that mapping right is the main thing that keeps a reverse ETL sync from quietly filling a tool with near duplicates.

Question 3

What happens if a contact in my model does not exist in Front?

Accepted Answer

It follows the sync mode. Update or create will create the contact. Update only will skip it. Create only will create the new ones and leave existing matches alone. If your model is broader than your actual customer base, update only is often the sensible setting, since it enriches the people Front already knows about without importing everyone you have ever recorded.

Question 4

What happens when a record fails to sync to Front?

Accepted Answer

One failure does not stop the run. The record is isolated and logged while the others continue, and it shows up in Sync History with the identity value and the error message so you can see what went wrong. Transient errors are retried automatically. Anything needing a fix can be retried by hand from History, or picked up automatically if you enable retrying failed records on the next run.

Question 5

Why use reverse ETL to push customer data into Front?

Accepted Answer

Because whoever answers the message should know the context without going to look for it. Plan, spend, usage and renewal date sit in your data warehouse, not in the inbox. Reverse ETL puts those details on the contact and account records in Front, so replies can be prioritised and personalised from what you actually know rather than from whatever the sender happened to mention.

Sync Snowflake to Front

Sync Snowflake to Front with Polytomic

Contacts and accounts

Match on your own field

Only changed rows

Or sync Front to Snowflake

Trusted by businesses worldwide

Step-by-step integration guide

Connect Snowflake in Polytomic

Connect Front in Polytomic

Create a sync between Snowflake and Front

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 Front?