Release Notes

April 2026

We've implemented a new mechanism to fetch source schema quicker when creating a new connection. Now, instead of deriving the schema from source data, we use fixed schema models. This allows you to see the schema blocking and hashing screen almost immediately after creating a new connection.

As a result of this improvement, you may see empty tables and columns in the Schema tab of existing connections that have not yet synced to your destination.

We've added the following new columns to the PROMOTED_LINK_HISTORY table:

• creative_format
• description
• title

We've added the cpm, roas, and total_roas columns to the following tables:

• CAMPAIGN_REPORT
• PROMOTED_LINK_REPORT
• GEOLOCATION_REPORT
• SECTION_REPORT
• PUBLISHER_REPORT

We've added a new table, CROP_POINT. The table contains crop point data associated with image metadata entries.

After optimizing schema fetch for the connectors below, these connections no longer use the pre-initial-sync schema capture flow described in schema_status.

Affected connectors

• Adyen
• Amazon Ads
• Amplitude
• AWS CloudTrail
• Coupa
• Facebook Pages
• GitHub
• Instagram Business
• Apple App Store
• LinkedIn Company Pages
• Outbrain
• SAP Business ByDesign
• Shopify
• Twilio
• Twitter
• Workday Financial Management
• Workday HCM
• Xero
• YouTube Analytics

REST API request changes (breaking)

For the connectors listed above, the schema_status request field is no longer supported in:

• Update a Connection

If your automation still sends schema_status for these connectors, requests may fail.

REST API response changes

For the connectors listed above, schema_status is no longer returned for flows that previously exposed it, including:

• List All Connections
• Create a Connection
• Retrieve Connection Details
• Update a Connection
• Run Connection Setup Tests
• List All Connections within a Group

If your downstream transformations or orchestration rely on this field, update them to handle its absence.

Dashboard flow change

In the Fivetran dashboard, these connectors no longer show the schema prefetch and review step before initial sync. After connection creation, you proceed directly to the initial sync flow.

January 2026

We've added the following columns to the CAMPAIGN_REPORT, GEOLOCATION_REPORT, PROMOTED_LINK_REPORT, PUBLISHER_REPORT, and SECTION_REPORT tables:

• videoReachedFirstQ
• videoReachedSecondQ
• videoReachedThirdQ
• videoReachedCompletion
• videoAvgViewDuration
• clicksOnVideo
• videoActiveCompletions
• videoActiveCompletionsPercentage
• videoPlays

February 2024

We have added the Pull archived campaigns option for reports in the setup form. If you want to sync data for archived campaigns, set the toggle to ON. For more information, see our Outbrain documentation.

January 2024

We have added a new table, CAMPAIGN_CONVERSION_REPORT, which has a composite primary key consisting of the day, campaign_id, name, and platform columns. The campaign_id column refers to the CAMPAIGN_HISTORY table. We have made this change to sync campaign-related conversion metrics.

January 2023

We have updated the endpoint we use to retrieve the PROMOTED_LINK_REPORT table. Learn more in Outbrain's API documentation.

April 2022

The Outbrain connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Outbrain's priority-first syncs fetch the most recent 30 days' worth of data from the reporting tables.

To learn more, see our priority-first sync documentation.

November 2021

We have added a new table, PUBLISHER_REPORT, which stores metrics of publishers.

August 2021

Our Outbrain connector now supports multithreading. We now use multiple parallel API requests to sync data from your Outbrain account to your destination, which makes your syncs faster. The connector’s sync speed depends on your Outbrain API quota and account metadata.

July 2021

We have added a new table, IMAGE_METADATA.

We have added the following columns to the PROMOTED_LINK_HISTORY table:

• image_metadata_id
• call_to_action_type
• call_to_action_value
• cpc_adjustment

We have added the following columns to the CAMPAIGN_HISTORY table:

• targets_exclude_ad_block_users
• targets_include_cellular_network
• targets_native_placements_enabled

June 2020

We have removed the following fields from the tables below:

• status from the PROMOTED_LINK_HISTORY table

• total_value from the CAMPAIGN_REPORT, GEOLOCATION_REPORT, PROMOTED_LINK_REPORT, and SECTION_REPORT tables

January 2020

We have made a number of schema changes to support Outbrain's API documentation.

We have added the following columns to all _REPORT tables:

• sum_value
• total_sum_value
• view_sum_value
• total_average_value
• view_average_value
• view_conversion_rate
• total_conversions
• views_conversions
• total_cpa

We have added the approval_status and approval_status_is_editable columns to the PROMOTED_LINK_HISTORY table.

We will discontinue the status column in the PROMOTED_LINK_HISTORY table on May 1, 2020. This data will then appear in the approval_status column.

We will discontinue the total_value column in all _REPORT tables on May 1, 2020. This data will then appear in the sum_value column.

To learn more, see our Outbrain schema information.

October 2019

You can now select how many months' worth of reporting data you'd like to include in your initial sync. Choose from the following options:

• 3 months
• 6 months
• 12 months (default)
• 24 months
• All time

July 2018

Outbrain is a native advertising platform using targeted advertising to recommend articles, slideshows, blog posts, photos or videos to a reader.

Read our Outbrain connector documentation.