Skip to content
Book a demoStart free
Connectors

Blogger connector

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

Blogger connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Blogger 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.

Sync your Blogger posts, pages, and comments into BigQuery with Kaivo to track publishing output and reader engagement across your blogs.

CategoryMarketing & Sales
AuthenticationAPI key
SetupSelf-service

Getting started with the Blogger connector

Section titled “Getting started with the Blogger connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Blogger account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Authenticate with your Blogger credentials. You provide:

Field Description
Client Secret
The Client Secret from your Google Cloud OAuth 2.0 credentials.

| | Refresh Token |

The OAuth refresh token obtained by authorizing your app against the Blogger API.

|

Prerequisites

Blogger uses Google OAuth, so you need to register your own Google Cloud application:

  1. In the Google Cloud Console, create a project, enable the Blogger API v3, and create OAuth 2.0 credentials to obtain a Client ID and Client Secret.
  2. Authorize your app for the Blogger API (scope https://www.googleapis.com/auth/blogger.readonly) and complete the OAuth consent flow once — for example with the Google OAuth 2.0 Playground configured to use your own Client ID and Secret — to obtain a Refresh Token.

Then enter those values below.

Need help? Reach our team via the chat in the bottom-right corner.

When you set up the connector, you provide:

Field Description
Client ID
The Client ID from your Google Cloud OAuth 2.0 credentials.

|

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

blogs (18 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
author__display_name STRING
author__id STRING
author__image__url STRING
author__url STRING
blog__id STRING
content STRING
etag STRING
id STRING
kind STRING
published STRING
replies__self_link STRING
replies__total_items STRING
self_link STRING
title STRING
updated STRING
url STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
comments (14 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
author__display_name STRING
author__id STRING
author__image__url STRING
author__url STRING
blog__id STRING
content STRING
id STRING
kind STRING
post__id STRING
published STRING
self_link STRING
updated STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
pages (16 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
author__display_name STRING
author__id STRING
author__image__url STRING
author__url STRING
blog__id STRING
content STRING
etag STRING
id STRING
kind STRING
published STRING
self_link STRING
title STRING
updated STRING
url STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
posts (18 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
author__display_name STRING
author__id STRING
author__image__url STRING
author__url STRING
blog__id STRING
content STRING
etag STRING
id STRING
kind STRING
published STRING
replies__self_link STRING
replies__total_items STRING
self_link STRING
title STRING
updated STRING
url STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
users (18 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
description STRING
id STRING
kind STRING
locale__country STRING
locale__language STRING
locale__variant STRING
name STRING
pages__self_link STRING
pages__total_items FLOAT64
posts__self_link STRING
posts__total_items FLOAT64
published STRING
self_link STRING
status STRING
updated STRING
url STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Blogger 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.

How long does the initial sync take for Blogger?

Section titled “How long does the initial sync take for Blogger?”

It depends on how much history is in your Blogger 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.

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 Blogger’s schema changes?

Section titled “What happens when Blogger’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 Blogger, 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 Blogger 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 Blogger connector in Kaivo and all of its synced data is deleted with it.

Aggregate posts by published date and blog to see how often you publish.

Join posts with comments and replies to find which content draws the most discussion.

Report on posts and pages across blogs to keep track of what is live.

Use author on posts to see contribution by writer over time.

Once Blogger 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 Blogger data.

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

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

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

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

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

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

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

See our pricing page for Blogger connector pricing and plan details.