Pendo Destination

Destination Info

• Accepts Group, and Identify calls.
• Referred to as Pendo in the Integrations object

Components

• Browser

Connection Modes

Device-mode	Cloud-mode
Web	Web
Mobile	Mobile
Server	Server

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.

Pendo maintains this destination. For any issues with the destination, contact the Pendo Support team.

Getting Started

Before you start, make sure Pendo supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.

1. From the Segment web app, click Catalog.
2. Search for “Pendo” in the Catalog, select it, and choose which of your sources to connect the destination to.
3. In the destination settings, enter your Pendo API Key which you can find in the Pendo UI under Site Settings > Basic Information > API Key.

Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading Pendo’s snippet on your page and sending data.

This pulls in all page and click events without needing to make additional method calls.

Cloud-mode configuration

To add the Pendo destination using Cloud-mode, use the Webhooks destination to enable Segment to send data to Pendo through a webhook.

1. From the Segment web app, click Catalog.
2. Search for Webhooks in the Catalog, select it, and choose which of your Javascript sources to connect the destination to.
3. Add the following as your Webhook URL: https://pendo-io.appspot.com/data/segmentio/YOUR_PENDO_API_KEY and replace YOUR_PENDO_API_KEY with your actual Pendo API Key which you can find in the Pendo UI under Site Settings > Basic Information > API Key.
4. Headers are not required in Webhook configuration. Once you’re done adding in your URL, save changes.
5. Using Track method also requires a setting enabled on your Pendo subscription. contact Pendo to enable this feature flag for your account.

To learn more about server-side data to Pendo, see Pendo’s support documentation.

Identify

If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like:

analytics.identify("userId1", {
  name: "Peter Gibbons",
  email: "peter@example.com",
  plan: "premium",
  logins: 5
});

When you send an Identify call, Segment passes that user’s information to Pendo with userId as Pendo’s visitor ID. User traits that you pass are mapped to visitor metadata in Pendo.

Group

If you’re not familiar with the Segment Specs, take a look to understand what the Group method does. An example call would look like:

analytics.group("0e8c78ea9d97a7b8185e8632", {
  name: "Initech",
  industry: "Technology",
  employees: 329,
  plan: "enterprise"
});

When you send a Group call, Segment sends groupId as the Pendo as account ID. Group traits are mapped to account metadata in Pendo. If you are using Pendo account data, group calls (fields groupId & traits) are required.

Track

If you’re not familiar with the Segment Specs, take a look to understand what the Track method does. An example call would look like:

analytics.track("Registered", {
  groupId: "0e8c78ea9d97a7b8185e8632",
  plan: "Pro Annual",
  accountType: "Facebook"
});

When you send a Track call, Segment sends it as a Pendo Track Event. Note that groupId is not included by default in a Track call, but it is highly recommended to add as a property.

Pendo maps groupId to an account ID. For more information on Pendo’s Track Events, check out their support documentation.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.