Circle Separator5 mins read

How Do You Connect Instagram Ads to BigQuery?

Google BigQuery Data Transfer Service is the standard way to connect Instagram Ads data to BigQuery. The service retrieves advertising data through Meta's Marketing API and loads it into BigQuery under the Facebook Ads source. Filter the imported data with PublisherPlatform = 'instagram' to isolate Instagram placements.

The native transfer is a practical choice for scheduled paid social reporting. It is maintained by Google, requires no custom ingestion code and creates BigQuery tables for ad accounts, campaigns, ad sets, ads, creatives, insights and actions. The minimum recurring transfer interval is 24 hours.

Native BigQuery Transfer Versus a Third-Party Connector

RouteBest forMain limitation
BigQuery Data Transfer ServiceStandard Instagram and Facebook Ads reporting24-hour minimum transfer interval and fixed report tables
Managed connector, such as SupermetricsCross-channel reporting, normalized tables and simpler transformationsAdds a third-party platform and connector cost
Custom Meta Marketing API pipelineCustom fields, frequent ingestion or advanced transformationsRequires engineering, token management and API monitoring

For most businesses, start with BigQuery Data Transfer Service. Use a managed connector when you need pre-structured tables across several advertising platforms. Build a custom pipeline only when the native transfer lacks the required reporting frequency or fields.

What You Need Before Connecting Instagram Ads

You need the following:

  • A Google Cloud project with BigQuery Data Transfer Service enabled
  • A BigQuery dataset for the imported Meta Ads tables
  • A Meta developer app with the Business app type
  • The Meta app ID and app secret
  • A long-lived Meta user access token or a suitable system user token
  • Access to the relevant Meta ad account
  • Meta permissions including ads_read, ads_management and business_management
  • Sufficient Google Cloud permissions to create a transfer configuration

Google lists a Meta app, client credentials and a long-lived access token as prerequisites for the Facebook Ads transfer. The setup also requires access to the BigQuery dataset and permissions to create the transfer.

How Do You Connect Instagram Ads to BigQuery?

Connect Instagram Ads through the Facebook Ads source in BigQuery Data Transfer Service. The process has four main parts.

1. Create the BigQuery Dataset

In Google Cloud:

  1. Open BigQuery.
  2. Select the Google Cloud project that will store the data.
  3. Create a dataset for Meta Ads data.
  4. Choose the dataset location carefully. The transfer configuration and destination must use compatible locations.

Use a dedicated dataset such as meta_ads_raw instead of mixing imported source data with reporting views.

2. Create or Select a Meta Developer App

In the Meta developer dashboard:

  1. Create a Business app.
  2. Copy the app ID.
  3. Copy the app secret.
  4. Configure the OAuth redirect URI shown in the Google Cloud transfer setup.
  5. Authorize the Meta user or system user that can access the required ad accounts.

The Meta Ads Insights API provides performance data for ad accounts, campaigns, ad sets and individual ads. Insights access requires the ads_read permission.

3. Create the Facebook Ads Transfer in BigQuery

In Google Cloud:

  1. Open BigQuery Data Transfer Service.
  2. Select Create transfer.
  3. Choose Facebook Ads as the data source.
  4. Enter the Meta app ID.
  5. Enter the Meta app secret.
  6. Authorize the Meta account or enter a valid token.
  7. Select the ad accounts and reports to transfer.
  8. Select the BigQuery dataset.
  9. Set the transfer schedule.
  10. Save the configuration.

The source is labelled Facebook Ads, but it also covers paid Instagram placements because Meta's Marketing API handles advertising across Facebook and Instagram. The imported insights data includes publisher and placement breakdowns that identify where an ad ran.

4. Select Instagram Placement Breakdowns

To report Instagram separately from Facebook, include:

  • PublisherPlatform
  • PlatformPosition

PublisherPlatform identifies the platform. PlatformPosition identifies placements such as Instagram Feed and Instagram Stories, along with other available placements. Google maps these values into the AdInsights table.

Avoid selecting incompatible breakdown combinations. Meta restricts which breakdowns can be requested together, and an invalid combination can cause the transfer to fail.

Which BigQuery Tables Contain Instagram Ads Data?

The native transfer can populate tables including:

  • AdAccounts
  • AdInsights
  • AdInsightsActions
  • Ads
  • AdCreatives
  • AdSets
  • Campaigns
  • AdImages
  • Businesses
  • CustomAudiences

AdInsights contains metrics such as spend, impressions, reach, clicks, campaign IDs, ad IDs and platform breakdowns. AdInsightsActions contains action and conversion records based on the action collections selected in the transfer configuration.

What SQL Isolates Instagram Ads in BigQuery?

After the first transfer completes, use this query to check the available platforms and placements:

SELECT DISTINCT
  PublisherPlatform,
  PlatformPosition
FROM `your_project.meta_ads_raw.AdInsights`
ORDER BY
  PublisherPlatform,
  PlatformPosition;

To retrieve Instagram ad performance:

SELECT
  DateStart,
  AdAccountId,
  CampaignId,
  CampaignName,
  AdSetId,
  AdId,
  AdName,
  Spend,
  Impressions,
  Reach,
  Clicks,
  PublisherPlatform,
  PlatformPosition
FROM `your_project.meta_ads_raw.AdInsights`
WHERE LOWER(PublisherPlatform) = 'instagram'
ORDER BY DateStart DESC;

Table and field names can vary according to the transfer schema and selected breakdowns, so inspect the generated table schema before creating production views. Google documents mappings such as date_start to DateStart, campaign_id to CampaignId, spend to Spend and publisher_platform to PublisherPlatform.

How Do You Include Instagram Conversions and Actions?

Configure action collections when creating the transfer. Available collections can include:

  • Actions
  • Conversions
  • ConversionValues
  • PurchaseRoas
  • WebsitePurchaseRoas
  • OutboundClicks
  • VideoPlayActions

These records are stored in AdInsightsActions. One ad can have multiple action types, so aggregate the action table before joining it to spend data. Joining several action rows directly to AdInsights can multiply spend and impression totals. Google identifies action collections as the source for records in AdInsightsActions.

Use this reporting pattern:

  1. Aggregate AdInsights by ad, placement and reporting period.
  2. Aggregate AdInsightsActions by the same keys and action type.
  3. Join the two aggregated results.
  4. Calculate CPA, ROAS or conversion rate in the final reporting view.

What Are the Limitations of the Native Connection?

The native Facebook Ads transfer works for scheduled reporting, but it has several constraints:

  • The minimum recurring transfer interval is 24 hours.
  • The connector supports a fixed set of tables rather than arbitrary custom reports.
  • Some insights tables do not use incremental transfers.
  • The refresh window is limited for several core ad reporting tables.
  • Meta access tokens require ongoing lifecycle management.
  • Invalid Meta breakdown combinations can cause a transfer to fail.
  • Large transfers can encounter Meta API rate limits.

Google also states that long-lived user access tokens expire and must be replaced or renewed through the transfer configuration. A system user token can be an alternative, but it still requires credential management and the correct access to the ad accounts.

When Should You Use a Managed Instagram Ads Connector?

Use a managed connector when you need:

  • Facebook, Instagram, Google Ads and other channels in one pipeline
  • Pre-structured reporting tables
  • Easier schema normalization
  • More convenient historical backfills
  • Less maintenance than a custom API integration

For example, Supermetrics supports Facebook and Instagram Ads as a combined source and can send the data to BigQuery alongside other advertising platforms. Its stated workflow is to connect the Meta account, blend the data and deliver it to BigQuery or another reporting destination.

A managed connector is useful when the reduction in engineering and transformation work justifies using another platform. It is not automatically a better choice than Google's native transfer.

How Are Paid Instagram Ads Different From Organic Instagram Insights?

The BigQuery Facebook Ads transfer covers paid advertising data, including campaign, ad set, ad, spend and conversion reporting.

Organic Instagram metrics, such as content performance, follower growth and media insights, come through separate Instagram Insights APIs or social analytics connectors. Meta documents Ads Insights and Instagram account or media insights as separate API areas.

If you need both datasets, store them separately:

  • meta_ads_raw for paid Meta advertising
  • instagram_organic_raw for organic Instagram account and media insights

This keeps paid placement data separate from organic post performance.

For a standard marketing warehouse, use this layout:

Meta Ads account
      ↓
BigQuery Data Transfer Service
      ↓
meta_ads_raw.AdInsights
meta_ads_raw.AdInsightsActions
meta_ads_raw.Campaigns
meta_ads_raw.AdSets
meta_ads_raw.Ads
      ↓
BigQuery reporting views
      ↓
Looker Studio, dashboards or attribution models

Create reporting views that standardize:

  • Ad account
  • Campaign
  • Ad set
  • Ad
  • Platform
  • Placement
  • Spend
  • Impressions
  • Reach
  • Clicks
  • Conversions
  • Conversion value
  • Attribution window

Create the native Facebook Ads transfer, select PublisherPlatform and PlatformPosition, then validate the AdInsights table before adding reporting logic. Use a managed connector or custom Meta API pipeline if you need more frequent ingestion, custom reports or normalized multi-channel data.

Next Read