Real-time
Two-way sync
Changes in Pendo or Recurly instantly reflect in both systems. No stale data, no manual imports.
Analytics ⇄ Accounting and finance
Pendo to Recurly integration — real-time, two-way sync
Keep Pendo and Recurly in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Pendo and Recurly
Feed the customers, invoices, and revenue records in Recurly into Pendo in real time, so dashboards and reports run on current numbers instead of last night's export.
Recurly holds the financial truth: who the customers are, what they were invoiced, what they paid, and what revenue landed. Pendo is where that data is turned into dashboards, reports, and metrics, but it only reflects the world as of its last load. When the connection between them is a scheduled extract or a hand-built pipeline, analysis runs a step behind the books, and the numbers on a chart rarely match the numbers in the finance system.
Stacksync keeps Billing Info, Measured Units and Usage, Accounts, Subscriptions in Recurly in sync with Guide Events, Poll / NPS Responses, Features / Pages / Guides (metadata), Visitors in Pendo, field by field and in real time. A customer, invoice, or amount created or corrected in Recurly shows up in Pendo within seconds, mapped to the right record. Where Pendo keeps its own accounts or users, the flow runs both ways, so finance attributes can enrich what Pendo already tracks.
There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning's reporting running on yesterday's figures.
Common use cases
- 01 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
- 02 Sync Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.
- 03 Load guide-engagement events into a reporting database to measure onboarding-flow adoption against retention and expansion.
- 04 Export feature, page, and guide Events out of Pendo over event-time windows into Postgres or a warehouse so product usage joins with CRM, billing, and support data in SQL.
Common sync patterns
Reports refresh as the books change
Instead of waiting for a scheduled load, Pendo updates the moment a figure moves in Recurly, so a dashboard opened at any point in the day is current.
Where Pendo keeps account or user records: finance attributes enrich them
Status, plan, or outstanding balance from Recurly attaches to the matching account or user in Pendo, so segments and cohorts can be cut by real financial standing.
Financial records land in Pendo for reporting
Invoices, payments, and revenue from Recurly flow into Pendo as they change, so dashboards are built on live figures rather than a periodic extract.
What you can sync between Pendo and Recurly
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Pendo objects | Recurly objects | How this pairing syncs | |
|---|---|---|---|
| Accounts Company/workspace records that roll visitors up to an account dimension; readable via Aggregation and a write target for custom fields (plan, ARR, health) via the Metadata API. | Accounts Customer/billing entity records keyed by account_code; the anchor most subscriptions and invoices hang off. Synced two-way with CRM accounts or a customer database. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Feature Events Click/interaction events on tagged features, read-only through the Aggregation API over an event-time window and joined to the Feature definitions. | Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. | Feature Events is specific to Pendo and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side. | |
| Page Events Page-view events for tagged pages; read-only via the Aggregation API, used for adoption and path analysis in a warehouse. | Billing Info Tokenized payment method (card/ACH) on an account; written when onboarding customers and read for payment-health signals (never stores raw card numbers). | Page Events is specific to Pendo and Billing Info to Recurly — each maps to any object or custom field on the other side. | |
| Guide Events Guide seen/advanced/dismissed and step events for in-app walkthroughs; read-only through the Aggregation API to measure onboarding flow adoption. | Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. | Guide Events is specific to Pendo and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side. | |
| Poll / NPS Responses Survey answers and NPS scores captured in-app (pollEvents / npsEvents); read-only via the Aggregation API as voice-of-customer data. | Subscriptions Recurring subscription records tied to an Account and a Plan, with state, term, and next-bill date. Core object, synced two-way to drive provisioning and reporting. | Poll / NPS Responses is specific to Pendo and Subscriptions to Recurly — each maps to any object or custom field on the other side. | |
| Features / Pages / Guides (metadata) Definitions of tagged UI elements listed through the entity endpoints; read-only reference used to label and join the event streams. | Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. | Features / Pages / Guides (metadata) is specific to Pendo and Plans to Recurly — each maps to any object or custom field on the other side. |
How changes propagate between Pendo and Recurly
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Pendo Recurly Interval-based propagation
DetectionStacksync polls Pendo for changes on an incremental schedule, reading only records changed since the previous pass. Polling - reads query the Aggregation API over event-time windows.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
Recurly Pendo Sub-second propagation
DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.
DeliveryEach detected change is written to Pendo through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Pendo: Pendo does not publish fixed numeric limits; it throttles heavy Aggregation queries with 429s and caps/paginates large responses, so wide exports are paced and time-windowed.
- Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
What ships with Pendo ⇄ Recurly
Connect Pendo and Recurly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Pendo–Recurly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Pendo or Recurly data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Pendo or Recurly record.
Observability
Monitoring
Track your Pendo ⇄ Recurly sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Pendo and Recurly.
How the Pendo and Recurly connectors work
Pendo
- Integration surface
- Pendo Engage API (REST) on app.pendo.io (US) / app.eu.pendo.io (EU), base path /api/v1/ - Aggregation API for reads and the Metadata API for writes
- Authentication
- Integration key sent in the x-pendo-integration-key header, generated in Subscription Settings; keys are scoped read-only or read/write, so writes require a read/write key
- Change detection
- Polling - reads query the Aggregation API over event-time windows; no change-data-capture feed and no data-change webhooks. Writes go through the Metadata API on demand.
- Capabilities
- read · write
- Rate limits
- Pendo does not publish fixed numeric limits; it throttles heavy Aggregation queries with 429s and caps/paginates large responses, so wide exports are paced and time-windowed.
Recurly
- Integration surface
- REST API (V3, date-versioned; legacy V2 XML API also exists)
- Authentication
- API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
- Change detection
- Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
- Capabilities
- read · write · webhooks
- Rate limits
- Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
How it works
How to connect Pendo to Recurly — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Pendo and Recurly with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pendo
connected
Recurly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Pendo and Recurly objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Pendo ⇄ RecurlyCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Pendo RecurlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Pendo and Recurly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Pendo and Recurly: authenticate both systems, choose the objects to sync (such as Pendo's Accounts and Feature Events), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Pendo and Recurly records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Pendo and Recurly connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Pendo–Recurly integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Pendo and Recurly. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Pendo: Polling - reads query the Aggregation API over event-time windows; no change-data-capture feed and no data-change webhooks. Writes go through the Metadata API on demand. On Recurly: Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Recurly side: Billing Info, Measured Units and Usage, Accounts, Subscriptions, plus custom fields where Recurly exposes them. On the Pendo side: Guide Events, Poll / NPS Responses, Features / Pages / Guides (metadata), Visitors. Stacksync auto-detects both schemas and converts types between the two systems.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 473 integrations available for Pendo and Recurly.
Popular · 4 of 473
No integrations match .
