Release Notes

August 2024

You can now exclude any of the SendGrid tables from the sync.

October 2020

We have added support for marketing.read API permission for our SendGrid Legacy accounts. You can now retrieve data from both legacy and new SendGrid marketing campaigns. We have also enabled backward compatibility. You can execute the queries designed for the old schema without any modifications on the new data.

We have added support for marketing_campaign.read API permission for our SendGrid New accounts. You can now retrieve data from both new and legacy SendGrid marketing campaigns.

July 2020

We have updated our connector to support SendGrid accounts based on both New Marketing Campaigns and Legacy Marketing Campaigns. SendGrid released a new set of API endpoints under new marketing campaigns and will be deprecating their legacy marketing campaigns API.

We have integrated the new endpoints to support users using the new SendGrid platform. We now use the latest SendGrid API v3 to sync data from SendGrid.

As part of the update, we now classify the connector based on the SendGrid account type you are using. We have adopted custom sync strategies for each connector type:

• Legacy: If you are using a legacy SendGrid account and have configured your connector with a legacy API key, we classify the connector as Legacy. We upsert the legacy tables in to the destination. See the schema information for details on the legacy tables. This schema applies to all legacy SendGrid connectors created before July 20, 2020.

  IMPORTANT: We recommend you to switch to a new marketing campaign account, as SendGrid will deprecate the legacy APIs in the near future. We won't be able to support connectors configured with legacy API keys.

• Upgraded: If you were using a legacy SendGrid account and had configured your connector with a legacy API key, but have migrated your account to a new marketing campaign account, and also configured the connector with the new API key, we classify the connector as Upgraded. We upsert data from both new marketing tables and mapped legacy tables into the destination to support your existing queries on the legacy tables.

  NOTE: We recommend you to create new queries on the new tables to replace your existing queries on the legacy tables.

• New: If you have a new SendGrid account, and have created a new connector using a new API key, we classify the connector as New. We upsert the new marketing tables into the destination. See the schema information for details on the new marketing tables. This schema applies to all new SendGrid connectors created after July 20, 2020.

May 2018

We have renamed the CAMPAIGN_CATEGORY table to CATEGORY. It has a foreign key relationship to the EVENT table.

We have made the following changes to the EVENT table:

• The primary key is now _fivetran_id.
• We have renamed the id field to sg_event_id.