Pendo Web (Actions) Destination
Pendo combines powerful software usage analytics with in-app guidance and user feedback capabilities, enabling even non-technical teams to deliver better product experiences to their customers or employees.
Pendo maintains this destination. For issues with the Pendo Web (Actions) destination, please reach out to Pendo's support team.
Success!
Good to know: This page is about the Actions-framework Pendo Web (Actions) Segment destination. There's also a page about the non-Actions Pendo destination. Both of these destinations receives data from Segment.
Pendo Web (Actions) provides the following benefits over the classic Pendo destination:
- Support for Track, Identify, and Group calls. The classic Pendo destination did not support Track calls and required users to configure an additional Webhook destination.
- Full region support. Setup allows the destination to be configured for US, EU, US restricted, or Japan.
- Supports CNAME for Pendo. Works with subscriptions using Pendo's custom CNAME feature.
- From the Segment web app, click Catalog, then click Destinations.
- Find the Destinations Actions item in the left navigation, and click it.
- Click Pendo Web (Actions).
- Click Add destination ->.
- Select an existing Source to connect to Pendo Web (Actions).
- In the destination settings, enter your Pendo API Key, which a Pendo Admin can find in the Pendo UI by going to Settings > Subscription Settings > Applications, opening the relevant app, then locating the API Key value.
- Select the correct region for your Pendo subscription.
Pendo API Key
Optional
If you are using Pendo's CNAME feature, this will update your Pendo install snippet with your content host.
Optional
Override sending Segment's group id for Pendo's account id. This will prevent Pendo from initializing with the group id from Segment (analytics.group().id()). Allowing you to adjust the mapping of account id in Segment's group event.
Optional
Override sending Segment's user traits on load. This will prevent Pendo from initializing with the user traits from Segment (analytics.user().traits()). Allowing you to adjust the mapping of visitor metadata in Segment's identify event.
The region for your Pendo subscription.
Pendo Web (Actions) has the following presets
| Preset Name | Trigger | Default Action |
|---|---|---|
| Send Identify Event | Event type = "identify" | Send Identify Event |
| Send Track Event | Event type = "track" | Send Track Event |
| Send Group Event | Event type = "group" | Send Group Event |
Build your own Mappings. Combine supported triggers with the following Pendo Web-supported actions:
Mapping limits per destination
Send Segment group() events to Pendo
Send Group Event is a Web action. The default Trigger is type="group"
Pendo Visitor ID. Maps to Segment userId
Pendo Account ID. Maps to Segment groupId. Note: If you plan to change this, enable the setting "Use custom Segment group trait for Pendo account id"
Optional
Additional Account data to send
Optional
Additional Parent Account data to send. Note: Contact Pendo to request enablement of Parent Account feature.
Send Segment identify() events to Pendo
Send Identify Event is a Web action. The default Trigger is type="identify"
Pendo Visitor ID. Maps to Segment userId
Optional
Additional Visitor data to send
Optional
Pendo Account ID. Maps to Segment groupId. Note: If you plan to change this, enable the setting "Use custom Segment group trait for Pendo account id"
Send Segment track() events to Pendo
Send Track Event is a Web action. The default Trigger is type="track"
The name of the analytics event
Optional
Additional metadata to include in the event
Remove the classic Pendo destination and Webhook destination from your Segment workspace before adding the Pendo Web (Actions) destination.