Circle Separator5 Min. Lesezeit

How to Connect LinkedIn Ads to BigQuery

The most practical way to connect LinkedIn Ads to BigQuery is to use a managed ETL connector. The connector authenticates with LinkedIn's Advertising API, retrieves campaign reporting data and loads it into BigQuery on a schedule.

There are 3 practical routes:

  • Use a managed connector for fast, recurring reporting.
  • Build a custom pipeline when you need control over requests, storage and transformations.
  • Export CSV files for one-off transfers or historical backfills.

LinkedIn's official integration route is its Marketing API. BigQuery has its own loading and ingestion methods, so connecting the two usually requires either a third-party connector or a custom extraction pipeline.

LinkedIn Ads to BigQuery: the Best Option by Use Case

RequirementRecommended approachWhy
Fast setup with minimal engineeringManaged ETL connectorHandles authentication, scheduling, loading and common schema changes
Multiple advertising platformsMulti-source connectorBrings LinkedIn Ads, Google Ads, Meta Ads and other channels into one system
Full control over fields and transformationsCustom API pipelineLets you define requests, storage and data models
One-time exportCSV upload to BigQuerySimple, but not automated
High-volume or regulated environmentCustom pipeline with governance controlsGives you more control over access, logging and retention

What LinkedIn Ads Data Can You Load Into BigQuery?

You can load account, campaign, campaign group, creative and supported demographic reporting into BigQuery. Common metrics include:

  • Impressions
  • Clicks
  • Ad spend
  • Leads
  • Conversions
  • Opens and sends for applicable campaign types
  • Video engagement metrics
  • Professional demographic results
  • Performance by company size, industry, seniority, job function, job title and region

The available metrics depend on the reporting pivot. LinkedIn states that some metrics are unavailable with particular pivots, so the number of fields supported by a connector is only part of the evaluation. The connector must support the dimensions and metrics your reports need in combination.

A useful BigQuery model usually separates the data into tables such as:

  • linkedin_ads_raw
  • linkedin_campaign_performance
  • linkedin_creative_performance
  • linkedin_demographic_performance
  • linkedin_ads_sync_log

Keep the original API response separate from the reporting tables. The raw layer helps you investigate discrepancies, replay failed loads and troubleshoot a sync without repeatedly querying LinkedIn.

Option 1: Use a Managed LinkedIn Ads Connector

A managed connector suits marketing teams that need reliable reporting without maintaining an API integration.

Typical Setup Process

  1. Create or select a BigQuery project.
  2. Create a dataset for LinkedIn Ads.
  3. Connect the LinkedIn advertising account through OAuth.
  4. Give the connector access to the required ad accounts.
  5. Select the reporting entities and metrics.
  6. Choose the destination dataset and table structure.
  7. Set the sync frequency.
  8. Compare the loaded totals with LinkedIn Campaign Manager.
  9. Build dashboards or transformation models on the loaded tables.

The connector should support:

  • LinkedIn OAuth reauthorisation
  • Multiple ad accounts
  • Campaign, campaign group and creative data
  • Incremental extraction
  • Historical backfills
  • Schema change handling
  • Retry logic and API error reporting
  • Raw and normalised tables
  • Sync monitoring
  • Destination table partitioning or similar cost controls

Do not assume that every LinkedIn Ads connector supports the same API resources. Some tools load only basic campaign metrics. Others also support demographic reporting, conversion data or lead information.

Option 2: Build a Custom LinkedIn Ads to BigQuery Pipeline

A custom pipeline gives you more control, but your team must maintain the extraction, error handling and data model.

A typical architecture looks like this:

LinkedIn Advertising API
        ↓
Extractor service
        ↓
Raw storage or staging table
        ↓
Transformation layer
        ↓
BigQuery reporting tables
        ↓
Looker, Power BI, Tableau or internal analytics

LinkedIn's reporting API requires the appropriate advertising permissions. The r_ads_reporting permission is used to retrieve advertising account reporting data. LinkedIn Marketing API access also uses authenticated member authorisation rather than a simple unauthenticated server connection.

A custom extractor should:

  1. Authenticate through LinkedIn OAuth.
  2. Retrieve the advertising accounts available to the authorised user.
  3. Request account, campaign and creative reporting.
  4. Store the original response in a raw layer.
  5. Resolve LinkedIn URNs into stable account, campaign and creative identifiers.
  6. Upsert new and corrected reporting records.
  7. Record request status, response errors and row counts.
  8. Apply retention and deletion rules.
  9. Publish clean tables for analytics.

LinkedIn's Ad Analytics endpoint supports finder methods for analytics, statistics and attributed revenue metrics. It also has restrictions around pagination, metric availability and reporting pivots. The extractor needs to handle those restrictions before the data reaches dashboard users.

Option 3: Export LinkedIn Ads as CSV and Load It Into BigQuery

CSV works for:

  • A one-time historical import
  • A small advertising account
  • Testing a BigQuery schema
  • Recovering data while an API connection is being repaired

The process is:

  1. Export reporting data from LinkedIn Campaign Manager.
  2. Upload the file to Cloud Storage.
  3. Create a BigQuery load job.
  4. Select the correct schema and data types.
  5. Append to or replace the destination table.
  6. Check totals and field mappings.

BigQuery supports CSV, JSON, Avro, ORC and Parquet data through load jobs. Google recommends scheduled or automated loading methods for recurring ingestion rather than manual uploads.

CSV is a poor long-term choice because it does not provide reliable incremental extraction, automatic reauthorisation, error monitoring or consistent handling of campaign changes.

The BigQuery Schema to Use

A campaign performance table should include fields such as:

Field groupExample fields
Identifiersaccount_id, campaign_group_id, campaign_id, creative_id
Namesaccount_name, campaign_name, creative_name
Reporting grainreport_period, time_granularity, currency
Delivery metricsimpressions, clicks, reach
Cost metricsspend, cost_per_click, cost_per_lead
Conversion metricsleads, conversions, conversion_value
Metadatacampaign_status, objective, campaign_type
Pipeline fieldsextracted_at, source_system, sync_run_id

Where possible, use one row for each reporting period, account, campaign and creative combination. Do not put campaign-level and demographic-level records in the same fact table. The two grains differ, so combining them can multiply spend, impressions or conversion totals.

A clean model often includes:

  • A campaign fact table with performance by account and campaign
  • A creative fact table with performance by advertisement creative
  • A demographic fact table with performance by professional audience segment
  • Dimension tables for campaigns, accounts, creatives and conversion metadata

Important LinkedIn Reporting Limitations

Reporting Latency Varies by Metric

Account, campaign and creative performance metrics are described by LinkedIn as near real-time. Professional demographic metrics can be delayed by 12 to 24 hours. Some video watch-time metrics can be delayed by up to 48 hours.

Your pipeline should update existing records after the first extraction. Treating the first result as final can leave reports incomplete.

Demographic Metrics Are Approximate

LinkedIn states that professional demographic metrics are approximate for privacy reasons. Totals can differ when you compare different reporting ranges, reporting levels or combinations of dimensions.

Do not treat demographic breakdowns as an exact additive allocation of campaign totals.

Metrics Are Not Available at Every Reporting Level

A metric may be available at campaign level but unavailable for a demographic or device pivot. Preserve null values when LinkedIn does not provide a metric. Do not convert missing values into zero.

API Access Is Separate From User Interface Access

A user may be able to view an account in Campaign Manager without the connected application having the required API access. LinkedIn controls access through application approval, OAuth permissions and advertising account authorisation.

Data Retention and Compliance

Do not treat BigQuery as an unrestricted archive for LinkedIn API data.

LinkedIn's storage requirements set retention limits for different categories of Marketing API data. Advertising account administration and reporting data have one storage period, while professional demographic data has a separate requirement. LinkedIn also has additional conditions for member-related data and deletion requests.

Your pipeline should include:

  • A documented retention policy
  • Automated deletion or expiration
  • Access controls for demographic tables
  • Separate handling for lead and member-related data
  • Audit logs for extraction and deletion
  • A process for responding to LinkedIn policy changes

A connector that stores data indefinitely without configurable retention controls can create a governance problem even when the sync itself works.

How to Validate the Connection

After loading LinkedIn Ads into BigQuery, compare:

  1. Total spend by advertising account
  2. Impressions and clicks by campaign
  3. Conversion and lead totals
  4. Currency handling
  5. Reporting time zone
  6. Campaign and creative identifiers
  7. Results for a completed reporting range
  8. Results after LinkedIn reporting latency has passed

Use a tolerance policy for metrics known to be approximate or delayed. Investigate large differences caused by:

  • Duplicated rows
  • Mixed reporting grains
  • Currency conversion
  • Attribution windows
  • Failed incremental updates
  • Incomplete account access

Final Recommendation

Use a managed connector when you need to centralise LinkedIn Ads data quickly for dashboards, attribution models or marketing performance reporting.

Build a custom pipeline when you need non-standard API requests, custom attribution logic, control over retention, detailed observability, integration with an existing data platform or lower variable connector costs at significant scale.

Use CSV for temporary transfers and one-off imports. For a production setup, load LinkedIn Advertising API data into a raw BigQuery layer, then publish separate campaign, creative and demographic tables.

Als Nächstes lesen