We now support syncing data for the
media_creative entity. See our MEDIA CREATIVE table documentation for more information.
We now support Twitter Ads API v8.
We have added the following new report tables to support Reach and Average Frequency:
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.
We now support syncing data from the reporting tables for the
promoted_account entity. See our PROMOTED ACCOUNT tables for more information.
We can now sync the records that you have deleted from 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.
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:
We have added four new fields to the
TWEETtable because the Twitter API endpoint has changed from
tweet_type(DRAFT, PUBLISHED, SCHEDULED)
We have deprecated and replaced the following fields in the tables below:
We have deprecated the following fields from the tables below:
We will stop syncing data from the
VIDEO_WEBSITE_CARDtables to the
CARD_HISTORYtable. However, we will continue syncing the data from the
VIDEO_POLLStable to the
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.
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 of data. Making so many API calls slowed down our syncs.
Now Fivetran can fetch multiple days of data for up to 20 entity IDs in a single API call, which makes syncs significantly faster.
We released a new version of our Twitter Ads connector, service version 2. You can now select how many months 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, please upgrade to the newest version by creating a new Twitter Ads connector and syncing into a new schema.
- 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|
If you receive this warning, give Account Administrator permissions for that account to the user which you used to create your Twitter Ads App.
We upgraded Twitter Ads API version to v4. Read more about their new version on Twitter’s documentation. This upgrade means the following changes to the schema:
VIDEO_REASON_HISTORYtables as Twitter deprecated the
- Removed column
- From now on the column
CARD_HISTORYwill be delivered as
Twitter Ads provides a history of the settings and detailed reports of your Twitter Ad Accounts, Campaigns, Line Items, Tweets, and Media Creatives.