Release Notes

October 2025

We unified each connector’s pre-built dbt Core*–compatible data models into a single model. It standardizes and documents the Fivetran schemas created in your destination and outputs analytics-ready tables. Previously, most connectors used distinct source and transform models.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

June 2025

We have added a new Quickstart package for the Microsoft Dynamics 365 CRM connector.

We have updated the Quickstart packages for the following connectors:

Connectors supporting the Ad Reporting data model to version 1.15.0.
Connectors supporting the App Reporting data model to version 0.6.0.
Connectors supporting the Shopify Holistic Reporting data model to version 0.8.0.
Amazon Ads to version 0.5.0.
Amplitude to version 0.7.0.
Apple App Store to version 0.6.0.
Apple Search Ads to version 0.6.0.
Asana to version 0.9.0.
Facebook Ads to version 0.10.0.
Fivetran Platform to version 2.2.0.
GitHub to version 0.9.0.
Google Ads to version 0.14.0.
Google Play to version 0.5.0.
Greenhouse to version 0.9.0.
HubSpot to version 0.24.0.
Intercom to version 0.10.0.
Jira to version 0.21.0.
Klaviyo to version 0.9.0.
Lever to version 0.8.0.
LinkedIn Ad Analytics to version 0.12.0.
Mailchimp to version 0.12.0.
Microsoft Advertising to version 0.12.0.
Mixpanel to version 0.13.0.
NetSuite SuiteAnalytics to version 0.20.0.
Pendo to version 0.6.0.
Pinterest Ads to version 0.13.0.
QuickBooks to version 0.20.0.
Recurly to version 0.7.0.
Reddit Ads to version 0.5.0.
Sage Intacct to version 0.7.0.
Salesforce to version 1.3.0.
Snapchat Ads to version 0.10.0.
Stripe to version 0.19.0.
TikTok Ads to version 0.9.0.
Twilio to version 0.5.0.
Twitter Ads to version 0.10.0.
Workday HCM to version 0.4.0.
Zendesk Support to version 0.24.1.

April 2025

We have updated the Quickstart packages for the following connectors:

Facebook Ads to version 0.9.0
Google Ads to version 0.12.0
HubSpot to version 0.23.0
LinkedIn Ad Analytics to version 0.11.0
Microsoft Advertising to version 0.11.1
NetSuite SuiteAnalytics to version 0.19.0
Pinterest to version 0.12.0
Recharge to version 0.3.1
Reddit Ads to version 0.4.0
TikTok Ads to version 0.8.0
Twitter Ads to version 0.9.0
Xero to version 0.9.0
Zuora to version 0.4.0

April 2024

We have added new Quickstart packages for the following connectors:

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

June 2023

We have added the following new tables:

ACCOUNT_METROS_REPORT
CAMPAIGN_METROS_REPORT
FUNDING_INSTRUMENT_METROS_REPORT
LINE_ITEM_METROS_REPORT
PROMOTED_TWEET_METROS_REPORT
PROMOTED_ACCOUNT_METROS_REPORT

We have updated the following tables:

TABLE	REMOVED COLUMN(S)	REMOVED PRIMARY KEY	NEW COLUMN(S)
`ACCOUNT_CITIES_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`ACCOUNT_LOCATIONS_REPORT`	`segment`		`segment_name`, `segment_value`
`ACCOUNT_POSTAL_CODES_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`ACCOUNT_REGIONS_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`CAMPAIGN_CITIES_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`CAMPAIGN_LOCATIONS_REPORT`	`segment`		`segment_name`, `segment_value`
`CAMPAIGN_POSTAL_CODES_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`CAMPAIGN_REGIONS_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`FUNDING_INSTRUMENT_CITIES_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`FUNDING_INSTRUMENT_LOCATIONS_REPORT`	`segment`		`segment_name`, `segment_value`
`FUNDING_INSTRUMENT_POSTAL_CODES_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`FUNDING_INSTRUMENT_REGIONS_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`LINE_ITEM_CITIES_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`LINE_ITEM_LOCATIONS_REPORT`	`segment`		`segment_name`, `segment_value`
`LINE_ITEM_POSTAL_CODES_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`LINE_ITEM_REGIONS_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`PROMOTED_TWEET_CITIES_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`PROMOTED_TWEET_LOCATIONS_REPORT`	`segment`		`segment_name`, `segment_value`
`PROMOTED_TWEET_POSTAL_CODES_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`PROMOTED_TWEET_REGIONS_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`PROMOTED_ACCOUNT_CITIES_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`PROMOTED_ACCOUNT_LOCATIONS_REPORT`	`segment`		`segment_name`, `segment_value`
`PROMOTED_ACCOUNT_POSTAL_CODES_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`
`PROMOTED_ACCOUNT_REGIONS_REPORT`	`segment`, `location_name`, `location_type`	`country_name`	`segment_name`, `segment_value`

This change is enabled by default for connections created after June 12, 2023. We are gradually rolling this out to all existing connections and will notify all users beforehand.

March 2023

You can now select or deselect the following tables to sync from the Schema tab on your connector details page:

CAMPAIGN_HISTORY
CARD_HISTORY
FUNDING_INSTRUMENT_HISTORY
LINE_ITEM_HISTORY
TWEET

August 2022

We have added a new column, budget_optimization, to the CAMPAIGN_HISTORY table to support Twitter API version 11.

We have upgraded our Twitter Ads connector from version 10 to version 11 of the Twitter API.

May 2022

We have changed the segmentation of the line_item_cities_report report.

We have renamed the country_name column to location_name.

We have added a new column, location_type.

December 2021

We have added a new column, duration, to the MEDIA_LIBRARY table for storing video length values.

February 2021

We now support syncing data for the media_creative entity. See our MEDIA CREATIVE table documentation for more information.

November 2020

We now support Twitter Ads API v8.

We have added the following new report tables to support Reach and Average Frequency:

CAMPAIGN_REACH_DAILY_REPORT
CAMPAIGN_REACH_MONTHLY_REPORT
FUNDING_INSTRUMENT_REACH_DAILY_REPORT
FUNDING_INSTRUMENT_REACH_MONTHLY_REPORT

We have added a new table, PREROLL_CALL_TO_ACTIONS_HISTORY, which stores the preroll call-to-actions for an account. See Twitter's documentation for more information.

We have removed the video_mrc_views field from the analytics tables. The video_total_views field stores the same data.

October 2020

We have released pre-built, dbt Core-compatible data models for Twitter Ads. Find the models in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation*.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

August 2020

We now support syncing data from the reporting tables for the promoted_account entity. See our PROMOTED ACCOUNT tables for more information.

July 2020

We can now sync the records that you have deleted from the funding_instruments, campaigns, line_items, and promoted_tweets entities.

April 2020

In the MEDIA_CREATIVE_HISTORY table, we have deprecated the serving_status field and replaced it with the entity_status field to support Twitter API v7. We will continue to support the deprecated field for the next three months, so be sure to make the required schema changes by July 3, 2020.

February 2020

We have made multiple schema changes to support Twitter API v6 changes. You can read detailed API documentation on Twitter's website. We will continue to support all deprecated items for the next three months, so be sure to make the required schema changes by May 25, 2020.

We have renamed the CITIES segment to METROS. However, the CITIES sub-string will be present in all analytics tables.
We have added the following fields to the tables below:
- media_key to the CARD_HISTORY table
- poster_media_key and poster_media_url to the MEDIA_LIBRARY table
We have added four new fields to the TWEET table because the Twitter API endpoint has changed from scoped_timeline to tweets:
- tweet_type (DRAFT, PUBLISHED, SCHEDULED)
- media_key
- card_uri
- full_text
We have deprecated and replaced the following fields in the tables below:
- text with full_text in the TWEET table
- video_poster_url with poster_media_url in the CARD_HISTORY table
- media_id and video_content_id with media_key in the ACCOUNT_MEDIA_HISTORY table
- image, wide_app_image, and video_url with media_url in the CARD_HISTORY table
We have deprecated the following fields from the tables below:
- media_ids from the SCHEDULED_TWEETS table
- video_hls_url from the CARD_HISTORY table
We will stop syncing data from the VIDEO_APP_DOWNLOAD_CARD, VIDEO_CONVERSATION_CARD, VIDEO_DIRECT_MESSAGE_CARD, and VIDEO_WEBSITE_CARD tables to the CARD_HISTORY table. However, we will continue syncing the data from the VIDEO_POLLS table to the CARD_HISTORY table.

January 2020

We have deprecated the include_sentiment field from the LINE_ITEM_HISTORY table because the Twitter Ads API no longer supports it. To learn more, see Twitter's API documentation.

November 2019

We have improved the sync speed for our Twitter Ads connector.

Previously, we made one API call per entity ID per day of data during syncs. We therefore had to make a large number of API calls when we fetched data for multiple entity IDs and/or for multiple days' worth of data. Making so many API calls slowed down our syncs.

Now Fivetran can fetch multiple days' worth of data for up to 20 entity IDs in a single API call, which makes syncs significantly faster.

August 2019

We released a new version of our Twitter Ads connector, service version 2. You can now select how many months' worth of data you'd like to include in your initial sync. Choose from the following options:

3 months
6 months
12 months
24 months
All time

Twitter Ads connectors running on service version 0 and 1 will sunset on November 21, 2019. If you are using either of these service versions, upgrade to the newest version by creating a new Twitter Ads connector and syncing into a new schema.

July 2019

You can now configure your Twitter Ads connector through the Fivetran REST API. This feature is in BETA and available only for Standard and Enterprise accounts.

If we encounter insufficient permissions when we try to sync endpoints for a specific account, then we skip that endpoint for that account and give a warning in the dashboard. The warning includes endpoints with their respective accounts as follows.

Account ID	Skipped Endpoints
account_1	endpoint_1
	endpoint_2
account_2	endpoint_1

If you receive this warning, give Account Administrator permissions for that account to the user which you used to create your Twitter Ads App.

February 2019

We upgraded the connector to Twitter Ads API version v4. Read more about their new version on Twitter's documentation. As part of the upgrade, we have made the following schema changes:

Removed the VIDEO_HISTORY and VIDEO_REASON_HISTORY tables as Twitter deprecated the videos endpoint.
Removed the preview_url column from the CARD_HISTORY table.
Renamed the app_country_code column of the CARD_HISTORY table to country_code.

July 2018

Twitter Ads provides a history of the settings and detailed reports of your Twitter Ad Accounts, Campaigns, Line Items, Tweets, and Media Creatives.

Read our Twitter Ads connector documentation.