Question 1

What can I write from BigQuery into Front?

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 your data warehouse but not written to. Accounts and contacts are the practical targets anyway, since they hold the context somebody needs the moment a message lands.

Question 2

How do I avoid creating duplicate contacts in Front?

Accepted Answer

By matching on an identity field you choose. Map one field from your BigQuery 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 single thing that stops a reverse ETL sync quietly filling a tool with near duplicates.

Question 3

What if a contact in my model is not in Front?

Accepted Answer

It follows the sync mode. Update or create will create the contact, update only will skip it, and create only will create new ones while leaving existing matches alone. If your model covers more people than Front should know about, update only is usually the sensible setting, since it enriches the contacts already there without importing everyone you have ever recorded.

Question 4

Will a small sync to Front still cost BigQuery query spend?

Accepted Answer

Yes, and it is easy to miss because the destination is tiny. Every run executes a BigQuery query, and on demand pricing charges by bytes processed rather than rows returned, so a narrow result from a wide table can still be expensive. Select only the columns you map, filter inside the model, and set a tracking field so runs read forward from the last mark instead of scanning everything again.

Question 5

What does a support team gain from warehouse data in Front?

Accepted Answer

Context at the moment of reply, rather than after a search. A shared inbox knows an email address and a message. Whether that person is on a trial, spends a lot, or renews next month sits in your data warehouse. Putting those fields on the contact and account records means replies can be triaged by value and written with some idea of who is asking, instead of treating every message as identical until somebody digs.

Sync BigQuery to Front

Sync BigQuery to Front with Polytomic

Contacts and accounts

Match on a field you pick

Only changed rows go

Or sync Front to BigQuery

Trusted by businesses worldwide

Step-by-step integration guide

Connect BigQuery in Polytomic

Connect Front in Polytomic

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