Skip to main content

How to Connect Zuora as a Data Source in Alta (Connectors)

Connect Zuora through the Connectors library so Alta syncs your accounts, subscriptions, and invoices to power revenue analytics, metrics, and Luna.

Written by Katie Supporté

Zuora runs subscription billing — accounts, subscriptions, rate plans, and invoices. Connecting it as a data source through the Connectors library syncs those tables into your Alta workspace, where they become training data for Alta and a foundation for your metrics, dashboards, and Luna analysis. Once it's flowing, you can measure ARR, renewals, and collections — and ask Luna questions in plain English. Zuora connects with credentials.

Who this is for: Finance and RevOps teams running subscription billing in Zuora who want that data measured across Alta.


Before you start

  • Create Zuora OAuth API credentials (client ID and client secret) and note your Zuora environment/endpoint (production vs sandbox, plus your data center).

  • Connect a source only once per workspace. If Zuora already shows Connected, edit the existing connection.

Connect Zuora

  1. Open Connectors from the sidebar.

  2. Find Zuora via the Billing tab or the Search data sources box.

  3. Click the Zuora card to open the Create connector screen.

  4. Fill in the connection fields shown (such as client ID, client secret, and endpoint), then click Create.

  5. Alta runs a connect test. If it fails you'll see The connect test has failed with Zuora's error — fix the field and retry.

  6. The card then shows Connected and Data is syncing until the first sync finishes.

Choose which tables sync

  1. Open the connection. Zuora brings in tables like accounts, subscriptions, rate plan charges, and invoices.

  2. Use the Synced toggle in the Zuora tables section to control what's pulled in.

  3. Turn off Show only synced tables to see everything available.

Key tables and fields synced

  • accountsId, Name, Currency, Status, BillCycleDay

  • subscriptionsId, Status, TermStartDate, TermEndDate, AutoRenew, AccountId

  • rate plan charges — the money detail: Id, Mrr, Tcv, ChargeName, EffectiveStartDate

  • invoicesId, Amount, Balance, Status, InvoiceDate, DueDate, AccountId

  • invoice items / payments — line-level billing and cash applied

What you can ask this data

Once it's syncing, build it into metrics and dashboards or just ask Luna / Ask AI. For example:

  • "What's total invoiced vs collected this quarter?" — compares invoices.Amount to paid balance.

  • "How many active subscriptions, and what's their ARR?" — sums Mrr × 12 on active subscriptions.

  • "What's our renewal rate?" — uses TermEndDate and AutoRenew / renewal subscriptions.

  • "Which accounts have outstanding balances?" — filters invoices.Balance > 0 by AccountId.

  • "How is MRR trending by month?" — trends rate-plan-charge Mrr over time.

Example use cases

  • Recurring-revenue dashboard. MRR/ARR, new vs. churned, and net retention from rate plan charges.

  • Renewals pipeline. Upcoming TermEndDates to forecast and manage renewals.

  • AR & collections. Outstanding invoice balances and aging by account.

  • Bookings-to-billings. Join Zuora to CRM deals to reconcile what was sold vs. billed.

Keep it in sync

  • Sync status shows Last sync (Succeeded/Failed) and the Sync frequency.

  • Click Sync now to refresh immediately; it's disabled while a sync runs.

  • Use the overflow menu () to Disable, Enable, or Delete.

Tips and common pitfalls

  • Match the environment. Pointing production credentials at the sandbox endpoint (or vice versa) is the most common cause of a failed connect test.

  • MRR lives on rate plan charges. Sync that table to measure recurring revenue accurately.

  • Sync only what you need to keep syncs fast.

  • Deleting is permanent. Disable instead to pause.


Related

Did this answer your question?