Release Noteslink
October 2023link
Fivetran now supports extracting data from Pendo using Data Sync.
May 2023link
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_idaccountIdvisitorIdhourremoteIpserveruserAgent
March 2023link
We have added a new primary key column, _fivetran_id, to the following tables to avoid data integrity issues:
GUIDE_EVENTPOLL_EVENTEVENTTRACK_TYPE_EVENT
This functionality is enabled by default for new connectors created after March 21, 2023. We are gradually rolling out this change to all the existing connectors.
We now sync the properties field of the PAGE_EVENT and EVENT tables.
February 2023link
You can now exclude the following tables from your syncs:
ACCOUNT_APPLICATION_HISTORYACCOUNT_HISTORYAPPLICATION_HISTORYEVENTFEATURE_ELEMENT_PATH_RULE_HISTORYFEATURE_EVENTFEATURE HISTORYGUIDE_EVENTGUIDE_HISTORYPAGE_EVENTPAGE_HISTORYPAGE_RULE_HISTORYPOLL_EVENTTRACK_TYPE_EVENTTRACK_TYPE_HISTORYTRACK_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 2023link
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 2022link
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 connectors created after December 15, 2022. We are gradually rolling out the feature to all the existing connectors.
October 2022link
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 2022link
We have added the following columns to the GUIDE_EVENT table:
ui_element_actionsui_element_idui_element_textui_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 2022link
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 2021link
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*.
* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.
May 2021link
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 2021link
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 2020link
We now sync the following tables on a priority-first basis:
EVENTFEATURE_EVENTGUIDE_EVENTPAGE_EVENTPOLL_EVENTTRACK_TYPE_EVENT
September 2020link
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 2020link
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 2020link
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 2019link
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 2019link
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 2019link
We now provide segmentio metadata in ACCOUNT_HISTORY and VISITOR_HISTORY tables.
April 2019link
We have changed the data type of n_id in the VISITOR table from Long to String.
January 2019link
Pendo helps product teams understand and guide users to create product experiences that customers love.