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.
| Route | Best for | Main limitation |
|---|---|---|
| BigQuery Data Transfer Service | Standard Instagram and Facebook Ads reporting | 24-hour minimum transfer interval and fixed report tables |
| Managed connector, such as Supermetrics | Cross-channel reporting, normalized tables and simpler transformations | Adds a third-party platform and connector cost |
| Custom Meta Marketing API pipeline | Custom fields, frequent ingestion or advanced transformations | Requires 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.
You need the following:
ads_read, ads_management and business_managementGoogle 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.
Connect Instagram Ads through the Facebook Ads source in BigQuery Data Transfer Service. The process has four main parts.
In Google Cloud:
Use a dedicated dataset such as meta_ads_raw instead of mixing imported source data with reporting views.
In the Meta developer dashboard:
The Meta Ads Insights API provides performance data for ad accounts, campaigns, ad sets and individual ads. Insights access requires the ads_read permission.
In Google Cloud:
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.
To report Instagram separately from Facebook, include:
PublisherPlatformPlatformPositionPublisherPlatform 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.
The native transfer can populate tables including:
AdAccountsAdInsightsAdInsightsActionsAdsAdCreativesAdSetsCampaignsAdImagesBusinessesCustomAudiencesAdInsights 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.
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.
Configure action collections when creating the transfer. Available collections can include:
ActionsConversionsConversionValuesPurchaseRoasWebsitePurchaseRoasOutboundClicksVideoPlayActionsThese 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:
AdInsights by ad, placement and reporting period.AdInsightsActions by the same keys and action type.The native Facebook Ads transfer works for scheduled reporting, but it has several constraints:
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.
Use a managed connector when you need:
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.
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 advertisinginstagram_organic_raw for organic Instagram account and media insightsThis 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:
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.