Zentrik

Zentrik + Pendo

Bring product sentiment and account context into Discovery without turning every Pendo event into noise.

Admins save one workspace credential in Settings → Integrations.

Zentrik uses a Pendo Integration Key to read selected guide and poll context, NPS responses, comments, and account identities. Historical records can remain account context while only useful comments become Discovery signals.

The connection is read-only toward Pendo. Signal creation is opt-in and can be limited to an explicit guide or poll scope.

Connect Pendo

  1. In Pendo, open Settings → Integrations → Integration Keys and copy an Integration Key. Do not use the application key from the install snippet.
  2. In Zentrik, open Settings → Integrations → Pendo.
  3. Choose the Pendo region that owns the subscription.
  4. Paste the Integration Key and save. Zentrik validates the key server-to-server and never exposes it in the browser again.

Import and match

  1. Choose the guide or poll scope that contains the responses you want to review.
  2. Import a bounded historical window.
  3. Review NPS scores and comments before enabling signal creation.
  4. Preview account identities and apply only exact, unique matches to Zentrik accounts.
  5. Keep unmatched or ambiguous identities unresolved until the account mapping is clear.

Use comments as signals when they contain customer evidence. Score-only events can remain NPS history without entering the qualitative Discovery corpus.

Periodic imports

Periodic Pendo imports require an explicit guide or poll filter. This prevents a workspace-wide event stream from silently flooding Discovery. Confirm the saved scope and account rules before enabling the shared daily import cadence.

Data and access

  • Zentrik reads Pendo through the selected regional API endpoint.
  • The Integration Key remains server-side.
  • Zentrik does not write changes back to Pendo.
  • Disconnecting stops future reads; previously imported NPS records and Discovery signals remain until removed through normal product controls.

Troubleshooting

Check credentials and permissions on both sides first. If you have verified everything and it still fails, contact us with your workspace name and what you tried.

The key shows Needs validation

Re-enter the key, confirm the selected Pendo region, and save again. Existing valid credentials are not replaced by a failed reconnect.

A guide or poll is missing

Confirm the key can access that Pendo subscription and that the selected region is correct.

Account matches are ambiguous

Do not apply them in bulk. Tighten the identity rule or resolve the affected Pendo identities to Zentrik accounts explicitly.