Connect Pendo to Rig

    Bring Pendo's product usage data into your warehouse, so feature adoption and guide engagement sit next to revenue, CRM and support data and can be queried together.

    Requirements
    A Pendo plan with API access, and a subscription admin who can create integration keys
    Time required
    10 mins

    Before you start

    • API access depends on your Pendo plan, and Pendo says so in its own API docs. If you are unsure whether you have it, ask your Pendo admin or account rep first.
    • Only a Pendo subscription admin with integration key access can create a key. If you are an admin and Integration Keys is missing from Settings, another admin or your Pendo rep has to switch it on for you.
    • Note the address you use to sign in to Pendo. It tells Rig which regional API to call.

    Pick a route

    If you already use Pendo Data Sync, Pendo is writing its tables straight into your Snowflake, BigQuery or Databricks warehouse. Rig reads those tables like any other part of your warehouse, so there is no key to create. Check that the schema Data Sync writes to is one your Rig workspace reads, and you are done.

    Everyone else connects with an integration key, which takes about ten minutes and is what the rest of this guide covers.

    Create an integration key

    1. Sign in to Pendo as a subscription admin.
    2. Go to Settings, then Integrations, then Integration Keys.
    3. Click Add Integration Key and give it a description you will recognise later, such as Rig.
    4. Leave Allow Write Access unticked. Rig only reads from Pendo, so a read-only key is all it needs.
    5. Click Create and copy the key straight away. Pendo shows it once and cannot recover it, so if you lose it, make a new one. There is no limit on how many keys you can create.

    The key covers your whole subscription
    An integration key belongs to the subscription rather than to a person, an app or an environment. It can read every app in your Pendo subscription, so store it like a password. It is also a different thing from the app key in your Pendo install snippet, which only identifies your app to Pendo.

    Find your region

    Pendo runs five separate regions, and the API lives at the same address you sign in at. Take the address from your browser when you are signed in to Pendo.

    You sign in atRegion
    https://app.pendo.ioUS
    https://us1.app.pendo.ioUS1
    https://app.eu.pendo.ioEU
    https://app.jpn.pendo.ioJapan
    https://app.au.pendo.ioAustralia

    Connect it in Rig

    Pendo does not have a ready-made card in Rig yet. You add it with Rig Bore, which reads Pendo's public API docs, tests your key against the live API and builds the connector while you watch.

    1. In Rig, open Connections and go to Sources & actions.
    2. Under Don't see your tool?, click Add a custom connector with Rig Bore.
    3. Platform URL: your Pendo sign-in address from the table above.
    4. When asked what Rig should be able to do, choose Read data into Rig.
    5. Paste the integration key into the credentials form.
    6. Rig tests the key and shows you what it can reach, object by object. Tick what you want to sync and save.

    The connector then appears under Built with Rig Bore and runs in your workspace straight away.

    If your workspace has no Rig Bore button, get in touch with your Pendo region and we will build the connector for you. Do not send us the key. We will tell you where to enter it once the connector is ready.

    What Rig can pull in

    Pendo's API covers both the things your team has tagged and set up in Pendo and the activity recorded against them. Rig Bore shows which of these your key can reach before anything syncs.

    • Pages, features and track events: the definitions your team has tagged in Pendo, with their names and the rules behind them.
    • Guides: every in-app guide, with its steps and status.
    • Visitors and accounts: the people and companies Pendo has seen, with the metadata your install sends, such as plan or account owner.
    • Activity: page views, feature clicks, track events and guide interactions over time, which Pendo serves through its aggregation queries.

    Good to know

    • Events take a few minutes to reach the API. Pendo accepts them straight away but processes them in the background, and says they are usually available within 15 minutes.
    • Your Pendo exclude list still applies. Events from domains you have excluded in Pendo, often staging or test sites, are left out of what the API returns.
    • One key reaches every app. If your subscription has a web app and a mobile app, both are in scope.
    • Data Sync stores dates as day counts. If you take the Data Sync route, the periodId column is the number of days since 1 January 1970 rather than a date. Convert it before comparing it to a date, for example with DATEADD(day, periodId, '1970-01-01') in Snowflake.
    • Pendo Feedback is a separate product with its own API key. This guide covers Pendo's product analytics and in-app guides.

    Troubleshooting

    • The key is rejected: Pendo answers with a 401 when it does not accept a key. Check the region as well as the key, because each region is its own service and a key only works at the address you sign in at.
    • There is no Integration Keys option in Settings: either your Pendo role is not subscription admin, or integration keys are not enabled for your subscription. Ask another admin or your Pendo rep.
    • You lost the key: Pendo cannot show it again. Create a new one, update it in Rig, then delete the old one in Pendo.
    • Pages or features arrive from only one app: the connector is asking Pendo about a single app. Get in touch and we will widen it to every app in your subscription.

    Was this guide helpful?