Pivotal Tracker connector
Set up the Pivotal Tracker connector in Kaivo: authentication, configuration, the 7 BigQuery tables it syncs, and answers to common questions.
Pivotal Tracker connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Pivotal Tracker 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 project management data instead of moving it.
What is the Pivotal Tracker connector
Section titled “What is the Pivotal Tracker connector”Sync your Pivotal Tracker data into BigQuery with Kaivo to report on stories, releases, and team velocity.
| Category | Project Management |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the Pivotal Tracker connector
Section titled “Getting started with the Pivotal Tracker connector”- Sign up for Kaivo and create a workspace.
- Connect your Pivotal Tracker 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 Pivotal Tracker
Section titled “Authenticating Pivotal Tracker”Authenticate with your API Token.
| Field | Description |
|---|---|
| API Token | |
| Your Pivotal Tracker API token. Found under Profile > API Token in your account settings. |
|
Tables and columns synced from Pivotal Tracker
Section titled “Tables and columns synced from Pivotal Tracker”Kaivo syncs 7 tables from Pivotal Tracker into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
activity (15 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
guid |
STRING |
|
kind |
STRING |
|
project_id |
INT64 |
|
occurred_at |
TIMESTAMP |
|
performed_by__id |
INT64 |
|
performed_by__kind |
STRING |
|
performed_by__name |
STRING |
|
performed_by__initials |
STRING |
|
performed_by__email |
STRING |
|
performed_by__username |
STRING |
|
message |
STRING |
|
highlight |
STRING |
|
project_version |
INT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: activity__secondary_resources
Section titled “Subtable: activity__secondary_resources”| 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 |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: activity__changes
Section titled “Subtable: activity__changes”| 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. |
id |
INT64 |
|
kind |
STRING |
|
change_type |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: activity__primary_resources
Section titled “Subtable: activity__primary_resources”| 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. |
id |
INT64 |
|
kind |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
epics (16 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
INT64 |
|
url |
STRING |
|
kind |
STRING |
|
name |
STRING |
|
label__id |
INT64 |
|
label__kind |
STRING |
|
label__name |
STRING |
|
label__created_at |
TIMESTAMP |
|
label__project_id |
INT64 |
|
label__updated_at |
TIMESTAMP |
|
created_at |
TIMESTAMP |
|
project_id |
INT64 |
|
updated_at |
TIMESTAMP |
|
description |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
labels (8 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
INT64 |
|
kind |
STRING |
|
name |
STRING |
|
created_at |
TIMESTAMP |
|
project_id |
INT64 |
|
updated_at |
TIMESTAMP |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
project_memberships (19 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
INT64 |
|
kind |
STRING |
|
role |
STRING |
|
person__id |
INT64 |
|
person__kind |
STRING |
|
person__name |
STRING |
|
person__email |
STRING |
|
person__initials |
STRING |
|
person__username |
STRING |
|
favorite |
BOOL |
|
created_at |
TIMESTAMP |
|
project_id |
INT64 |
|
updated_at |
TIMESTAMP |
|
project_color |
STRING |
|
last_viewed_at |
TIMESTAMP |
|
wants_comment_notification_emails |
BOOL |
|
will_receive_mention_notifications_or_emails |
BOOL |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
projects (31 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
INT64 |
|
kind |
STRING |
|
show_priority_icon |
BOOL |
|
show_priority_icon_in_all_panels |
BOOL |
|
created_at |
TIMESTAMP |
|
updated_at |
TIMESTAMP |
|
project_id |
INT64 |
|
name |
STRING |
|
account_id |
INT64 |
|
version |
INT64 |
|
iteration_length |
INT64 |
|
current_iteration_number |
INT64 |
|
week_start_day |
STRING |
|
point_scale |
STRING |
|
point_scale_is_custom |
BOOL |
|
bugs_and_chores_are_estimatable |
BOOL |
|
automatic_planning |
BOOL |
|
enable_tasks |
BOOL |
|
velocity_averaged_over |
INT64 |
|
number_of_done_iterations_to_show |
INT64 |
|
has_google_domain |
BOOL |
|
enable_incoming_emails |
BOOL |
|
initial_velocity |
INT64 |
|
public |
BOOL |
|
atom_enabled |
BOOL |
|
enable_following |
BOOL |
|
show_story_priority |
BOOL |
|
project_type |
STRING |
|
start_time |
TIMESTAMP |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
releases (12 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
INT64 |
|
url |
STRING |
|
kind |
STRING |
|
name |
STRING |
|
deadline |
TIMESTAMP |
|
created_at |
TIMESTAMP |
|
project_id |
INT64 |
|
updated_at |
TIMESTAMP |
|
accepted_at |
TIMESTAMP |
|
current_state |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: releases__labels
Section titled “Subtable: releases__labels”| 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. |
id |
INT64 |
|
kind |
STRING |
|
name |
STRING |
|
created_at |
TIMESTAMP |
|
project_id |
INT64 |
|
updated_at |
TIMESTAMP |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
stories (18 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
INT64 |
|
url |
STRING |
|
kind |
STRING |
|
name |
STRING |
|
deadline |
TIMESTAMP |
|
estimate |
INT64 |
|
created_at |
TIMESTAMP |
|
project_id |
INT64 |
|
story_type |
STRING |
|
updated_at |
TIMESTAMP |
|
accepted_at |
TIMESTAMP |
|
description |
STRING |
|
owned_by_id |
INT64 |
|
current_state |
STRING |
|
story_priority |
STRING |
|
requested_by_id |
INT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: stories__labels
Section titled “Subtable: stories__labels”| 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. |
id |
INT64 |
|
kind |
STRING |
|
name |
STRING |
|
created_at |
TIMESTAMP |
|
project_id |
INT64 |
|
updated_at |
TIMESTAMP |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: stories__owner_ids
Section titled “Subtable: stories__owner_ids”| 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 |
INT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Pivotal Tracker sync works
Section titled “How the Pivotal Tracker sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Pivotal Tracker 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 Pivotal Tracker?
Section titled “How long does the initial sync take for Pivotal Tracker?”It depends on how much history is in your Pivotal Tracker 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 Pivotal Tracker’s schema changes?
Section titled “What happens when Pivotal Tracker’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 Pivotal Tracker, 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 Pivotal Tracker 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 Pivotal Tracker connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Pivotal Tracker data
Section titled “Common use cases for Pivotal Tracker data”Velocity tracking
Section titled “Velocity tracking”Use stories and activity to measure throughput and cycle time over time.
Release progress
Section titled “Release progress”Join releases and epics with stories to track delivery against plan.
Workload view
Section titled “Workload view”Use project_memberships with stories to balance work across the team.
Use Pivotal Tracker data in your AI and BI tools
Section titled “Use Pivotal Tracker data in your AI and BI tools”Once Pivotal Tracker 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 Pivotal Tracker 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 Pivotal Tracker connector pricing and plan details.