Product and documentation updates about the Facebook Ads integration from the team at Stitch.

Stay up-to-date by subscribing to our RSS feed.


Facebook Ads (v1) bug fix: Summary param error

We’ve updated our (v) integration to fix the following error:

Status:  400
Response:
  {
    "error": {
      "message": "(#100) Cannot include cost_per_inline_post_engagement, unique_inline_link_click_ctr, frequency, video_play_curve_actions, unique_ctr, ctr, spend, unique_clicks, unique_inline_link_clicks, video_p100_watched_actions, campaign_name in summary param because they weren't there while creating the report run. All available values are: ",
      "type": "OAuthException",
      "code": 100,
      "fbtrace_id": "*************"
    }
  }

While awaiting for Facebook’s fix, a workaround is now available. A new retry logic has been implemented, you can now retry the request for a successful data retrieval.


Facebook Ads (v1) update: SDK version upgrade

We’ve upgraded our (v) integration’s Facebook SDK version to 19.0.0.


Facebook Ads (v1) update: Add retry logic for status code 503

We’ve improved our (v) integration by adding a retry logic system when an error with the HTTP status code 503 (Service Unavailable) occurs.


Facebook Ads (v1): Add conversions to insights streams

We’ve updated our (v) integration to add the conversions and conversion_values fields to insights streams.


Facebook Ads (v1) update: Updated API version

We’ve bumped our (v) API version up to 14.


Facebook Ads (v1) update: Updated API version

We’ve bumped our (v) API version up to 13.


Facebook Ads (v1) update: Retry for job polling

We’ve improved our (v) integration to resolve race-condition errors. The integration will now retry when an error is encountered with AdsInsights job polling.


Facebook Ads (v1) update: Fixed composite primary key for the `ads_insights_country` table

We’ve fixed the ads_insights_country composite primary key. The country field had previously been erroneously excluded.

The composite primary key is now: campaign_id : adset_id : ad_id : date_start : country

This is a breaking change and communiation from Stitch support has been emailed to affected users.

If you are not already including the country field in downstream processes that identify uniqueness of records in the files loaded for this table, this field will need to be added into those processes.

You may also wish to reset this table to have historical data re-replicated and more accurately portrayed, in which case you should:

  1. Contact our support team to implement a courtesy row-usage exemption for your integration.
  2. Within Stitch, navigate to the ads_insights_country table’s Table Settings page.
  3. Use the Reset Table button to queue this table’s reset.

If you have any questions about the change or this process, please reach out to Stitch support via in-app chat.


Facebook Ads (v1) API upgrade to v10.0

The integration now replicates data using version 10.0 of the Facebook Marketing API. For more details, view the Facebook API changelog.


Facebook Ads (v1) update: Increased replication job timeout

We’ve increased the timeout from 120 seconds to 300 seconds for Ads Insights replication jobs.


New feature: Integration changelogs

Introducing: Integration changelogs!

Check out the history of our integrations and stay in the loop on updates with dedicated changelogs for these integrations:

We’ll add changelogs for other popular integrations and destinations in the weeks to come. If there’s a specific integration you’d like to see us work on, let us know by creating an issue in the Stitch Docs GitHub repo.


Facebook Ads (v1) update: New ads_insights.unique_outbound_clicks data

We’ve added the unique_outbound_clicks field to each of the ads_insights_* tables in the (v) integration.


Facebook Ads (v1) API upgrade to v8.0

The integration now replicates data using version 8.0 of the Facebook Marketing API. For more details, view the Facebook API changelog.


Facebook Ads (v1) API upgrade to v6.0

The integration now replicates data using version 6.0 of the Facebook Marketing API. For more details, view the Facebook API changelog.


Facebook Ads (v1) integrations: New ads_insights.video_play_curve_actions data

We’ve added the video_play_curve_actions field to each of the ads_insights_* tables in the (v) integration.


Facebook Ads (v1) integrations: Use Batch API for adcreative table

We’ve updated the adcreative table in the (v) integration to use Facebook’s Batch API. This change was made to prevent errors resulting from requesting too much data.


Facebook Ads (v1) API upgrade to v4.0

The integration now replicates data using version 4.0 of the Facebook Marketing API. For more details, view the Facebook API changelog.


Facebook Ads (v1) integrations: New ads_insights data

We’ve added a new table to our (v) integration: ads_insights_dma

This table contains entries for each campaign/set/ad combination for each day, along with detailed statistics, segmented by DMA (Designated Market Area).

Learn more in our documentation.


Facebook Ads (v1) API upgrade to v3.3

The integration now replicates data using version 3.3 of the Facebook Marketing API.


Facebook Ads (v1) integrations: Workaround relevance_score deprecation

Due to Facebook prematurely deprecating relevance_score in their API, we’ve added logging to notify you should this field cause an error during replication:

Due to a bug with Facebook prematurely deprecating 'relevance_score' that is not affecting all tap-facebook users in the same way, you need to deselect `relevance_score` from your Insights export. For further information, please see this Facebook bug report thread: https://developers.facebook.com/support/bugs/2489592517771422

Should you encounter this error in Stitch, de-select the relevance_score field from any ads_insights_* tables you have set to replicate.


Facebook Ads (v1) integrations: API upgrade to v3.2

We have updated the integration to use the latest version of the Facebook Marketing API - version 3.2.

As part of this update, Facebook has deprecated many values for cost_per_action_type to simplify reporting and support reporting based on their new eight standard events. Additionally, the total_action_value field has been deprecated and removed from all ads_insights tables.


Facebook Ads (v1) integrations: Field deprecation

Facebook has deprecated the following fields, meaning they are no longer available for selection or retrieval via Facebook’s API:

  • call_to_action_clicks
  • cost_per_total_action
  • social_reach
  • social_impressions
  • social_clicks
  • unique_social_clicks
  • today_spend
  • total_actions
  • total_unique_actions

In addition, several types of metrics have been deprecated. Note: The fields are still available, but the types listed below are not:

  • actions field: mention, tab_view
  • action_values field: app_custom_event
  • cost_per_action_type field: mention, tab_view
  • canvas_avg_view_percentage_per_component field: canvas_view

Facebook Ads (v1) integrations: API upgrade to v2.11

We’ve updated our integration to use the newest version of the Facebook Marketing API - version 2.11.

In addition, we’ve made the following improvements:

  • Configurable attribution window when creating or editing a integration. Choose between 1, 7 or 28 days so that Stitch replicates historical data in alignment with the attribution window of your account.

  • A new table named ads_insights_region. View your data by the region (such as state or province) where people live or were located when they saw your ads, depending on how you set your location targeting.

  • Removed the video_15_sec_watched_actions attribute from relevant tables. Facebook deprecated this attribute in the 2.11 version of their API.


Facebook Ads (v1) integrations: Include deleted ads, adsets, and campaigns

We’ve added a new setting for (v) integrations that enables you to replicate records for deleted ads, adsets, and campaigns:

When checked, Stitch will query for and extract data for deleted ads, adsets, and campaigns from your account. Relevant records will be included in the ads, adcreatives, adsets, and campaigns tables, if selected for replication.

Learn more in our integration documentation.


Facebook Ads (v1) integrations: use_page_actor_override field deprecation

Due to issues with querying and a bug in Facebook’s API, we’re removing support for the adcreative.use_page_actor_override column. As a result, this column will no longer display in Stitch as available for replication.


Facebook Ads (v15-10-2015) integration: API upgrade to v2.9

We’ve updated the integration to use a new version of the Facebook API. This update also provides access to a new table (facebook_ads_insights_platform_and_device), which contains fields allowing you to compare insights between platforms such as Facebok, Instagram, and Messenger, and positions such as feeds, instant articles, and stories.


Facebook Ads (v15-10-2015) integration: Improved error handling

We’ve updated the error handling in the integration to more aggressively retry when Insights jobs fail. As a result of this change, the error rate for this integration has been significantly reduced.


Extraction logs now available!

Detailed Extraction Logs are now available for select integrations in Stitch. This new feature presents detailed information about the extraction process in these integrations, and lets you:

  • Inspect, copy, and download extraction log files up to 50MB in size
  • View historical logs over the past seven days
  • Visualize how often extraction runs, how long it takes, and when it errors
  • View logs for extraction jobs currently in progress

This feature is available for the following integrations:

We’ll be working over the coming weeks to bring these logs to the rest of our integrations. Check out the docs for more info on this new feature.


Facebook Ads (v1) integrations: Ads, AdSets, and Campaigns now replicate incrementally!

Big news: The following integration tables, which previously replicated in full, now use Key-based Incremental Replication:

  • ads
  • adsets
  • campaigns

These tables use updated_time as Replication Keys, ensuring you’re only replicating records that have been updated. You can learn more about these tables in our integration documentation.


Facebook Ads (v1) integrations: AdLabel data is now available!

We’ve added the adlabels fields to the adsets and campaigns tables for our (v) integration.

Learn more in our documentation.


Facebook Ads integration: New version (v1)

A new (open-sourced!) version (v) of our integration is now available! This version, built from the ground up, supports field selection for increased control over what data you replicate through Stitch.

Learn more about the integration in our integration documentation.