Question 1

Which Front objects accept writes from Redshift?

Accepted Answer

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

Question 2

What decides whether a contact updates or a new one is created?

Accepted Answer

The identity field you map, together with the sync mode. Map one column from your model, usually an email address, to the identity field on the Front object. Polytomic looks the record up on that pair, and a match counts as existing. Then update or create makes the missing ones, update only skips them, and create only adds new ones without touching matches. Most duplicate problems come from a loose identity mapping rather than the mode.

Question 3

Will this sync affect cluster performance?

Accepted Answer

Only as much as the query behind it. Reverse ETL reads are ordinary Redshift queries, so a wide model over a large table costs the same as anyone running that query by hand, and Polytomic does not set its own query group or slot count. For a destination like Front the model is usually small, so the honest answer is that this one is unlikely to be your problem. Still worth a read only user with its own workload management queue if the cluster is already tight.

Question 4

Should the warehouse create contacts in Front?

Accepted Answer

Usually not. If your model covers everyone you have ever recorded, update or create will import all of them into a shared inbox tool where they add noise rather than value. Update only is normally the better setting here, enriching contacts Front already knows about because someone actually wrote in, and leaving the rest alone.

Question 5

How does this help someone triage a busy inbox?

Accepted Answer

By making priority visible without a lookup. A shared inbox shows an address and a message, so every conversation looks the same until somebody investigates. With plan, spend, usage and renewal date already on the contact and account records, the queue can be sorted by what matters and replies can be written with some sense of who is asking, which is the difference between fast and merely quick.

Sync Redshift to Front

Sync Redshift to Front with Polytomic

Contacts and accounts

Matching prevents duplicates

Keeps cluster load small

Or sync Front to Redshift

Trusted by businesses worldwide

Step-by-step integration guide

Connect Redshift in Polytomic

Connect Front in Polytomic

Create a sync between Redshift 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 Redshift with Front?