Skip to main content

Pendo Feeds

Pendo is a product experience and digital adoption platform that captures product usage analytics, in-app guides, and user feedback to help teams understand and improve how customers engage with their applications. The Pendo Feeds connector is a source-only ELT connector that extracts Pendo product usage data — including visitors, accounts, features, pages, guides, events, and related metadata — using Pendo's Aggregation and REST APIs. Select the objects you want to ingest, and Nexla loads each one as its own feed on a schedule using either an incremental (auto-increment) or full-refresh strategy depending on the object.

Pendo Feeds icon

Power end-to-end data operations for your Pendo Feeds API with Nexla. Our bi-directional Pendo Feeds connector is purpose-built for Pendo Feeds, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Pendo Feeds or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Pendo Feeds workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

The Pendo Feeds connector authenticates with an Integration Key (also called an API Key), which Pendo passes in the x-pendo-integration-key request header. Before creating a credential in Nexla, generate an integration key in Pendo and confirm the region-specific domain URL for your subscription.

Generate a Pendo integration key​

  1. Sign in to your Pendo subscription with an account that can manage integrations.

  2. Navigate to Settings > Integrations > Integration Keys.

  3. Use an existing key, or click to create a new integration key. When creating a key, give it a descriptive name (for example, Nexla Integration) so you can identify its purpose later.

  4. Copy the integration key value and store it securely.

A Pendo integration key is not tied to a specific user account or application — it grants programmatic access to all applications in your subscription and does not expire by default. Treat it like a password and keep it secret. This key is different from the application (snippet) key used in your Pendo install script.

Confirm your Pendo domain URL​

Your Pendo domain URL corresponds to the region and web address you use when logging in to the Pendo UI. Note which of the following applies to your subscription so you can select it when creating the credential:

  • https://app.pendo.io (default)
  • https://app.eu.pendo.io (EU)
  • https://us1.app.pendo.io (US1)
  • https://app.jpn.pendo.io (Japan)
  • https://app.au.pendo.io (Australia)

For more information, see the Pendo integration keys guide and the Pendo API reference.

Authenticate​

Credentials required​

Authenticate with Pendo using an Integration Key (API Key).

FieldRequiredSecretDescription
Pendo Domain URLYesNoThe main URL used to access the Pendo API corresponds to the region and web address that you use when logging into Pendo's UI. Allowed values: https://app.pendo.io; https://app.eu.pendo.io; https://us1.app.pendo.io; https://app.jpn.pendo.io; https://app.au.pendo.io
Pendo API KeyYesYesYour Pendo Integration Key used for API access.

Create a credential in Nexla​

  1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. Use them to identify the Pendo subscription, region, or access level represented by this credential.

  3. Select your Pendo Domain URL from the list of allowed values. This must match the region and web address you use to log in to Pendo, because it determines the base URL Nexla uses for all Pendo API requests.

  4. Enter your Pendo Integration Key in the Pendo API Key field. Nexla sends this value in the x-pendo-integration-key header when authenticating and ingesting feeds, and stores it securely as a secret.

  5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation and can be selected for use with Pendo Feeds flows.

Use as a data source​

How This Connector Works​

The Pendo Feeds connector is a source-only, multi-feed ELT connector. Rather than configuring one endpoint at a time, you select the Pendo objects you want from a single catalog of feeds, and Nexla ingests each selected object as its own feed.

  • Discovery: When you create the source, Nexla discovers the objects (feeds) available from your Pendo subscription and presents them for selection.

  • Sync strategy per object: Each feed uses one of two ingestion strategies. Auto-increment feeds track a cursor and fetch only new or changed records since the previous run, and are the default. Full-ingest feeds read the complete current set of records on every run.

  • Parallel ingestion: Selected feeds are ingested on the same schedule so a single source can pull many Pendo objects together.

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, click the New Data Flow button, select the ELT flow type, and click Create.

  2. Select the Pendo Feeds connector tile from the list of available connectors. Then, select the credential that will be used to connect to your Pendo subscription and click Next; or, create a new Pendo Feeds credential for use in this flow. The credential controls the Pendo domain URL, so use the credential that matches your subscription's region.

Select the Objects to Ingest​

After authenticating, Nexla lists the Pendo objects available from the connector. Select one or more of the following objects to ingest. Each selected object becomes its own feed.

The following objects are ingested with a full-refresh strategy, reading the complete current list on every run:

  • Features — Tagged features across your applications.
  • Pages — Tagged pages across your applications.
  • Guides — In-app guides configured in Pendo.
  • Segments — Saved visitor and account segments.
  • Reports — Saved Pendo reports.

The following objects are ingested with the default auto-increment (incremental) strategy, fetching new or changed records since the previous run:

  • Applications — Applications in your Pendo subscription.
  • Groups — Pendo groups.
  • Visitors — Visitor records, keyed by visitorId.
  • Accounts — Account records, keyed by accountId.
  • Page History — Historical page metadata changes.
  • Feature History — Historical feature metadata changes.
  • Guide History — Historical guide metadata changes.
  • Track Type History — Historical track type metadata changes.
  • Page Events — Aggregated page view events.
  • Feature Events — Aggregated feature usage events.
  • Guide Events — Guide interaction events.
  • Poll Events — Poll response events.
  • Track Events — Custom track events.

Event and history feeds are read from the Pendo Aggregation API. The Lookback Time: Hours setting controls how many hours of event data each incremental run reconsiders (default 2). If you experience timeouts when backfilling historical data, set this to 0 or a low integer.

Schedule and Activate​

Use the default sync schedule or adjust the schedule in the source settings before activating the flow. On each run, auto-increment feeds fetch records changed since the previous run, and full-ingest feeds read the complete current set of records.

Once the source has been configured, click the Test button to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving. Then, click the Create button in the upper right corner of the screen to save and create the new Pendo Feeds data source. Nexla will begin ingesting the selected feeds and will organize any data that it finds into one or more Nexsets.

Reference​

For object schemas, field definitions, and additional detail on each Pendo endpoint, see the Pendo API reference and the Pendo ETL API examples.