Linkrunner connector
Set up the Linkrunner connector in Kaivo: authentication, configuration, the 2 BigQuery tables it syncs, and answers to common questions.
Linkrunner connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Linkrunner 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 Linkrunner connector
Section titled “What is the Linkrunner connector”Sync your Linkrunner attribution data into BigQuery with Kaivo to connect campaigns to users and measure marketing performance.
| Category | Marketing & Sales, Tech |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the Linkrunner connector
Section titled “Getting started with the Linkrunner connector”- Sign up for Kaivo and create a workspace.
- Connect your Linkrunner 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 Linkrunner
Section titled “Authenticating Linkrunner”Authenticate with your LinkRunner API Key.
| Field | Description |
|---|---|
| LinkRunner API Key | |
| Your LinkRunner API key from the dashboard. |
|
Configuring the Linkrunner connector
Section titled “Configuring the Linkrunner connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| Campaign Filter | |
| Filter campaigns by status. |
| | Channel Filter |
Filter by advertising channel.
|
Tables and columns synced from Linkrunner
Section titled “Tables and columns synced from Linkrunner”Kaivo syncs 2 tables from Linkrunner into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
attributed_users (23 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
attributed_at |
STRING |
|
campaign_display_id |
STRING |
|
campaign_name |
STRING |
|
link |
STRING |
|
installed_at |
STRING |
|
store_click_at |
STRING |
|
ad_set_id |
STRING |
|
user_data__id |
STRING |
|
user_data__email |
STRING |
|
user_data__device_data__idfv |
STRING |
|
user_data__device_data__locale |
STRING |
|
user_data__device_data__country |
STRING |
|
user_data__device_data__language |
STRING |
|
user_data__device_data__timezone |
STRING |
|
user_data__device_data__device_display__scale |
FLOAT64 |
|
user_data__device_data__device_display__width |
FLOAT64 |
|
user_data__device_data__device_display__height |
FLOAT64 |
|
user_data__device_data__timezone_offset |
FLOAT64 |
|
user_data__device_data__install_instance_id |
STRING |
|
user_data__device_data__adservices_attribution_token |
STRING |
|
user_data__device_data__idfa |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
campaigns (23 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
display_id |
STRING |
|
name |
STRING |
|
created_at |
STRING |
|
update_at |
STRING |
|
google |
BOOL |
|
meta |
BOOL |
|
meta_campaign_id |
STRING |
|
meta_web_to_app |
BOOL |
|
active |
BOOL |
|
default_link |
BOOL |
|
attributed_users |
FLOAT64 |
|
link |
STRING |
|
shareable_link |
STRING |
|
website |
STRING |
|
domain |
STRING |
Domain used to generate campaign links |
android_web_redirect |
STRING |
Android-specific web redirect URL |
ios_web_redirect |
STRING |
iOS-specific web redirect URL |
network_account__id |
FLOAT64 |
|
network_account__name |
STRING |
|
network_account__status |
STRING |
|
network_account__capi_configured |
BOOL |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: campaigns__store_listings
Section titled “Subtable: campaigns__store_listings”| 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. |
store_listing_id |
STRING |
|
name |
STRING |
|
platform |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Linkrunner sync works
Section titled “How the Linkrunner sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Linkrunner 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
Section titled “Frequently asked questions”How long does the initial sync take for Linkrunner?
Section titled “How long does the initial sync take for Linkrunner?”It depends on how much history is in your Linkrunner 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?
Section titled “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 Linkrunner’s schema changes?
Section titled “What happens when Linkrunner’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 Linkrunner, 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.
How do I handle GDPR or data deletion requests?
Section titled “How do I handle GDPR or data deletion requests?”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 Linkrunner 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 Linkrunner connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Linkrunner data
Section titled “Common use cases for Linkrunner data”Attribution
Section titled “Attribution”Use campaigns and attributed_users to see which campaigns drive signups.
Campaign performance
Section titled “Campaign performance”Track campaigns to compare results across channels over time.
Marketing context
Section titled “Marketing context”Join attribution data with your product data to connect campaigns to outcomes.
Use Linkrunner data in your AI and BI tools
Section titled “Use Linkrunner data in your AI and BI tools”Once Linkrunner 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 Linkrunner data.
Claude
Section titled “Claude”Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →
Power BI
Section titled “Power BI”Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →
Data Studio
Section titled “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
Section titled “Tableau”The premium analytics standard, with native BigQuery integration. Setup guide →
Google Sheets
Section titled “Google Sheets”Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →
Connect via Power Query’s BigQuery connector. Setup guide →
Metabase
Section titled “Metabase”Open-source BI tool with strong BigQuery support. Setup guide →
See our pricing page for Linkrunner connector pricing and plan details.
Related connectors
Section titled “Related connectors”- 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.