This article explains how Pendo integrates with Segment. - a platform that collects, stores, and routes your user data.
If you were looking for information related to segmenting your users in Pendo but ended up here, you’ll want to click here.
Segment makes it easy to send your data to Pendo (and lots of other integrations). Once you’ve tracked your data through Segment’s open source libraries, they’ll translate and route your data to Pendo in the correct format.
How it works
When Segment’s snippet is installed on your site, it will automatically initialize Pendo with your API key. You do not have to paste the Pendo installation snippet into Segment, the integration is already configured to send data to Pendo if you enable it.
This effectively replaces the default Pendo installation method outlined here.
How to Setup
Pendo supports the
track specs. Follow the setup instructions based on what specs you would like to use:
Identify & Group
From the Segment Destinations page, click on Pendo and include your Pendo API key.
Track & Server Side Data
Pendo track method supports server-side data. If you would like to use server-side data with track or any spec, add both Pendo and Webhook destinations within Segment:
YOUR_PENDO_API_KEY with your actual Pendo API Key.
Headers are not required in webhook configuration. Once you’re done adding in your URL, save changes.
To learn more about server-side data to Pendo, check out support documentation.
After your Segment Destination(s) setup is completed, Segment will automatically initialize Pendo using the API key on
Analytics.js load. This pulls in all page and click events without needing to make additional method calls.
identify spec lets you tie a user (or visitor) to their actions and record traits about them. When you
identify a user, Segment will pass that user’s information to Pendo with
userId as Pendo’s visitor ID. User traits are mapped to visitor metadata in Pendo.
Read more on Segment’s Identify spec here.
group spec allows you associate an individual user with a ‘group’ of users. Pendo associates a ‘group’ with an account. So, when you call when you call
group, Segment will send
groupId as the account ID to Pendo. Group traits are mapped to account metadata in Pendo. Therefore, group calls (fields
traits) are required if you use Pendo account data.
Read more on Segment’s Group spec here.
track spec is how you record any actions your users perform, along with any properties that describe the action. When you call
track, we will send it as a Pendo Track Event. For more information on Pendo’s Track Events, check out the Track Event Help Article.