Skip to contentSkip to navigationSkip to topbar
Page tools
Useful for sharing or LLM
Accelerate development with AI

On this page
Looking for more inspiration?Visit the

Pendo Audiences Destination


The Pendo Audiences destination allows you to sync Twilio Engage audiences to Pendo Segments. For more information, visit Pendo's documentation(link takes you to an external page).


How it works

how-it-works page anchor

When you create an audience in Engage and connect it to the Pendo Audiences destination, Segment automatically:

  1. Creates a new Segment in Pendo using the audience name.
  2. Adds visitors to the Pendo Segment when they enter the audience.
  3. Removes visitors from the Pendo Segment when they exit the audience.
(information)

Real-time to batch destination sync frequency

Real-time audience syncs may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.


Prerequisites

prerequisites page anchor

Before you begin, make sure you have:

  • A Pendo Integration Key, which you can find in Pendo under Settings > Integrations > Integration Keys.
  • An Engage Audience that you want to connect to this destination.

Connect Pendo Audiences to Segment Engage

connect-pendo-audiences-to-segment-engage page anchor
  1. In Segment, navigate to Engage > Engage Settings.
  2. Click Destinations, then Add Destination.
  3. Search for Pendo Audiences and select the Pendo Audiences destination.
  4. Click Add destination, then click Confirm Source.
  5. Under Basic Settings, enter:
  • A name for your destination (for example, "Pendo Audiences Prod").
  • Your Pendo Integration Key.
  1. Enable the destination and click Save.

Set up the Sync Audience Action

set-up-the-sync-audience-action page anchor
  1. Navigate to Connections > Destinations, search for the Pendo Audiences destination you created, and click on it.
  2. Navigate to Mappings > New Mapping and click the Sync Audience tile.
  3. Review the default field mappings. Segment automatically maps the Visitor ID field to $.userId. Update this if your Pendo visitors are identified by a different field.
  4. Click Save.
  5. On the Mappings tab, enable the Sync Audience action.

Connect Pendo Audiences to your Audience

connect-pendo-audiences-to-your-audience page anchor
  1. Navigate to Engage > Audiences and select the Audience you want to sync to Pendo.
  2. Click Add Destination and select the Pendo Audiences destination you created.
  3. Configure the per-audience settings:
  • Pendo Segment Name (optional): Override the name used when creating the Pendo Segment. By default, Segment maps this field to the Engage audience name.
  1. Click Save, then click Add 1 Destination. Your audience begins syncing to Pendo.

Which Segment event types does this destination support?

which-segment-event-types-does-this-destination-support page anchor

This destination processes Identify and Track calls emitted by Engage. Both are handled the same way — the payload is inspected to determine whether the visitor should be added to or removed from the Pendo Segment. If using Track, the event name is ignored.

Which field is used to identify visitors in Pendo?

which-field-is-used-to-identify-visitors-in-pendo page anchor

Segment maps Pendo's Visitor ID field to $.userId by default. This must match the visitor ID used in your Pendo installation. You can update the mapping in the Sync Audience action if your Pendo visitors are identified by a different field.

Can I override the Pendo Segment name per audience?

can-i-override-the-pendo-segment-name-per-audience page anchor

Yes. By default Segment uses the Engage audience name when creating the Pendo Segment. You can override this on a per-audience basis using the Pendo Segment Name field in the destination's settings.

Does this destination support batching?

does-this-destination-support-batching page anchor

Yes. By default, events are batched and synced to Pendo using the batch PATCH endpoint, with up to 1000 visitors per request. Batching is enabled by default and can be configured in the Sync Audience action mapping.