Question 1

Will this overwrite unsubscribes?

Accepted Answer

No. Polytomic writes contacts and their fields, while suppression groups, bounces and unsubscribes live on the SendGrid side untouched. A contact you send that is already suppressed stays suppressed, which is the behaviour you want rather than a compliance problem.

Question 2

How does list membership work?

Accepted Answer

Drive it from the query. Whoever the source returns is who ends up on the list, so the segment definition lives in SQL where it can be reviewed, rather than in a filter somebody built in the interface a year ago.

Question 3

Which fields can I write?

Accepted Answer

SendGrid's reserved contact fields such as email, first name, last name and country, plus any custom fields you have defined. Custom fields have to exist in SendGrid before a sync can map to them.

Question 4

How often should this run?

Accepted Answer

Match it to the sending schedule rather than to the data. Refreshing contacts an hour before a campaign goes out matters. Refreshing them every ten minutes only spends your source database's read budget.

Question 5

What is the source read doing meanwhile?

Accepted Answer

Either a full table read or a tracking field read, since Azure SQL has no change stream. On a contacts table filtered through a view, a full read is usually so light that configuring a tracking field is not worth the effort.

Sync Azure SQL to Twilio SendGrid

Sync Azure SQL to Twilio SendGrid with Polytomic

One way write

Contacts and lists

Custom fields mapped

Trusted by businesses worldwide

Step-by-step integration guide

Connect Azure SQL in Polytomic

Connect Twilio SendGrid in Polytomic

Create a sync between Azure SQL and Twilio SendGrid

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 Azure SQL with Twilio SendGrid?