LinkedIn Pages connector

Set up the LinkedIn Pages connector in Kaivo: authentication, configuration, the 4 BigQuery tables it syncs, and answers to common questions.

Written By Lauri Raivio

Last updated 16 days ago

Kaivo is a fully managed data platform that syncs your LinkedIn Pages data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your marketing and sales data instead of moving it.

What is the LinkedIn Pages connector

Sync your LinkedIn Pages follower and post statistics into BigQuery with Kaivo to track organic social performance alongside the rest of your data.

Category	Marketing & Sales
Authentication	OAuth or API key
Setup	Self-service

Getting started with the LinkedIn Pages connector

Sign up for Kaivo and create a workspace.
Connect your LinkedIn Pages account.
Choose which tables to sync.
Wait for the initial sync to finish.
Query your data in BigQuery or your favourite AI or BI tool.

Authenticating LinkedIn Pages

The LinkedIn Pages connector supports 2 ways to connect. Pick the one that fits how you work.

Connect by signing in to your LinkedIn Pages account. Kaivo runs the connection for you, so you never share a password.

API key

Authenticate with your Page ID.

Field	Description
Page ID	Your LinkedIn page's ID. When you go to the admin dashboard of your page, you can see the ID in the URL. For example, if the URL is "https://www.linkedin.com/company/123456789/admin/dashboard/", your page ID is "123456789".

Configuring the LinkedIn Pages connector

When you set up the connector, you provide:

Field	Description
Start Date	Any data before this date will not be fetched.
Time Granularity Type	Granularity of the statistics for metrics per time period.

Tables and columns synced from LinkedIn Pages

Kaivo syncs 4 tables from LinkedIn Pages into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

follower_statistics (3 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`organizational_entity`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: follower_statistics__follower_counts_by_association_type

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: follower_statistics__follower_counts_by_function

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: follower_statistics__follower_counts_by_geo

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: follower_statistics__follower_counts_by_geo_country

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: follower_statistics__follower_counts_by_industry

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: follower_statistics__follower_counts_by_seniority

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: follower_statistics__follower_counts_by_staff_count_range

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

organization_lookup (18 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`auto_created`	`BOOL`
`created__actor`	`STRING`
`created__time`	`FLOAT64`
`default_locale__country`	`STRING`
`default_locale__language`	`STRING`
`id`	`FLOAT64`
`last_modified__actor`	`STRING`
`last_modified__time`	`FLOAT64`
`localized_name`	`STRING`
`name__localized__ru_ru`	`STRING`
`name__preferred_locale__country`	`STRING`
`name__preferred_locale__language`	`STRING`
`organization_type`	`STRING`
`primary_organization_type`	`STRING`
`vanity_name`	`STRING`
`version_tag`	`STRING`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: organization_lookup__alternative_names

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: organization_lookup__groups

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: organization_lookup__localized_specialties

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: organization_lookup__locations

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: organization_lookup__specialties

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`organizational_entity`	`STRING`
`total_share_statistics__click_count`	`FLOAT64`
`total_share_statistics__comment_count`	`FLOAT64`
`total_share_statistics__comment_mentions_count`	`FLOAT64`
`total_share_statistics__engagement`	`FLOAT64`
`total_share_statistics__impression_count`	`FLOAT64`
`total_share_statistics__like_count`	`FLOAT64`
`total_share_statistics__share_count`	`FLOAT64`
`total_share_statistics__share_mentions_count`	`FLOAT64`
`total_share_statistics__unique_impressions_count`	`FLOAT64`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

total_follower_count (3 columns)

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`first_degree_size`	`FLOAT64`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

How the LinkedIn Pages sync works

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where LinkedIn Pages supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won't get duplicate rows.

Frequently asked questions

How long does the initial sync take for LinkedIn Pages?

It depends on how much history is in your LinkedIn Pages account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they're much faster.

Can I sync only some tables or columns?

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don't select are never copied to your warehouse.

What happens when LinkedIn Pages's schema changes?

New fields are never added automatically. You choose which fields to sync, so data you haven't selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table's sync mode: full-refresh tables always match what's currently in LinkedIn Pages, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in LinkedIn Pages instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the LinkedIn Pages connector in Kaivo and all of its synced data is deleted with it.

Common use cases for LinkedIn Pages data

Follower growth

Use follower_statistics and total_follower_count to track audience growth over time.

Post engagement

Analyse share_statistics to see which posts earn the most engagement.

Organic and paid together

Combine Pages data with LinkedIn Ads in BigQuery for a full social view.

Content trends

Report on engagement over time to find what content resonates.

Use LinkedIn Pages data in your AI and BI tools

Once LinkedIn Pages data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here's how the most common destinations work with LinkedIn Pages data.

Claude

Use Kaivo's MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Power BI

Microsoft's BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Data Studio

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

Tableau

The premium analytics standard, with native BigQuery integration. Setup guide →

Google Sheets

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Excel

Connect via Power Query's BigQuery connector. Setup guide →

Metabase

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for LinkedIn Pages connector pricing and plan details.

Google Ads: Sync Google Ads to BigQuery.
Custobar: Sync Custobar to BigQuery.
Google Search Console: Sync Google Search Console to BigQuery.
HubSpot: Sync HubSpot to BigQuery.
Adform: Sync Adform to BigQuery.
Amplitude: Sync Amplitude to BigQuery.

Was this helpful?

Still need help? Share an idea