Skip to main content

Facebook Marketing Migration Guide

Availability
Available CoreAvailable StandardAvailable PlusAvailable ProAvailable Enterprise FlexAvailable Self-Managed EnterpriseAvailable PyAirbyte
Support Level
Airbyte
Connector Version
5.2.14 (last updated 14 days ago)
CDK Version
7.17.4
Sync Success Rate
Usage Rate
Data workers used
0.2 per sync (Learn more)
Definition ID
e7778cfc-e97c-4458-9ecb-b4f2bba8946c

Upgrading to 6.0.0​

Meta deprecated the dma (Nielsen DMA) breakdown effective June 22, 2026, replacing it with comscore_market (Comscore Markets). This is an out-of-cycle change that applies to all API versions immediately.

What changed​

Meta transitioned from Nielsen DMA to Comscore Markets for geographic ad-performance data. The following built-in streams have been replaced:

Removed Stream (v5.x)Replacement Stream (v6.0.0)Breakdown
ads_insights_dmaads_insights_comscore_marketcomscore_market
ads_insights_demographics_dma_regionads_insights_demographics_comscore_market_regioncomscore_market

The dma breakdown has also been removed from the Custom Insights configuration options.

Who is affected?​

Any user syncing the ads_insights_dma or ads_insights_demographics_dma_region streams, or any Custom Insights stream configured with the dma breakdown.

Custom Insights streams​

If you have any Custom Insights streams that use breakdowns=dma, you must update them to use comscore_market before syncing:

  1. Go to Sources → select your Facebook Marketing source.
  2. In the Custom Insights section, find streams that include dma in their breakdowns.
  3. Replace dma with comscore_market in the breakdown list.
  4. Save and retest the source.
note

After upgrading to v6.0.0, syncs for Custom Insights streams that still reference dma will fail with a configuration error because dma is no longer a valid breakdown option. Update your configuration to use comscore_market instead.

Steps to upgrade built-in streams​

  1. Select Connections in the main navbar.
    1. Select the connection(s) affected by the update.
  2. Select the Schema tab.
    1. Select Refresh source schema.
    2. Select OK.
    note

    Any detected schema changes will be listed for your review. The old DMA streams will be removed and the new Comscore Market streams will be available.

  3. Enable the new ads_insights_comscore_market and/or ads_insights_demographics_comscore_market_region streams to replace the removed DMA streams.
  4. Select Save changes at the bottom of the page.
    1. Ensure the Clear affected streams option is checked.
  5. Select Save connection.
    note

    This will reset the data in your destination and initiate a fresh sync.

For more information on resetting your data in Airbyte, see this page.

Upgrading to 5.0.0​

This version includes three breaking schema changes:

1. Level-based primary keys for Custom Insights​

Custom Insights streams now use level-based primary keys. Previously, all Custom Insights streams used ad_id as part of their primary key regardless of the configured level setting. This caused issues when using level=adset, level=campaign, or level=account because the ad_id field would be null, making deduplication impossible.

With this update, the primary key now correctly reflects the configured level:

LevelPrimary Key Fields
ad (default)date_start, account_id, ad_id, plus any breakdowns
adsetdate_start, account_id, adset_id, plus any breakdowns
campaigndate_start, account_id, campaign_id, plus any breakdowns
accountdate_start, account_id, plus any breakdowns

2. Removed deprecated attribution window columns​

The 7d_view and 28d_view columns have been removed from all Ads Insights streams. Meta deprecated these attribution windows on January 12, 2026, and they have been returning null values since that date. Only 1d_view remains as a supported view-through attribution window. The click-through windows (1d_click, 7d_click, 28d_click) are unaffected.

3. Removed wish_bid field​

The wish_bid field has been removed from Ads Insights streams. This field was already excluded from API requests because it caused data inaccuracies (incorrect spend values) and has been returning null.

Who is affected?​

All users syncing any Ads Insights stream (built-in or custom) are affected by the schema column removals (changes 2 and 3). Users that sync Custom Insights streams with level=adset, level=campaign, or level=account are additionally affected by the primary key change (change 1). Users syncing only default level=ad Custom Insights or only built-in Ads Insights streams only need to refresh their schema for the column removals.

Steps to upgrade​

  1. Select Connections in the main navbar.
    1. Select the connection(s) affected by the update.
  2. Select the Schema tab.
    1. Select Refresh source schema.
    2. Select OK.
    note

    Any detected schema changes will be listed for your review.

  3. Select Save changes at the bottom of the page.
    1. Ensure the Clear affected streams option is checked.
  4. Select Save connection.
    note

    This will reset the data in your destination and initiate a fresh sync.

For more information on resetting your data in Airbyte, see this page.

Upgrading to 4.0.0​

The connector has been updated to use v23.0 of Meta's Marketing API as v21.0 will be deprecated on September 9, 2025.

Three fields from the AdCreatives stream have been deprecated:

  • instagram_actor_id -> instagram_user_id
  • effective_instagram_story_id -> effective_instagram_media_id
  • instagram_story_id -> source_instagram_media_id

See the v22.0 changelog for more information

Steps to refresh the AdCreatives stream schema:​

  1. Select Connections in the main navbar.
    1. Select the connection(s) affected by the update.
  2. Select the Schema tab.
    1. Select Refresh source schema.
    2. Select OK
    3. Select Save changes at the bottom of the page.
    note

    Any detected schema changes will be listed for your review.

Upgrading to 3.1.0​

The AdsInsights Reports now don't have the possibility to fetch the next root level properties (fields):

  • cost_per_conversion_lead
  • conversion_lead_rate

Refresh affected AdsInsights Report:​

  1. Select Connections in the main navbar.
    1. Select the connection(s) affected by the update.
  2. Select the Schema tab.
    1. Select Refresh source schema.
    2. Select OK
    3. Select Save changes at the bottom of the page.
    note

    Any detected schema changes will be listed for your review.

Custom streams​

Custom streams will not be able to rely on cost_per_conversion_lead and conversion_lead_rate as fields anymore. Those streams will need to updated considering the fact that the information is not available in Facebook Marketing.

Upgrading to 3.0.0​

Custom Insights Reports now have updated schema for following breakdowns:

  • body_asset
  • call_to_action_asset
  • description_asset
  • image_asset
  • link_url_asset
  • title_asset
  • video_asset
FieldOld TypeNew TypeExample
body_assetstringobject{"text": "Body Text", "id": "12653412653"}
call_to_action_assetstringobject{"name": "Action Name", "id": "12653412653"}
description_assetstringobject{"text": "Description", "id": "12653412653"}
image_assetstringobject{"hash": "hash_value", "url": "http://url","id": "12653412653" }
link_url_assetstringobject{"website_url": "http://url","id": "12653412653" }
title_assetstringobject{"text": "Text", "id": "12653412653" }
video_assetstringobject{"video_id": "2412334234", "url": "http://url", "thumbnail_url: "http://url", "video_name": "Video Name", "id": "12653412653" }

Refresh affected Custom Insights Report above and clear data if it uses breakdowns​

  1. Select Connections in the main navbar.

    1. Select the connection(s) affected by the update.

  2. Select the Schema tab.

    1. Select Refresh source schema.
    2. Select OK
    3. Select Save changes at the bottom of the page.
    note

    Any detected schema changes will be listed for your review.

  3. Navigate to a connection's Settings tab and click Clear data to clear all streams. This action will clear data for all streams in the connection. To clear data for a single stream navigate to the Status tab, click the three grey dots next to the affected stream, and select Clear data. Do this for all affected streams in the connection.

For more information on clearing your data in Airbyte, see this page.

Upgrading to 2.0.0​

Streams Ads-Insights-* streams now have updated schemas.

danger

Please note that data older than 37 months will become unavailable due to Facebook limitations. It is recommended to create a backup at the destination before proceeding with migration.

Update Custom Insights Reports (this step can be skipped if you did not define any)​

  1. Select Sources in the main navbar.
    1. Select the Facebook Marketing Connector.
  2. Select the Retest saved source.
  3. Remove unsupported fields from the list in Custom Insights section.
  4. Select Test and Save.

Refresh affected schemas and reset data​

  1. Select Connections in the main navbar.
    1. Select the connection(s) affected by the update.
  2. Select the Replication tab.
    1. Select Refresh source schema.
    2. Select OK.
note

Any detected schema changes will be listed for your review.

  1. Select Save changes at the bottom of the page. 1. Ensure the Reset affected streams option is checked.
    note

    Depending on destination type you may not be prompted to reset your data.

  2. Select Save connection.
    note

    This will reset the data in your destination and initiate a fresh sync.

For more information on resetting your data in Airbyte, see this page.

Was this page helpful?