Release Notes

June 2026

We have added table re-sync support. Previously, we only supported connection-level re-syncs.

April 2026

We have added the following new tables:

• SEGMENT_HISTORY
• SEGMENT_FILTER
• SEGMENT_PIPELINE
• SEGMENT_DEPENDENT_METADATA

We are gradually rolling out this change to all existing connections.

October 2025

We unified each connector’s pre-built dbt Core–compatible data models into a single model. It standardizes and documents the Fivetran schemas created in your destination and outputs analytics-ready tables. Previously, most connectors used distinct source and transform models.

September 2025

Our Pendo connector now supports projects in the JPN region and AU region. To let a connector fetch data from Pendo's JPN or AU data center, you must change the integration key for the connector to one that is compatible with respective endpoint. Generate a compatible integration key from app.jpn.pendo.io for JPN region and app.au.pendo.io for AU region.

February 2025

We have added a new field, Historical Sync Time Frame, to the connector setup form. This allows you to select how much duration worth of historical data you want to sync. The default value is Sync all historical data. You can choose Sync data from selected date option from the drop down to set HistoricSync Backwards Limit form date picker. You can edit the connection details and set the time frame value for an existing connector. We have also added support for the historic_sync_time_frame field for connections created using the Create a connection endpoint. For more information, see our REST API config.

The historical sync limit only applies to the following tables.

• EVENT
• FEATURE_EVENT
• GUIDE_EVENT
• PAGE_EVENT
• POLL_EVENT
• TRACK_TYPE_EVENT

We are gradually rolling out this feature to all connections.

September 2024

We have added the following new columns to the PAGE_HISTORY table:

• isCoreEvent
• isSuggested
• kind

To sync the historical data for these columns, contact Fivetran support.

June 2024

We have added the following columns to the GUIDE_HISTORY table:

• audience
• audienceUiHint
• authored_language
• current_first_eligible_to_be_seen_at
• description
• editor_type
• is_module
• is_top_level
• kind
• published_ever

If you'd like to sync historical data for these columns, contact our support team.

October 2023

Fivetran now supports extracting data from Pendo using Data Sync.

May 2023

We have changed the primary key of the EVENT table. Now, we use only the _fivetran_id column as the primary key. Previously, we used a composite primary key which was a combination of the following columns:

• _fivetran_id
• accountId
• visitorId
• hour
• remoteIp
• server
• userAgent

March 2023

We have added a new primary key column, _fivetran_id, to the following tables to avoid data integrity issues:

• GUIDE_EVENT
• POLL_EVENT
• EVENT
• TRACK_TYPE_EVENT

This functionality is enabled by default for new connections created after March 21, 2023. We are gradually rolling out this change to all the existing connections.

We now sync the properties field of the PAGE_EVENT and EVENT tables.

February 2023

You can now exclude the following tables from your syncs:

• ACCOUNT_APPLICATION_HISTORY
• ACCOUNT_HISTORY
• APPLICATION_HISTORY
• EVENT
• FEATURE_ELEMENT_PATH_RULE_HISTORY
• FEATURE_EVENT
• FEATURE HISTORY
• GUIDE_EVENT
• GUIDE_HISTORY
• PAGE_EVENT
• PAGE_HISTORY
• PAGE_RULE_HISTORY
• POLL_EVENT
• TRACK_TYPE_EVENT
• TRACK_TYPE_HISTORY
• TRACK_TYPE_RULE_HISTORY

By default, we include these tables in syncs. To exclude the tables, go to the Schema tab of your connector details page and deselect the tables.

January 2023

You can now exclude the VISITOR, VISITOR_APPLICATION, and VISITOR_ACCOUNT_ASSOCIATION tables from the syncs. On your connector details page, go to the Schema tab and deselect the tables. By default, we include these tables in the sync. If you exclude the tables and later want to sync the tables, perform a complete table re-sync to ensure data integrity.

December 2022

We have added a new primary key column, _fivetran_id, to the PAGE_EVENT and FEATURE_EVENT tables to avoid data integrity issues. This functionality is enabled by default for new connections created after December 15, 2022. We are gradually rolling out the feature to all the existing connections.

October 2022

Our Pendo connector now supports projects in the US1 region. To fetch data from Pendo's US1 data center, you must change the integration key for the connector to one that is compatible with Pendo's US1 endpoint. Generate a compatible integration key from us1.app.pendo.io.

June 2022

We have added the following columns to the GUIDE_EVENT table:

• ui_element_actions
• ui_element_id
• ui_element_text
• ui_element_type

To sync your historical data from these columns, contact our support team.

We have added a new table, PICKLIST_POLL_RESPONSE, that stores the text response of the PickList poll type.

March 2022

Pendo processes data at the top of each hour, and it can take up to 15 minutes past the hour for that data to be available. As a result, events data is not immediately available to Fivetran through the API but within 15 minutes past the hour. We have updated our API calls for the VISITOR, EVENT, and POLL_EVENT tables to include a rollback time for the end cursors to fetch the data.

September 2021

We have released pre-built, dbt Core-compatible data models for Pendo. Find the models in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation.

May 2021

We have added a new field, Sync Mode, to the connector setup form. You can now select all or specific Pendo App Ids to sync to your destination. See our setup instructions for more details.

March 2021

We have added a new custom field, property_*, to the FEATURE_EVENT table.

We have added a new field, is_core_event, to the FEATURE_HISTORY table.

December 2020

We now sync the following tables on a priority-first basis:

• EVENT
• FEATURE_EVENT
• GUIDE_EVENT
• PAGE_EVENT
• POLL_EVENT
• TRACK_TYPE_EVENT

September 2020

We now sync property data in the TRACK_TYPE_EVENT table. We sync each property to the destination in its own column and add the prefix property_ to the column name. For example, the file property is synced to the destination as the property_file column.

July 2020

We now sync parameter data in the PAGE_EVENT, FEATURE_EVENT, and EVENT tables. We sync each parameter to the destination in its own column and add the prefix param_ to the column name. For example, the decisionData parameter is synced to the destination as the param_decisionData column.

April 2020

You can now configure your Pendo connector using the Fivetran REST API. This feature is in BETA and is available only for Standard and Enterprise accounts.

November 2019

The Pendo connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Pendo's priority-first syncs fetch the most recent seven days' worth of data from the ACCOUNT_HISTORY and VISITOR_HISTORY tables.

To learn more, see our priority-first sync documentation.

August 2019

Our Pendo connector now supports projects in the EU region. To let a connector fetch data from Pendo's EU data center, you must change the integration key for the connector to one that is compatible with Pendo's EU endpoint.  Generate a compatible integration key from app.eu.pendo.io.

June 2019

We now provide segmentio metadata in ACCOUNT_HISTORY and VISITOR_HISTORY tables.

April 2019

We have changed the data type of n_id column in the VISITOR table from LONG to STRING.

January 2019

Pendo helps product teams understand and guide users to create product experiences that customers love.

Read our Pendo connector documentation.