|
| 1 | +--- |
| 2 | +title: Pendo Audiences Destination |
| 3 | +slug: actions-pendo-audiences |
| 4 | +--- |
| 5 | + |
| 6 | +The Pendo Audiences destination allows you to sync Segment Engage audiences to Pendo Segments. For more information, visit [Pendo's documentation](https://support.pendo.io/hc/en-us/articles/360031862532-Segments){:target="_blank"}. |
| 7 | + |
| 8 | +## How it works |
| 9 | + |
| 10 | +When you create an audience in Engage and connect it to the Pendo Audiences destination, Segment automatically: |
| 11 | + |
| 12 | +1. Creates a new Segment in Pendo using the audience name. |
| 13 | +2. Adds visitors to the Pendo Segment when they enter the audience. |
| 14 | +3. Removes visitors from the Pendo Segment when they exit the audience. |
| 15 | + |
| 16 | +{% include content/sync-frequency-note.md %} |
| 17 | + |
| 18 | +## Getting started |
| 19 | + |
| 20 | +### Prerequisites |
| 21 | + |
| 22 | +Before you begin, make sure you have: |
| 23 | + |
| 24 | +* A Pendo **Integration Key**, which you can find in Pendo under **Settings > Integrations > Integration Keys**. |
| 25 | +* An [Engage Audience](/docs/engage/audiences/) that you want to connect to this destination. |
| 26 | + |
| 27 | +### Connect Pendo Audiences to Segment Engage |
| 28 | + |
| 29 | +1. In Segment, go to **Engage > Engage Settings**. |
| 30 | +2. Click **Destinations**, then click **Add Destination**. |
| 31 | +3. Search for **Pendo Audiences** and click on it. |
| 32 | +4. Click **Add destination**, then click **Confirm Source**. |
| 33 | +5. Under **Basic Settings**, enter: |
| 34 | + - A name for your destination (for example, "Pendo Audiences Prod"). |
| 35 | + - Your Pendo **Integration Key**. |
| 36 | +6. Enable the destination and click **Save**. |
| 37 | + |
| 38 | +### Set up the Sync Audience Action |
| 39 | + |
| 40 | +7. Navigate to **Connections > Destinations**, search for the **Pendo Audiences** destination you created, and click on it. |
| 41 | +8. Navigate to **Mappings > New Mapping** and click the **Sync Audience** tile. |
| 42 | +9. Review the default field mappings. The **Visitor ID** field maps to `$.userId` by default. Update this if your Pendo visitors are identified by a different field. |
| 43 | +10. Click **Save**. |
| 44 | +11. On the Mappings tab, enable the **Sync Audience** action. |
| 45 | + |
| 46 | +### Connect Pendo Audiences to your Audience |
| 47 | + |
| 48 | +12. Navigate to **Engage > Audiences** and select the Audience you want to sync to Pendo. |
| 49 | +13. Click **Add Destination** and select the **Pendo Audiences** destination you created. |
| 50 | +14. Configure the per-audience settings: |
| 51 | + - **Pendo Segment Name** (optional): Override the name used when creating the Pendo Segment. By default, the Segment audience name is used. |
| 52 | +15. Click **Save**, then click **Add 1 Destination**. Your audience will begin syncing to Pendo. |
| 53 | + |
| 54 | +## FAQs |
| 55 | + |
| 56 | +### Which Segment event types does this destination support? |
| 57 | + |
| 58 | +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. |
| 59 | + |
| 60 | +### Which field is used to identify visitors in Pendo? |
| 61 | + |
| 62 | +The **Visitor ID** field maps 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. |
| 63 | + |
| 64 | +### Can I override the Pendo Segment name per audience? |
| 65 | + |
| 66 | +Yes. By default the Segment audience name is used when creating the Pendo Segment. You can override this on a per-audience basis using the **Pendo Segment Name** field in the audience destination settings. |
| 67 | + |
| 68 | +### Does this destination support batching? |
| 69 | + |
| 70 | +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. |
0 commit comments