Facebook Marketing
Use this guide to set up and reference the Facebook Marketing source connector.
Prerequisites
- A Facebook Ad Account ID for each ad account you want to sync.
- Access to each ad account. If you aren’t an admin, an admin must grant you access to it. For system user access tokens, assign the ad accounts to that system user.
- To authenticate with an access token (required for Airbyte Open Source, optional for Airbyte Cloud):
- A Meta app created with the Measure ad performance data with Marketing API use case and connected to a business portfolio.
- A system user access token with the
ads_read,ads_management, andbusiness_managementpermissions. See Create a Meta app and access token.
Set up the connector
Set up Facebook Marketing
For Airbyte Cloud:
- Log into your Airbyte Cloud account.
- Click Sources, then click + New source.
- On the Set up the source page, select Facebook Marketing from the Source type dropdown.
- Enter a name for the Facebook Marketing connector.
- For Authentication, choose one of these options:
- Authenticate via Facebook Marketing (Oauth): Click Authenticate your account to authorise your Facebook account. First, confirm you’re logged in to the correct Facebook account. Airbyte authenticates your current account, which must access every ad account you want to sync.
- Service Account Key Authentication: Enter a system user access token. To create one, follow Create a Meta app and access token.
For Airbyte Open Source:
- Go to the Airbyte Open Source dashboard.
- Click Sources, then click + New source.
- On the Set up the source page, select Facebook Marketing from the Source type dropdown.
- Enter a name for the Facebook Marketing connector.
- For Authentication, select Service Account Key Authentication and enter a system user access token. To create one, follow Create a Meta app and access token.
Create a Meta app and token
Create a Meta app and system user access token for Service Account Key Authentication by following these steps. Meta occasionally changes its UI labels. If a label differs, check the linked Meta documentation.
1. Register as a Meta developer
If you don’t already have one, register as a Meta developer. A developer account gives you access to the App Dashboard.
2. Create a Meta app
- Go to the Meta for Developers App Dashboard and click Create App.
- When prompted to add a use case, select Measure ad performance data with Marketing API. This adds the
ads_read,ads_management, andbusiness_managementpermissions and the Marketing API Access Tier feature. Don’t select Create an app without a use case. That option creates an app without permissions or products. - Connect the app to the business portfolio that owns or can access your ad accounts. Meta recommends a verified business portfolio. You need one to access ad accounts owned by other businesses.
- Finish creating the app.
For details, see Meta’s Create an app and Marketing API: Get started guides.
3. Generate a system user token
A system user is a non-human account in your business portfolio. Its token isn’t tied to a personal Facebook login. This makes it Meta’s recommended option for server-to-server integrations such as Airbyte.
- In Meta Business Settings, go to Users > System users. Click Add to create a system user. See Meta’s Add system users to your business portfolio guide.
- Select the system user and click Assign assets. Assign every ad account you want to sync, with at least permission to view performance. Also assign the Meta app you created in Step 2.
- Click Generate new token and select your app.
- Choose an expiration. A 60-day token is more secure. You must generate and update it in Airbyte before it expires. A token that never expires doesn’t need refreshing.
- Select the
ads_read,ads_management, andbusiness_managementpermissions, then generate the token. - Copy the token and store it securely. Enter it as the Access Token when you choose Service Account Key Authentication.
The system user and app must belong to the same business portfolio. See Meta’s Install apps and generate tokens guide for details.
:::tip Check a token’s permissions and expiration with Meta’s Access Token Debugger. :::
4. Get full Marketing API access
New apps begin with Limited access to the Marketing API. Limited access has strict rate limits and supports development only. It’s usually too slow for regular syncs.
- In the App Dashboard, find the Marketing API Access Tier feature added by the use case.
- Click +Upgrade to request Full access.
Your app needs at least 500 Marketing API calls within 15 days to gain and keep full access. Its error rate must stay below 15% across its last 500 calls. Meta checks these requirements continuously and can return an app to limited access.
You only need advanced access to the ads_read or ads_management permissions when syncing ad accounts owned by other businesses. This access requires App Review and business verification. See Meta’s Marketing API: Authorization guide for details.
Fix permission errors
If a connection check or sync returns an ad account permission error, check these details:
- The Account ID is correct. Enter only the number, without the
act_prefix. - The authenticated user has access to the ad account. With OAuth, Airbyte uses the Facebook account active when you clicked Authenticate your account. With an access token, assign the ad account to the system user. Check access in Meta Business Settings under Accounts > Ad accounts.
- The token has the required permissions. Use the Access Token Debugger to confirm the token includes
ads_read,ads_management, andbusiness_management. Also confirm it hasn’t expired. - The ad account belongs to your business portfolio, or is shared with it. If another business owns the ad account, it must share the account with your business portfolio.
Configure source settings
- For Account ID(s), enter one or more comma-separated Facebook Ad Account ID numbers. To find an ID, open Meta Ads Manager and go to your ad account’s Settings. Look under Account overview. Enter only the number, without the
act_prefix.
- (Optional) For Start Date, use the datepicker or enter the date programmatically in
YYYY-MM-DDTHH:mm:ssZformat. Without a start date, the connector replicates all data except Insights data. It only pulls Insights data from the last 37 months.
:::info Insight tables can only pull data from the last 37 months. If your start date is older, those streams won’t sync successfully. :::
- (Optional) For End Date, use the datepicker or enter the date programmatically in
YYYY-MM-DDTHH:mm:ssZformat. The connector replicates Incremental stream data generated between the start date and this end date. Leave this option unset to keep syncing the latest data.
- (Optional) Select multiple Campaign Statuses values to include Campaigns data for specific statuses.
- (Optional) Select multiple AdSet Statuses values to include AdSets data for specific statuses.
- (Optional) Select multiple Ad Statuses values to include Ads data for specific statuses.
:::caution Status filtering and missing records
If you select no Campaign Statuses, AdSet Statuses, or Ad Statuses, the connector uses the Facebook Marketing API default. The API excludes records in ARCHIVED and DELETED states. As a result, archived campaigns, ad sets, and ads won’t appear in your synced data.
Select every status you need to ensure a complete dataset. This matters especially with Full Refresh sync mode. Previously synced records that are now archived won’t be fetched again unless you include ARCHIVED. :::
- (Optional) Toggle the Fetch Thumbnail Images button to fetch the
thumbnail_url. The connector stores the result inthumbnail_data_urlfor each Ad Creative.
- (Optional) Change the default action breakdowns for the Built-in Ads Insights stream. Remove every value to create an empty list, or change the defaults.
- (Optional) In Custom Insights, add a list of ad statistics entries. Give each entry a unique name. Entries can contain fields, breakdowns, or action breakdowns (
action_breakdowns). Fields define the ad data points collected. Breakdowns and action breakdowns segment that data for more detail. Click Add to add an entry. See Custom Insights settings for each entry’s options.
Choose the fields and breakdowns to sync specific Facebook Ads Insights data. You can’t request every field, and many only work with specific field combinations. For example, the app_id breakdown only supports the total_postbacks field. See the Facebook documentation for breakdown limits.
:::info The connector dynamically generates more data streams from your Custom Insights. After changing or removing Custom Insights, refresh the schema for connections that sync those streams. :::
Optionally, configure each custom insight’s Custom Insights settings and the Advanced settings. Then click Set up source and wait for the tests to finish.
Configure Custom Insights
Define the data each custom insight pulls:
- For Name, enter an insight name. Airbyte uses this as the stream name.
- (Optional) For Level, enter the data granularity to pull from the Facebook Marketing API:
account,ad,adset, orcampaign. The default isad. Your selected level determines the deduplication primary key in Incremental Append + Deduped sync mode. See primary key behavior by level for details.
- (Optional) For Fields, select the Facebook Marketing API fields you want to pull from the dropdown.
- (Optional) For Breakdowns, select the breakdowns you want to configure from the dropdown.
:::info High-cardinality breakdowns
Some breakdowns, including product_id, can produce thousands of rows daily. Connection setup still succeeds for these breakdowns. If Facebook’s synchronous validation call returns "Please reduce the amount of data you're asking for", the connector retries using a one-day window. If that call also exceeds the limit, it logs a warning. Real syncs use async jobs and aren’t affected by this limit.
:::
- (Optional) For Action Breakdowns, select the action breakdowns you want to configure from the dropdown.
- Action Report Time has been deprecated and hidden from the UI since v3.5.0. It defaults to
mixedand can’t be changed through the Airbyte UI. When set programmatically through API, Terraform, or PyAirbyte, the available values areimpression,conversion, ormixed. These attribute results to view time, action time, or click-through and view-through times, respectively.
Set each custom insight’s time range and attribution window:
- (Optional) For Time Increment, enter the number of days used to aggregate statistics. The sync runs in intervals of this size. For example, enter 7 for seven-day intervals. The default is 1 day. You can’t use this with Time Increment Period.
-
(Optional) For Time Increment Period, select a calendar-aligned aggregation period instead of a fixed number of days. This creates consistently aligned time buckets, regardless of the start date. It makes comparisons between clients easier. Available options:
daily: equivalent to Time Increment = 1, creating one-day buckets.weekly: aligns with Monday-to-Sunday calendar weeks.monthly: aligns with calendar months, from the first through the last day. The Facebook API supports this natively.
You can’t use this with Time Increment. Switching between Time Increment and Time Increment Period triggers a full re-sync.
- (Optional) For Start Date, enter the date in
YYYY-MM-DDTHH:mm:ssZformat. Airbyte replicates data added on or after this date. Leave this field blank to replicate all data.
- (Optional) For End Date, enter the date in
YYYY-MM-DDTHH:mm:ssZformat. Airbyte replicates data added on or before this date. Leave this field blank to replicate the latest data.
- (Optional) For Custom Insights Lookback Window, set a lookback window in days to capture updated conversion data during syncs. Facebook supports click-through attribution windows of up to 28 days. A conversion can be attributed to an ad during this period. View-through attribution is limited to 1 day. Match any custom attribution window set in your Facebook account. Otherwise, keep the default of 28 days. See the Meta Help Center for details about action attributions.
- (Optional) Toggle Include Incrementality to add the
incrementalityattribution window to this custom insight stream. When enabled, action metrics such asactions,action_values, andcost_per_action_typeinclude anincrementalityfield. This setting only affects this custom insight. See the global Include Incrementality setting in Advanced settings for details.
Advanced settings
Most users don’t need to change these settings.
- (Optional) For Page Size of Requests, set the records per page for paginated responses. Only change this field for specific issues or use cases requiring connector tuning. The default is 100 records per page.
- (Optional) For Insights Window Lookback, set a lookback window in days to capture updated conversion data during syncs. Facebook supports click-through attribution windows of up to 28 days. A conversion can be attributed to an ad during this period. View-through attribution is limited to 1 day. Match any custom attribution window set in your Facebook account. Otherwise, keep the default of 28 days. See the Meta Help Center for details about action attributions.
- (Optional) For Insights Job Timeout, set a custom value from 10 to 60 minutes. This defines the maximum wait for the report job to finish.
- (Optional) Toggle Include Incrementality to add the
incrementalityattribution window to all built-in Ads Insights streams. When enabled, the connector adds"incrementality"to theaction_attribution_windowsparameter sent to the Facebook API. Action metrics such asactions,action_values, andcost_per_action_typethen include anincrementalityfield. This field contains the incremental lift value attributed to the ad. It’s populated only for ad accounts with active Conversion Lift studies configured in Facebook. For accounts without lift studies, the field isnull. This setting is disabled by default. See the Ads Action Stats API reference for details about theincrementalityattribution window.
Supported sync modes
The Facebook Marketing source connector supports these sync modes:
- Full Refresh - Overwrite
- Full Refresh - Append
- Incremental Sync - Append, except for the AdCreatives, AdAccount, CustomConversions, and CustomAudiences streams
- Incremental Sync - Append + Deduped, except for the AdCreatives, AdAccount, CustomConversions, and CustomAudiences streams
Supported streams
| Stream Name | API Docs | Supports Full Refresh | Supports Incremental |
|---|---|---|---|
| activities | Latest | ✅ | ✅ |
| ad_account | Latest | ✅ | ❌ |
| ad_creatives | Latest | ✅ | ❌ |
| ad_creatives_from_ads | Latest | ✅ | ✅ |
| ad_sets | Latest | ✅ | ✅ |
| ads | Latest | ✅ | ✅ |
| ads_insights | Latest | ✅ | ✅ |
| campaigns | Latest | ✅ | ✅ |
| custom_conversions | Latest | ✅ | ❌ |
| custom_audiences | Latest | ✅ | ❌ |
| images | Latest | ✅ | ✅ |
| videos | Latest | ✅ | ✅ |
Notes on Streams:
:::info Custom Audiences
The Facebook Marketing API limits syncing of the rule field in the Custom Audiences stream. As a result, some records may omit this field. Syncing it can also return the error Please reduce the amount of data. See Troubleshooting for details.
:::
:::info Ad Creatives From Ads
The ad_creatives_from_ads stream provides an alternative to ad_creatives. It fetches creative data through the Ads endpoint instead of AdCreatives. Use it when ad_creatives returns “Please reduce the amount of data you’re asking for.” Its output matches ad_creatives and adds an updated_time field containing the parent ad’s timestamp. It only returns creatives linked to ads and excludes orphaned creatives. See Troubleshooting for details.
During incremental syncs, the cursor uses the parent ad’s updated_time because AdCreative has no timestamp. Content changes create a new creative and are always captured. Other changes might not update the parent ad’s timestamp and can be missed. These include in-place renames, status changes, ad-label changes, and edits to the page post behind effective_object_story_id. Use full refresh to capture these changes. The first incremental sync reads the complete ads history to initialise the cursor. The start_date setting doesn’t apply to this stream. Time savings begin with the second sync.
:::
Airbyte also supports these Prebuilt Facebook Ad Insights Reports:
| Stream | Breakdowns | Action Breakdowns |
|---|---|---|
| Ad Insights Action Carousel Card | --- | action_carousel_card_id, action_carousel_card_name |
| Ad Insights Action Conversion Device | device_platform | action_type |
| Ad Insights Action Product ID | product_id | --- |
| Ad Insights Action Reaction | --- | action_reaction |
| Ad Insights Action Video Sound | --- | action_video_sound |
| Ad Insights Action Video Type | --- | action_video_type |
| Ad Insights Action Type | --- | action_type |
| Ad Insights Age And Gender | age, gender | action_type, action_target_id, action_destination |
| Ad Insights Delivery Device | device_platform | action_type |
| Ad Insights Delivery Platform | publisher_platform | action_type |
| Ad Insights Delivery Platform And Device Platform | publisher_platform, device_platform | action_type |
| Ad Insights Demographics Age | age | action_type |
| Ad Insights Demographics Country | country | action_type |
| Ad Insights Demographics Comscore Market Region | comscore_market | action_type |
| Ad Insights Demographics Gender | gender | action_type |
| Ad Insights Comscore Market | comscore_market | action_type, action_target_id, action_destination |
| Ad Insights Country | country | action_type, action_target_id, action_destination |
| Ad Insights Platform And Device | publisher_platform, platform_position, impression_device | action_type |
| Ad Insights Region | region | action_type, action_target_id, action_destination |
:::info Breakdown opt-in requirement (effective August 6, 2026)
From August 6, 2026, Meta requires certain ad accounts to opt in to impression_device, hourly_stats_aggregated_by_audience_time_zone, and frequency_value breakdowns. This affects the Ad Insights Platform And Device stream and Custom Insights streams configured with these breakdowns. The requirement only applies to non-sales-supported accounts. The connector gets insights through asynchronous report jobs, which Meta documents as a supported fallback. If these streams return no data, ask your account administrator to opt in through Ads Manager. See Meta’s 2026 out-of-cycle changes for details.
:::
You can segment the Ad Insights table using the following information. With normalisation enabled, each segment syncs as a separate table:
- Country
- Comscore Market
- Gender & Age
- Platform & Device
- Region
For details, see the Facebook Insights API documentation.
Custom Insights primary keys {#custom-insights-primary-keys}
The configured Level setting determines each Custom Insights stream’s primary key. It controls record deduplication in Incremental Append + Deduped sync mode.
| Level | Primary Key Fields |
|---|---|
ad (default) | date_start, account_id, ad_id, plus any configured breakdowns |
adset | date_start, account_id, adset_id, plus any configured breakdowns |
campaign | date_start, account_id, campaign_id, plus any configured breakdowns |
account | date_start, account_id, plus any configured breakdowns |
Built-in Ads Insights streams and Prebuilt Ads Insights Reports use level=ad by default. They always include ad_id in the primary key.
Entity-relationship diagram
Insights timezone handling
The Facebook Insights API interprets time_range date filters, since and until, in the ad account’s timezone rather than UTC. For timezones ahead of UTC, the connector detects each account’s timezone and adjusts its sync date range. Examples include Asia/Tokyo at UTC+9 and Europe/Berlin at UTC+1. This prevents the connector from missing the current day’s data. The per-account adjustment covers all built-in and custom Ads Insights streams. You don’t need to configure it.
When one connection syncs ad accounts across different timezones, the connector calculates each account’s date range independently.
Attribution reporting
During Incremental syncs, the connector uses lookback_window to reread the previous <lookback_window> days. This captures updated Facebook ads conversion data, but may sync some data more than once. You can change the window through lookback_window during source setup, up to 28 days. Smaller values create fewer duplicates. Larger values provide more accurate results. See Meta article for more about the attribution window’s purpose.
IP allow list
If you use Airbyte Cloud and restrict access by IP, add the Airbyte Cloud IP addresses to your allow list.
Data type map
| Integration Type | Airbyte Type |
|---|---|
| string | string |
| number | number |
| array | array |
| object | object |
Troubleshooting
Reduce requested data
This response means the Facebook Graph API rejected a synchronous request because one response would contain too much data. The required action depends on where the error occurs.
During a sync on a stream other than ad_creatives: request fewer fields for that stream.
- Go to the Schema Tab: Go to your connection’s schema tab.
- Select the Source: Click the source with sync issues.
- Toggle Fields: Clear or toggle off fields you don’t need. The Graph API will no longer receive requests for those fields.
During a sync on the ad_creatives stream: switch to the ad_creatives_from_ads stream. See the next section for details.
During connection setup for a custom insight using a high-cardinality breakdown, such as product_id: you don’t need to act. Since v5.2.7, the connector retries breakdown validation with a one-day range. If that also exceeds the limit, it logs a warning and continues. The breakdown combination remains validated. Real syncs aren’t affected because async jobs handle large result sets.
Fix Ad Creatives data errors
If ad_creatives returns “Please reduce the amount of data you’re asking for, then retry your request”, you have another option. If you don’t want to disable fields, switch to ad_creatives_from_ads. This stream gets the same creative data through the Ads endpoint, one creative at a time. This avoids the data-size limit. Its output schema matches ad_creatives.
ad_creatives_from_ads is slower than ad_creatives because it makes a separate API call for each creative. It only returns creatives linked to ads, so orphaned creatives aren’t included.
Ad creatives without object_story_spec
For some Degrees of Freedom creatives, the Graph API rejects object_story_spec requests with error 100 / 2446211. The error reads “First Dof Value Should Match Object Story Spec Field”. The ad_creatives and ad_creatives_from_ads streams return these creatives without object_story_spec instead of failing. They also log a warning containing the creative ID. ad_creatives reads every creative during each sync, restoring the field when the API returns it. In incremental mode, ad_creatives_from_ads only rereads a creative after its parent ad changes. Therefore, refresh that stream to backfill object_story_spec.
Find missing Campaigns, Ad Sets, or Ads {#missing-records-status-filtering}
If campaigns, ad sets, or ads are missing from synced data, check your status filters first.
By default, the Facebook Marketing API excludes records in ARCHIVED and DELETED states. Empty Campaign Statuses, AdSet Statuses, or Ad Statuses fields don’t override this default. The connector therefore omits archived or deleted records without notice.
This is especially visible after a Full Refresh sync. Records synced while active won’t reappear if they’ve since been archived. To confirm, look up the missing record IDs directly through the Facebook API. Individual ID lookups return records regardless of status. The connector’s listing endpoints don’t.
To restore the missing records:
- Go to Settings > Source > Facebook Marketing.
- For Campaign Statuses, AdSet Statuses, and Ad Statuses, select every status you need. At minimum, add
ARCHIVEDalongside the active statuses. - Run a Full Refresh sync to fetch the complete dataset again.
Missing view-through attribution data
On January 12, 2026, Meta removed support for 7-day and 28-day view-through attribution windows in the Ads Insights API. These windows are 7d_view and 28d_view. Version v4.1.3 removed them from request parameters for ads_insights and Ads Insights Reports streams. Version v5.0.0 also removed the 7d_view and 28d_view columns from stream schemas. Data previously returned for these windows is no longer available. See Meta’s 2025 Out-Of-Cycle Changes for details.
Available data
- The
1d_viewattribution window remains supported and returns data where applicable. - This change doesn’t affect click-through attribution windows:
1d_click,7d_click, and28d_click.
Fix an invalid token after OAuth
Your saved token may be corrupt if a connection check fails soon after OAuth re-authentication. The error may say “Invalid access token” or “Error validating access token”. Chrome’s autofill feature can cause this problem.
Cause
Chrome may interpret two adjacent fields as a login form. These are the Ad Account ID text field and Access Token password field. It can then silently insert saved browser credentials. Saving this autofilled value lets an internal migration overwrite the valid OAuth token. All later syncs and connection checks then fail.
Connector version 6.0.2 fixed this issue (airbytehq/airbyte#81331). Upgrade older versions to 6.0.2 or later to prevent it recurring.
Fix
- Open your Facebook Marketing source configuration in Airbyte.
- Click Authenticate your account or Re-authenticate and complete OAuth again. This creates a fresh, valid access token.
- Click Save, then run Test Connection to confirm the new token works.
If the connection check still fails after re-authentication, contact Airbyte Support for further help.
Missing purchase metrics
Purchases or purchase value fields in Ads Insights may look incomplete or under-reported for certain date ranges. This issue affects several platforms, including direct Facebook API calls. It isn’t specific to Airbyte and relates to intermittent upstream API behaviour.
What happens
API users have reported missing purchase metrics on Reddit and in Facebook Developer and Community forums. Sometimes, action values such as offsite_conversion.fb_pixel_purchase appear at ad or ad set level. They may disappear at campaign or account level. API users documented similar behaviour in the Facebook Developer Community several years ago. It appears to have become more frequent since 2025.
Why it happens
Facebook’s Ads Insights API dynamically aggregates and filters metrics. Purchase data may be missing or inconsistent for these reasons.
-
Attribution window processing: Facebook reattributes purchases up to 28 days after a click or 1 day after an impression. Recent data can therefore change or seem missing before finalisation.
-
Complex breakdowns or field combinations: using multiple breakdowns such as
action_type,action_target_id, andaction_destinationcan produce partial or truncated responses. -
Intermittent API behaviour: Facebook’s data availability and aggregation can vary by endpoint and attribution window, causing temporary inconsistencies.
-
Throughput and rate limits: exceeding API throughput or running many queries concurrently can return partial datasets or suppress some metrics.
Resolve the issue
-
Refresh recent data: set the connector’s Start Date just before the discrepancy begins. Then run a “Refresh and Retain” sync from the connection’s settings tab. Many customers find this restores missing metrics.
-
Simplify breakdowns: temporarily remove Action breakdowns such as
action_type,action_target_id, andaction_destinationfrom Ads Insights. Sync again, then reintroduce them gradually. -
Reduce query size: for custom report streams, first sync fewer fields or a narrower date range. Check the results, then expand incrementally.
-
Limit concurrency: stagger sync schedules for Facebook Marketing connections that share an access token. This can reduce contention and avoid Facebook API limits. It only works across separate connections. You can’t stagger syncs within one connection containing several ad accounts.
-
Check Facebook Ads Manager: compare values at ad or ad set level. Action values often appear there when aggregated results omit them.
Changelog
Expand to review
| Version | Date | Pull Request | Subject |
|---|---|---|---|
| 6.1.12 | 2026-11-04 | 90852 | Build the insights stream schema once per stream instead of for every record, which speeds up insights syncs, most of all custom insights |
| 6.1.11 | 2026-11-04 | 90896 | Raise minimum supported Python version to 3.11 |
| 6.1.10 | 2026-11-04 | 90974 | Update CDK to 7.45 |
| 6.1.9 | 2026-10-21 | 89624 | Keep the custom insights primary key in the configured breakdowns order so it no longer changes between syncs |
| 6.1.8 | 2026-10-20 | 74884 | Retry dropped connections, truncated responses, and read timeouts from the Facebook API, and report them as transient errors if retries are exhausted |
| 6.1.7 | 2026-10-16 | 89019 | Include Meta’s user-facing error title and message, plus the error subcode, in otherwise generic Graph API error messages |
| 6.1.6 | 2026-10-16 | 89047 | Fix in-app setup guide rendering in Airbyte Cloud, update access token setup steps to match Meta’s current docs, and correct field descriptions |
| 6.1.5 | 2026-10-16 | 89006 | Upgrade to Python 3.13 and python-connector-base 4.1.1 |
| 6.1.4 | 2026-10-16 | 89020 | Fix ad_creatives and ad_creatives_from_ads failing on Facebook error 2446211 by emitting affected creatives with a null object_story_spec |
| 6.1.3 | 2026-09-30 | 87588 | Fix insights streams cursor moving backwards after interrupted sync attempts (causing progressively wider re-reads), clean up stale completed slices in state, and fix cursor advancement for monthly/weekly time increments |
| 6.1.2 | 2026-09-21 | 86315 | Fix ad-account quota errors (code 17/2446079) being retried as transient failures: read rate-limit headers on failed calls and wait out the block (API-provided reset estimate when present, 10-minute re-checks otherwise, up to 1 hour); read every business-use-case entry and the ad-account reset time from the rate-limit headers; the connection check fails fast instead of waiting |
| 6.1.1 | 2026-08-24 | 74266 | feat(source-facebook-marketing): add opt-in engaged view (ev) attribution window (AI-Triage PR) |
| 6.1.0 | 2026-08-04 | 83704 | Add incremental sync support to the ad_creatives_from_ads stream |
| 6.0.2 | 2026-06-30 | 81331 | Hide legacy top-level access_token field from UI to prevent Chrome autofill from corrupting OAuth tokens |
| 6.0.1 | 2026-06-24 | 80779 | Fix TypeError in CursorPatch.load_next_page() when Facebook API returns malformed (non-dict) responses or data items |
| 6.0.0 | 2026-06-23 | 80324 | Replace deprecated ads_insights_dma and ads_insights_demographics_dma_region streams with ads_insights_comscore_market and ads_insights_demographics_comscore_market_region following Meta’s DMA → Comscore Market transition. Remove dma from Custom Insights breakdowns. |
| 5.2.14 | 2026-06-11 | 79643 | Replace the cryptic system_error on un-generatable Ads Insights reports with a clear, actionable config_error that names the offending stream/field/breakdown and how to resolve it (unselect the field, or disable the incrementality attribution window) (oncall #12088). |
| 5.2.13 | 2026-06-03 | 78060 | Fixed sync failures on Ads Insights breakdown streams caused by invalid field requests; cap async-job status-poll batches at Meta’s 50-per-batch limit when a parent job has many children; tolerate malformed responses on the throttle-refresh ping instead of failing the whole sync. |
| 5.2.12 | 2026-05-27 | 78451 | Promoted release candidate to GA |
| 5.2.12-rc.1 | 2026-05-20 | 75457 | Bump facebook-business SDK from v23 to v25 to support Marketing API v25.0 before v23.0 sunset on June 9, 2026 |
| 5.2.11 | 2026-04-28 | 76977 | Bump airbyte-cdk to ^7.17.4; facebook-business updated to 23.0.3 via lockfile refresh |
| 5.2.10 | 2026-04-27 | 76064 | Fix ad_account stream crash by catching AirbyteTracedException wrapping FacebookRequestError in list_objects |
| 5.2.9 | 2026-04-24 | 76995 | Fix TypeError crash when Facebook API returns error response with no message body |
| 5.2.8 | 2026-04-24 | 76996 | Cast API throttle and rate-limit header values to float to prevent TypeError when Facebook returns string-typed numbers |
| 5.2.7 | 2026-04-23 | 76951 | Promoted release candidate to GA |
| 5.2.7-rc.1 | 2026-04-16 | 74127 | Allow connection setup to succeed for custom insights with high-cardinality breakdowns (for example, product_id) |
| 5.2.6 | 2026-04-13 | 76101 | Replace ValueError with AirbyteTracedException for proper error classification in async job splitting |
| 5.2.5 | 2026-04-08 | 76134 | Fix undefined APILimit name in async_job.py type annotations |
| 5.2.4 | 2026-04-02 | 75981 | Fix ad_creatives_from_ads stream crash by catching AirbyteTracedException in creative detail fetching |
| 5.2.3 | 2026-04-02 | 75372 | Fix _collect_child_ids: clamp since <= until after retention validation, add retry logic for transient Job Failed status, and apply fields_exceptions filtering to exclude problematic fields from API requests |
| 5.2.2 | 2026-03-17 | 75130 | Extend upgrade deadline for version 5.0.0 breaking changes to 2026-04-10 |
| 5.2.1 | 2026-03-09 | 74147 | Add calendar-aligned time periods (daily/weekly/monthly) to InsightConfig |
| 5.2.0 | 2026-03-09 | 72835 | Add ad_creatives_from_ads stream as alternative to ad_creatives |
| 5.1.1 | 2026-03-03 | 74255 | update upgradeDeadline for the v5.0.0 |
| 5.1.0 | 2026-03-02 | 74134 | Add opt-in include_incrementality config option to append incrementality to action attribution windows |
| 5.0.1 | 2026-02-24 | 73281 | fix(source-facebook-marketing): Fix Facebook Marketing UTC hardcoding with per-account timezone detection |
| 5.0.0 | 2026-02-20 | 72779 | Custom Insights streams now use level-based primary keys; removed deprecated 7d_view and 28d_view attribution window columns; removed wish_bid field. All users should refresh schema and reset affected streams. |
| 4.2.1 | 2026-02-09 | 72952 | fix(source-facebook-marketing): classify ‘Invalid OAuth access token’ as config_error (AI-Triage PR) |
| 4.2.0 | 2026-01-07 | 71029 | Add 98 missing fields for custom insights streams including objective_results transformation |
| 4.1.3 | 2026-01-06 | 70349 | Remove deprecated 7d_view and 28d_view attribution windows (Facebook API deprecation effective January 12, 2026) |
| 4.1.2 | 2025-11-10 | 69204 | Add config migration that adds default action breakdowns |
| 4.1.1 | 2025-11-04 | 69169 | Finalize progressive rollout. |
| 4.1.1-rc.1 | 2025-10-27 | 68632 | Performance improvement on normalization |
| 4.1.0 | 2025-10-06 | 67081 | Promoting release candidate 4.1.0-rc.2 to a main version. |
| 4.1.0-rc.2 | 2025-10-02 | 66976 | Add missing breakdown user_segment_key |
| 4.1.0-rc.1 | 2025-09-25 | 66000 | Add field-based splitting for failed Ad-level async jobs; Upgrade to CDK v7 |
| 4.0.1 | 2025-09-15 | 66182 | Classify subcode 2446289 error as config error |
| 4.0.0 | 2025-08-27 | 65533 | Migrate to Marketing API v23 |
| 3.5.12 | 2025-08-23 | 65288 | Update dependencies |
| 3.5.11 | 2025-08-19 | 64911 | Allow overriding action breakdowns for default Ads Insights stream. |
| 3.5.10 | 2025-08-16 | 65010 | Update dependencies |
| 3.5.9 | 2025-08-09 | 64679 | Update dependencies |
| 3.5.8 | 2025-08-02 | 64406 | Update dependencies |
| 3.5.7 | 2025-07-26 | 63934 | Update dependencies |
| 3.5.6 | 2025-07-19 | 63604 | Update dependencies |
| 3.5.5 | 2025-07-12 | 63029 | Update dependencies |
| 3.5.4 | 2025-07-05 | 62811 | Update dependencies |
| 3.5.3 | 2025-06-28 | 62413 | Update dependencies |
| 3.5.2 | 2025-06-21 | 61958 | Update dependencies |
| 3.5.1 | 2025-06-14 | 61290 | Update dependencies |
| 3.5.0 | 2025-06-09 | 61477 | Removed action_report_time from spec as deprecated |
| 3.4.9 | 2025-05-24 | 60025 | Update dependencies |
| 3.4.8 | 2025-05-03 | 58889 | Update dependencies |
| 3.4.7 | 2025-04-19 | 58296 | Update dependencies |
| 3.4.6 | 2025-04-12 | 57827 | Update dependencies |
| 3.4.5 | 2025-04-05 | 57219 | Update dependencies |
| 3.4.4 | 2025-03-29 | 56467 | Update dependencies |
| 3.4.3 | 2025-02-20 | 54171 | Fix retry pattern |
| 3.4.2 | 2025-03-22 | 55991 | Update dependencies |
| 3.4.1 | 2025-03-21 | 55760 | Fixed KeyError during discovery due to outdated breakdown schema |
| 3.4.0 | 2024-12-24 | 50418 | Add learning_stage_info field to ad_sets stream |
| 3.3.35 | 2025-03-08 | 55307 | Update dependencies |
| 3.3.34 | 2025-03-01 | 54990 | Update dependencies |
| 3.3.33 | 2025-02-22 | 54386 | Update dependencies |
| 3.3.32 | 2025-02-15 | 53721 | Update dependencies |
| 3.3.31 | 2025-02-11 | 53626 | Log Utilization type |
| 3.3.30 | 2025-02-08 | 53330 | Update dependencies |
| 3.3.29 | 2025-02-01 | 52835 | Update dependencies |
| 3.3.28 | 2025-01-27 | 52032 | Update to API version 21 |
| 3.3.27 | 2025-01-25 | 52365 | Update dependencies |
| 3.3.26 | 2025-01-18 | 51706 | Update dependencies |
| 3.3.25 | 2025-01-11 | 51080 | Update dependencies |
| 3.3.24 | 2025-01-04 | 50922 | Update dependencies |
| 3.3.23 | 2024-12-28 | 50533 | Update dependencies |
| 3.3.22 | 2024-12-21 | 50014 | Update dependencies |
| 3.3.21 | 2024-12-14 | 49197 | Update dependencies |
| 3.3.20 | 2024-11-25 | 48632 | Starting with this version, the Docker image is now rootless. Please note that this and future versions will not be compatible with Airbyte versions earlier than 0.64 |
| 3.3.19 | 2024-11-04 | 48155 | Update dependencies |
| 3.3.18 | 2024-10-29 | 47894 | Update dependencies |
| 3.3.17 | 2024-10-28 | 43787 | Update dependencies |
| 3.3.16 | 2024-07-15 | 46546 | Raise exception on missing stream |
| 3.3.15 | 2024-07-15 | 42562 | Add friendly messages for “reduce fields” and “start date” errors |
| 3.3.14 | 2024-07-15 | 41958 | Update cdk to filter invalid fields from configured catalog |
| 3.3.13 | 2024-07-13 | 41732 | Update dependencies |
| 3.3.12 | 2024-07-11 | 41644 | Remove discriminator with missing schemas |
| 3.3.11 | 2024-07-10 | 41039 | Pick request fields from configured json schema properties if present |
| 3.3.10 | 2024-07-10 | 41458 | Update dependencies |
| 3.3.9 | 2024-07-09 | 41106 | Update dependencies |
| 3.3.8 | 2024-07-06 | 40934 | Update dependencies |
| 3.3.7 | 2024-07-01 | 40645 | Use latest CDK version possible |
| 3.3.6 | 2024-06-24 | 40241 | Update AdsInsights fields - removed adset_start |
| 3.3.5 | 2024-06-26 | 40545 | Fixed issue when the STATE is literal None (RFR) |
| 3.3.4 | 2024-06-25 | 40485 | Update dependencies |
| 3.3.3 | 2024-06-22 | 40191 | Update dependencies |
| 3.3.2 | 2024-06-06 | 39174 | [autopull] Upgrade base image to v1.2.2 |
| 3.3.1 | 2024-06-15 | 39511 | Fix validation of the spec custom_insights.time_increment field |
| 3.3.0 | 2024-06-30 | 33648 | Add support to field source_instagram_media_id to ad_creatives report |
| 3.2.1 | 2024-06-13 | 39439 | Apply configured statuses to ads insight streams |
| 3.2.0 | 2024-06-05 | 37625 | Source Facebook-Marketing: Add Selectable Auth |
| 3.1.0 | 2024-06-01 | 38845 | Update AdsInsights fields - removed cost_per_conversion_lead and conversion_lead_rate |
| 3.0.0 | 2024-04-30 | 36608 | Update body_asset, call_to_action_asset, description_asset, image_asset, link_url_asset, title_asset, video_asset breakdowns schema. |
| 2.1.9 | 2024-05-17 | 38301 | Fix data inaccuracies when wish_bid is requested |
| 2.1.8 | 2024-05-07 | 37771 | Handle errors without API error codes/messages |
| 2.1.7 | 2024-04-24 | 36634 | Update to CDK 0.80.0 |
| 2.1.6 | 2024-04-24 | 36634 | Schema descriptions |
| 2.1.5 | 2024-04-17 | 37341 | Move rate limit errors to transient errors. |
| 2.1.4 | 2024-04-16 | 37367 | Skip config migration when the legacy account_id field does not exist |
| 2.1.3 | 2024-04-16 | 37320 | Add retry for transient error |
| 2.1.2 | 2024-03-29 | 36689 | Fix key error account_id for custom reports. |
| 2.1.1 | 2024-03-18 | 36025 | Fix start_date selection behaviour |
| 2.1.0 | 2024-03-12 | 35978 | Upgrade CDK to start emitting record counts with state and full refresh state |
| 2.0.1 | 2024-03-08 | 35913 | Fix lookback window |
| 2.0.0 | 2024-03-01 | 35746 | Update API to v19.0 |
| 1.4.2 | 2024-02-22 | 35539 | Add missing config migration from include_deleted field |
| 1.4.1 | 2024-02-21 | 35467 | Fix error with incorrect state transforming in the 1.4.0 version |
| 1.4.0 | 2024-02-20 | 32449 | Replace “Include Deleted Campaigns, Ads, and AdSets” option in configuration with specific statuses selection per stream |
| 1.3.3 | 2024-02-15 | 35061 | Add integration tests |
| 1.3.2 | 2024-02-12 | 35178 | Manage dependencies with Poetry |
| 1.3.1 | 2024-02-05 | 34845 | Add missing fields to schemas |
| 1.3.0 | 2024-01-09 | 33538 | Updated the Ad Account ID(s) property to support multiple IDs |
| 1.2.3 | 2024-01-04 | 33828 | Make ready for airbyte-lib |
| 1.2.2 | 2024-01-02 | 33828 | Add insights job timeout to be an option, so a user can specify their own value |
| 1.2.1 | 2023-11-22 | 32731 | Removed validation that blocked personal ad accounts during check |
| 1.2.0 | 2023-10-31 | 31999 | Extend the AdCreatives stream schema |
| 1.1.17 | 2023-10-19 | 31599 | Base image migration: remove Dockerfile and use the python-connector-base image |
| 1.1.16 | 2023-10-11 | 31284 | Fix error occurring when trying to access the funding_source_details field of the AdAccount stream |
| 1.1.15 | 2023-10-06 | 31132 | Fix permission error for AdAccount stream |
| 1.1.14 | 2023-09-26 | 30758 | Exception should not be raises if a stream is not found |
| 1.1.13 | 2023-09-22 | 30706 | Performance testing - include socat binary in docker image |
| 1.1.12 | 2023-09-22 | 30655 | Updated doc; improved schema for custom insight streams; updated SAT or custom insight streams; removed obsolete optional max_batch_size option from spec |
| 1.1.11 | 2023-09-21 | 30650 | Fix None issue since start_date is optional |
| 1.1.10 | 2023-09-15 | 30485 | added ‘status’ and ‘configured_status’ fields for campaigns stream schema |
| 1.1.9 | 2023-08-31 | 29994 | Removed batch processing, updated description in specs, added user-friendly error message, removed start_date from required attributes |
| 1.1.8 | 2023-09-04 | 29666 | Adding custom field boosted_object_id to a streams schema in campaigns catalog CustomAudiences |
| 1.1.7 | 2023-08-21 | 29674 | Exclude rule from stream CustomAudiences |
| 1.1.6 | 2023-08-18 | 29642 | Stop batch requests if only 1 left in a batch |
| 1.1.5 | 2023-08-18 | 29610 | Automatically reduce batch size |
| 1.1.4 | 2023-08-08 | 29412 | Add new custom_audience stream |
| 1.1.3 | 2023-08-08 | 29208 | Add account type validation during check |
| 1.1.2 | 2023-08-03 | 29042 | Fix broken advancedAuth references for spec |
| 1.1.1 | 2023-07-26 | 27996 | Remove reference to authSpecification |
| 1.1.0 | 2023-07-11 | 26345 | Add new action_report_time attribute to AdInsights class |
| 1.0.1 | 2023-07-07 | 27979 | Added the ability to restore the reduced request record limit after the successful retry, and handle the unknown error (code 99) with the retry strategy |
| 1.0.0 | 2023-07-05 | 27563 | Migrate to FB SDK version 17 |
| 0.5.0 | 2023-06-26 | 27728 | License Update: Elv2 |
| 0.4.3 | 2023-05-12 | 27483 | Reduce replication start date by one more day |
| 0.4.2 | 2023-06-09 | 27201 | Add complete_oauth_server_output_specification to spec |
| 0.4.1 | 2023-06-02 | 26941 | Remove authSpecification from spec.json, use advanced_auth instead |
| 0.4.0 | 2023-05-29 | 26720 | Add Prebuilt Ad Insights reports |
| 0.3.7 | 2023-05-12 | 26000 | Handle config errors |
| 0.3.6 | 2023-04-27 | 22999 | Specified date formatting in specification |
| 0.3.5 | 2023-04-26 | 24994 | Emit stream status messages |
| 0.3.4 | 2023-04-18 | 22990 | Increase pause interval |
| 0.3.3 | 2023-04-14 | 25204 | Fix data retention period validation |
| 0.3.2 | 2023-04-08 | 25003 | Don’t fetch thumbnail_data_url if it’s None |
| 0.3.1 | 2023-03-27 | 24600 | Reduce request record limit when retrying second page or further |
| 0.3.0 | 2023-03-16 | 19141 | Added Level parameter to custom Ads Insights |
| 0.2.86 | 2023-03-01 | 23625 | Add user friendly fields description in spec and docs. Extend error message for invalid Account ID case. |
| 0.2.85 | 2023-02-14 | 23003 | Bump facebook_business to 16.0.0 |
| 0.2.84 | 2023-01-27 | 22003 | Set AvailabilityStrategy for streams explicitly to None |
| 0.2.83 | 2023-01-13 | 21149 | Videos stream remove filtering |
| 0.2.82 | 2023-01-09 | 21149 | Fix AdAccount schema |
| 0.2.81 | 2023-01-05 | 21057 | Remove unsupported fields from request |
| 0.2.80 | 2022-12-21 | 20736 | Fix update next cursor |
| 0.2.79 | 2022-12-07 | 20402 | Exclude Not supported fields from request |
| 0.2.78 | 2022-12-07 | 20165 | Fix fields permission error |
| 0.2.77 | 2022-12-06 | 20131 | Update next cursor value at read start |
| 0.2.76 | 2022-12-03 | 20043 | Allows action_breakdowns to be an empty list - bugfix for #20016 |
| 0.2.75 | 2022-12-03 | 20016 | Allows action_breakdowns to be an empty list |
| 0.2.74 | 2022-11-25 | 19803 | New default for action_breakdowns, improve “check” command speed |
| 0.2.73 | 2022-11-21 | 19645 | Check “breakdowns” combinations |
| 0.2.72 | 2022-11-04 | 18971 | Handle FacebookBadObjectError for empty results on async jobs |
| 0.2.71 | 2022-10-31 | 18734 | Reduce request record limit on retry |
| 0.2.70 | 2022-10-26 | 18045 | Upgrade FB SDK to v15.0 |
| 0.2.69 | 2022-10-17 | 18045 | Remove “pixel” field from the Custom Conversions stream schema |
| 0.2.68 | 2022-10-12 | 17869 | Remove “format” from optional datetime end_date field |
| 0.2.67 | 2022-10-04 | 17551 | Add cursor_field for custom_insights stream schema |
| 0.2.66 | 2022-09-29 | 17371 | Fix stream CustomConversions enable_deleted=False |
| 0.2.65 | 2022-09-22 | 17304 | Migrate to per-stream state. |
| 0.2.64 | 2022-09-22 | 17027 | Limit time range with 37 months when creating an insight job from lower edge object. Retry bulk request when getting error code 960 |
| 0.2.63 | 2022-09-06 | 15724 | Add the Custom Conversion stream |
| 0.2.62 | 2022-09-01 | 16222 | Remove end_date from config if empty value (re-implement #16096) |
| 0.2.61 | 2022-08-29 | 16096 | Remove end_date from config if empty value |
| 0.2.60 | 2022-08-19 | 15788 | Retry FacebookBadObjectError |
| 0.2.59 | 2022-08-04 | 15327 | Shift date validation from config validation to stream method |
| 0.2.58 | 2022-07-25 | 15012 | Add DATA_RETENTION_PERIODvalidation and fix failed_delivery_checks field schema type issue |
| 0.2.57 | 2022-07-25 | 14831 | Update Facebook SDK to version 14.0.0 |
| 0.2.56 | 2022-07-19 | 14831 | Add future start_date and end_date validation |
| 0.2.55 | 2022-07-18 | 14786 | Check if the authorized user has the “MANAGE” task permission when getting the funding_source_details field in the ad_account stream |
| 0.2.54 | 2022-06-29 | 14267 | Make MAX_BATCH_SIZE available in config |
| 0.2.53 | 2022-06-16 | 13623 | Add fields bid_amount bid_strategy bid_constraints to ads_set stream |
| 0.2.52 | 2022-06-14 | 13749 | Fix the not syncing any data issue |
| 0.2.51 | 2022-05-30 | 13317 | Change tax_id to string (Canadian has letter in tax_id) |
| 0.2.50 | 2022-04-27 | 12402 | Add lookback window to insights streams |
| 0.2.49 | 2022-05-20 | 13047 | Fix duplicating records during insights lookback period |
| 0.2.48 | 2022-05-19 | 13008 | Update CDK to v0.1.58 avoid crashing on incorrect stream schemas |
| 0.2.47 | 2022-05-06 | 12685 | Update CDK to v0.1.56 to emit an AirbyeTraceMessage on uncaught exceptions |
| 0.2.46 | 2022-04-22 | 12171 | Allow configuration of page_size for requests |
| 0.2.45 | 2022-05-03 | 12390 | Better retry logic for split-up async jobs |
| 0.2.44 | 2022-04-14 | 11751 | Update API to a directly initialise an AdAccount with the given ID |
| 0.2.43 | 2022-04-13 | 11801 | Fix user_tos_accepted schema to be an object |
| 0.2.42 | 2022-04-06 | 11761 | Upgrade Facebook Python SDK to version 13 |
| 0.2.41 | 2022-03-28 | 11446 | Increase number of attempts for individual jobs |
| 0.2.40 | 2022-02-28 | 10698 | Improve sleeps time in rate limit handler |
| 0.2.39 | 2022-03-09 | 10917 | Retry connections when FB API returns error code 2 (temporary oauth error) |
| 0.2.38 | 2022-03-08 | 10531 | Add time_increment parameter to custom insights |
| 0.2.37 | 2022-02-28 | 10655 | Add Activities stream |
| 0.2.36 | 2022-02-24 | 10588 | Fix execute_in_batch for large amount of requests |
| 0.2.35 | 2022-02-18 | 10348 | Add error code 104 to backoff triggers |
| 0.2.34 | 2022-02-17 | 9805 | Performance and reliability fixes |
| 0.2.33 | 2021-12-28 | 10180 | Add AdAccount and Images streams |
| 0.2.32 | 2022-01-07 | 10138 | Add primary_key for all insights streams. |
| 0.2.31 | 2021-12-29 | 9138 | Fix videos stream format field incorrect type |
| 0.2.30 | 2021-12-20 | 8962 | Add asset_feed_spec field to ad creatives stream |
| 0.2.29 | 2021-12-17 | 8649 | Retrieve ad_creatives image as data encoded |
| 0.2.28 | 2021-12-13 | 8742 | Fix for schema generation related to “breakdown” fields |
| 0.2.27 | 2021-11-29 | 8257 | Add fields to Campaign stream |
| 0.2.26 | 2021-11-19 | 7855 | Add Video stream |
| 0.2.25 | 2021-11-12 | 7904 | Implement retry logic for async jobs |
| 0.2.24 | 2021-11-09 | 7744 | Fix fail when async job takes too long |
| 0.2.23 | 2021-11-08 | 7734 | Resolve $ref field for discover schema |
| 0.2.22 | 2021-11-05 | 7605 | Add job retry logics to AdsInsights stream |
| 0.2.21 | 2021-10-05 | 4864 | Update insights streams with custom entries for fields, breakdowns and action_breakdowns |
| 0.2.20 | 2021-10-04 | 6719 | Update version of facebook_business package to 12.0 |
| 0.2.19 | 2021-09-30 | 6438 | Annotate Oauth2 flow initialization parameters in connector specification |
| 0.2.18 | 2021-09-28 | 6499 | Fix field values converting fail |
| 0.2.17 | 2021-09-14 | 4978 | Convert values’ types according to schema types |
| 0.2.16 | 2021-09-14 | 6060 | Fix schema for ads_insights stream |
| 0.2.15 | 2021-09-14 | 5958 | Fix url parsing and add report that exposes conversions |
| 0.2.14 | 2021-07-19 | 4820 | Improve the rate limit management |
| 0.2.12 | 2021-06-20 | 3743 | Refactor connector to use CDK: - Improve error handling. - Improve async job performance (insights). - Add new configuration parameter insights_days_per_job. - Rename stream adsets to ad_sets. - Refactor schema logic for insights, allowing to configure any possible insight stream. |
| 0.2.10 | 2021-06-16 | 3973 | Update version of facebook_business to 11.0 |
| 0.2.9 | 2021-06-10 | 3996 | Add AIRBYTE_ENTRYPOINT for Kubernetes support |
| 0.2.8 | 2021-06-09 | 3973 | Add 80000 as a rate-limiting error code |
| 0.2.7 | 2021-06-03 | 3646 | Add missing fields to AdInsights streams |
| 0.2.6 | 2021-05-25 | 3525 | Fix handling call rate limit |
| 0.2.5 | 2021-05-20 | 3396 | Allow configuring insights lookback window |
| 0.2.4 | 2021-05-13 | 3395 | Fix an issue that caused losing Insights data from the past 28 days while incremental sync |
| 0.2.3 | 2021-04-28 | 3116 | Wait longer (5 min) for async jobs to start |
| 0.2.2 | 2021-04-03 | 2726 | Fix base connector versioning |
| 0.2.1 | 2021-03-12 | 2391 | Support FB Marketing API v10 |
| 0.2.0 | 2021-03-09 | 2238 | Protocol allows future/unknown properties |
| 0.1.4 | 2021-02-24 | 1902 | Add include_deleted option in params |
| 0.1.3 | 2021-02-15 | 1990 | Support Insights stream via async queries |
| 0.1.2 | 2021-01-22 | 1699 | Add incremental support |
| 0.1.1 | 2021-01-15 | 1552 | Release Native Facebook Marketing Connector |