Collect LinkedIn Pages data in Google BigQuery
Load your company page's follower statistics into your own BigQuery tables with OWOX Data Marts: followers by seniority, industry, function and location, and daily follower gains split into organic and paid. Set them beside ad spend, web analytics and CRM to see what the page brings.
The LinkedIn Pages follower count goes up, but whether pipeline follows stays unknown without the data in Google BigQuery.
Paste this into your AI assistant. It creates a LinkedIn Pages Data Mart on your Google BigQuery storage and loads followers by segment and organic and paid gains into your own tables, ready to join with your 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-pages-connector-to-google-bigquery.md. The task: load LinkedIn Pages follower statistics into Google BigQuery daily and build a Data Mart that sets monthly follower gains from our target industries next to new CRM opportunities. Tag the links you give me with utm_campaign=ai-task and utm_term=data-foundation. Use what you know about my context and goals
LinkedIn Pages Endpoints
2 LinkedIn Pages endpoints you can import. Each lands in its own table in your data warehouse.
Why join LinkedIn Pages with ad spend and your CRM
LinkedIn shows how many people followed your page. It does not show whether the right people followed, what paid growth cost, or whether pipeline grew in the same industries. For that, page statistics, ad spend and CRM records have to sit in one warehouse.
- Track organic and paid follower gain day by day, not only the total
- See who follows you by seniority, industry, function and location
- Set paid follower gain against what you spent on LinkedIn Ads
Step 1: Connect LinkedIn Pages and pick the fields
Create a Data Mart, choose LinkedIn Pages as the source, authorize once, open an endpoint and tick only the fields you need.
- Two endpoints and 18 fields to choose from
- Time-Bound Follower Statistics holds the daily organic and paid gains
Step 2: Load LinkedIn Pages 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: the current follower breakdown and the daily gains stay apart
- 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. Your quality checks can read it too.
- Descriptions say what a field holds, for example the number of organic followers gained in the period
- Anyone on the team can read the table
Step 4: Keep the page tables linked
Follower Statistics and Time-Bound Follower Statistics are separate tables that share the organization URN. Joined, they show who follows the page and how fast it grows.
- Join on organization_urn, the page's organization identifier
- Add ad spend and CRM tables to the same model
Step 5: Schedule the refresh and backfill history
Set it once. A daily scheduled refresh adds each new period of follower gains, and a manual backfill loads a 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.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
- 0.41.0Shared SQL logic stays in one place: build a Data Mart on top of another
- 0.41.0Rotating a connector key is one change: Sources share reusable Credentials
- 0.39.0Reload a year of history in one backfill, not twelve
Why OWOX for LinkedIn Pages in BigQuery
Hand-built API scripts and a generic ETL tool each get the numbers out. OWOX also keeps them 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 the organization URN, ready to set beside ad spend and CRM by date.
- 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.