Collect LinkedIn Ads data in Google BigQuery
Load LinkedIn Ads into your own BigQuery tables with OWOX Data Marts: one table per endpoint, a business-friendly schema, refreshed on a schedule. Join it with web analytics and CRM to see which ads become deals.
LinkedIn Ads reports cost and leads in its own account, so the pipeline it built never shows up in Google BigQuery.
Paste this into your AI assistant. It creates a LinkedIn Ads Data Mart on your Google BigQuery storage, loads ad analytics into your own tables on a schedule, and joins spend to web analytics and CRM.
The prompt
Read https://www.owox.com/ai-agent-setup.md and follow it to set up OWOX Data Marts for me, starting from /connectors/free-linkedin-ads-connector-to-google-bigquery.md. The task: load LinkedIn Ads ad analytics into Google BigQuery every day and build a Data Mart with cost, website conversions and CRM pipeline by campaign and month. Tag the links you give me with utm_campaign=ai-task and utm_term=m4. Use what you know about my context and goals
LinkedIn Ads Endpoints
8 LinkedIn Ads endpoints you can import. Each lands in its own table in your data warehouse.
Ad Accounts
Your ad account settings, billing details, currency, and account status.
14 fieldsAd Analytics
Daily performance metrics for your campaigns — impressions, clicks, spend, and conversions.
104 fieldsTime seriesAd Analytics by Country
Daily campaign performance by the country of the members who saw your ads — impressions, clicks, spend, and conversions per country.
100 fieldsTime seriesAd Analytics by County
Daily campaign performance by the county of the members who saw your ads — impressions, clicks, spend, and conversions per county.
100 fieldsTime seriesAd Analytics by Region
Daily campaign performance by the region of the members who saw your ads — impressions, clicks, spend, and conversions per region.
100 fieldsTime seriesCampaign Groups
Top-level containers that group campaigns with shared objectives, budgets, and scheduling.
14 fieldsCampaigns
Individual campaigns defining your targeting, ad format, bid strategy, and budget.
29 fieldsCreatives
The visual and copy elements of your ads shown to members across LinkedIn.
14 fields
Why join LinkedIn Ads with your web analytics and CRM
LinkedIn Ads shows what an ad cost. It cannot show which ad led to a deal that closed a year later. For that, ad spend, website touch points and CRM deals have to sit in one warehouse.
- Compare spend across LinkedIn, Facebook, Google and Microsoft Ads in one table
- Connect ad clicks and form submits to the deals they became
- Keep the data in your own tables, not inside an ad account
Step 1: Connect LinkedIn Ads and pick the fields
Create a Data Mart, choose LinkedIn Ads as the source, authorize once, open an endpoint and tick only the fields you need.
- Five endpoints and 175 fields to choose from
- Ad Analytics alone has 104 fields: spend, impressions, clicks, conversions, leads
Step 2: Load LinkedIn Ads into a BigQuery table
The dataset and table in your storage are pre-filled, and you can change them. Run it and the first load lands in your own BigQuery project.
- Each endpoint gets its own table, not one 300-column table
- Every run is logged in Run History
Step 3: Get a business-friendly output schema
After the first run you get the output schema: every field with a readable description, not an API identifier. Your quality checks can read it too.
- Field descriptions come from the LinkedIn Ads documentation
- Anyone on the team can read the table
Step 4: Keep the LinkedIn Ads tables linked
Campaign groups, campaigns, creatives and ad analytics stay separate tables, joined by ids. Together they become one LinkedIn Ads model.
- LinkedIn stores links as URNs such as urn:li:sponsoredAccount:{id}; extract the id to join
- Join the model to web analytics and CRM tables
Step 5: Schedule the refresh and backfill history
Set it once. A daily scheduled refresh keeps the tables current, and a manual backfill loads any past period.
- Daily runs with no pipeline to maintain
- Backfill history the first time you connect
Step 6: Reuse the same table everywhere
One table feeds your model, , , assistants like Claude and ChatGPT, and scheduled AI insights in Slack or email.
- Define the numbers once
- Every report reads the same table
- 0.44.0Connector Data Marts set up through MCP no longer fail their first run because of the table path
- 0.44.0Backfill a catalog for any period in one run, and follow a long backfill as parts of one operation
- 0.43.0Compare LinkedIn Ads results across markets: spend by country, region, and county
- 0.43.0Parallel reads of a SQL Data Mart on Google BigQuery no longer fail with a rate limit error
- 0.41.0Rotating a warehouse key is one change: Storages share reusable Credentials
Why OWOX for LinkedIn Ads in BigQuery
Hand-built API scripts, a native transfer or a generic ETL tool each get the data in. OWOX also keeps it yours, readable and ready to model.
- You own the data. It lands in your own data warehouse, in tables you control.
- A business-friendly schema. Readable field names and descriptions, not API identifiers.
- Ready for a data model. Separate tables per endpoint, joined by ids, built to connect to web analytics and CRM.
- Maintained for you. No scripts to fix when LinkedIn changes its API.
- Free to self-host. The open-source OWOX Data Marts runs in your own infrastructure.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.