Pendo is a product cloud that helps product teams deliver software users love. With Pendo, product teams can understand product usage, collect feedback, measure NPS, onboard users, and announce new features in app—all without requiring engineering resources.
This is an Event Cloud Source which can not only export data into your Segment warehouse, but can also federate the exported data into your other Segment Destinations.
This source is maintained by Pendo. For any issues with the source, please reach out to their team.
NOTE: The Pendo Source will continue to be adding new events sources as it is still in active development. This doc was last updated on September 13, 2019. If you have any feedback to help improve the Pendo Source and its documentation, please let their team know!
- From your Segment UI’s Sources page click on “Add Source”.
- Search for “Pendo” within the Sources Catalog and confirm by clicking “Connect”.
- Give the Source a nickname and follow the setup flow to “Add Source”. The nickname will be used to designate the source in the Segment interface, and Segment will create a related schema name. The schema name is the namespace you’ll be querying against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (eg. Pendo_Prod, Pendo_Staging, Pendo_Dev).
- Copy the Write Key from the Segment UI.
- Log in to your Pendo subscription - navigate to Settings > Integrations > Webhooks.
- Select “Add Webhook”.
- Give it a name, select “Segment” in the Type dropdown menu, and paste your Segment Write Key into the textbox.
- Select the events you want to send to Segment.
- Make sure your webhook is marked as Active and Click “Save”.
Below is a table of events that Pendo can send to Segment. These events will show up as tables in your warehouse, and as regular events in your other Destinations. Pendo will send through the
userId (in Pendo this is the
visitorId) if available.
|A new visitor was created|
|Visitor metadata was updated|
|Flag indicating GDPR status was updated|
|A new account was created|
|Account metadata was updated|
|A feature was clicked|
|A track event was received|
|A guide was seen|
|A poll was seen|
|A poll was submitted|
|A page was tagged|
|A page was updated|
|A page was deleted|
|A feature was tagged|
|A feature was update|
|A feature was deleted|
|A goal was created|
|A goal was updated|
|A goal was deleted|
|A goal status was changed|
|A NPS survey was seen|
|A NPS survey was submitted|
|A NPS survey was created|
|A NPS survey was updated|
|A NPS survey was deleted|
|A NPS survey status changed|
|A poll was created|
|A poll was updated|
|A poll was deleted|
|A path was created|
|A path was updated|
|A path was deleted|
|A funnel was created|
|A funnel was updated|
|A funnel was deleted|
|A user was invited|
|A user was added|
|A user was updated|
|A user was deleted|
These are the common properties for all Pendo events. The
properties section of each event contains the detailed information specific to that event type.
|Common Properties||Properties common to all event types|
|Value of the Visitor Id in Pendo|
|Collection of key/value data specific to each event|
Now that your Source is set up, you can connect it with Destinations.
Log into your downstream tools and check to see that your events are populating and they contains all the properties you expect. If all your events and properties are not showing up, refer to the Destination docs for troubleshooting.
If there are any issues with how the events are arriving to Segment, please contact the Pendo team.