How to Build Revenue Analytics Across Stripe, QuickBooks, and Salesforce with CRM and Accounting APIs

March 4, 2026

Revenue analytics products need data from multiple systems to present an accurate picture of business performance.

Sales pipeline data typically lives in CRM platforms like Salesforce, billing and invoices are stored in accounting tools such as QuickBooks, and payments or subscriptions may be processed through Stripe.

For SaaS teams building revenue dashboards, RevOps tools, or financial analytics platforms, this fragmentation creates a difficult integration challenge. Each provider exposes different APIs, authentication models, and data schemas.

Unified simplifies this process by providing normalized APIs for CRM, payments, and accounting platforms. Instead of building separate integrations for Salesforce, Stripe, and QuickBooks, developers can retrieve and combine revenue data through consistent objects and endpoints.

Why SaaS Products Need Revenue Analytics

Revenue analytics features are common in many SaaS products, including:

• RevOps platforms
• Financial reporting tools
• SaaS metrics dashboards
• Customer success analytics products
• AI-driven revenue assistants

These tools rely on combining three different categories of data:

• Sales pipeline data from CRM systems
• Invoices and receivables from accounting platforms
• Transactions and subscriptions from payment processors

When these sources are connected, product teams can build dashboards that track the full lifecycle of revenue — from deal creation to invoice issuance to payment collection.

Common Revenue Analytics Use Cases

Revenue analytics dashboards typically support several key workflows.

Pipeline forecasting

Sales teams estimate future revenue using open opportunities and their probability of closing.

Billed revenue tracking

Finance teams monitor the total value of invoices issued to customers.

Cash collections monitoring

Revenue teams track payments received against outstanding invoices.

Recurring revenue metrics

Subscription products measure MRR, ARR, renewals, and churn.

Revenue attribution

Analytics platforms connect sales pipeline data with billing records to understand how deals convert into revenue.

Unified Categories Used in Revenue Analytics

A revenue analytics product usually pulls data from three Unified API categories.

Using these normalized categories allows developers to retrieve revenue data across many platforms without writing vendor-specific integrations.

Unified Objects and Key Fields

Unified standardizes the core objects required for revenue analytics.

These normalized fields allow analytics tools to calculate revenue metrics consistently across platforms.

Revenue Metrics and How They Map to Data

Once data from CRM, accounting, and payment systems is combined, several key revenue metrics can be calculated.

Pipeline value

Derived from open CRM deals.

weighted_pipeline = deal.amount * deal.probability

Billed revenue

Calculated from invoices issued to customers.

billed_revenue = sum(invoice.total_amount)

Cash collected

Based on payment transactions.

collections = sum(payment.total_amount)

Recurring revenue

Calculated from active subscriptions.

MRR = sum(active subscription monthly value)
ARR = MRR * 12

These metrics allow teams to compare pipeline forecasts with actual revenue and collections.

Connecting Customer Accounts

Customers authorize their systems using Unified Connect.

The authorization flow is consistent across CRM, payments, and accounting integrations.

Typical process:

1. Your application launches the Unified Connect authorization component.
2. The user selects integrations such as Salesforce, Stripe, or QuickBooks.
3. The user authorizes the selected platform.
4. The redirect URL includes a connection_id identifying the authorized account.

Your application stores the mapping:

user_id → connection_id

All future Unified API requests reference this connection identifier.

Retrieving CRM and Billing Data

Revenue analytics dashboards retrieve data from several Unified endpoints.

CRM endpoints

GET /crm/{connection_id}/deal
GET /crm/{connection_id}/contact
GET /crm/{connection_id}/company

These endpoints return normalized CRM records regardless of the underlying provider.

Accounting endpoints

GET /accounting/{connection_id}/invoice
GET /accounting/{connection_id}/contact

These endpoints retrieve invoices and accounting customer records.

Payments endpoints

GET /payment/{connection_id}/payment
GET /payment/{connection_id}/subscription

These endpoints provide payment transactions and recurring billing data.

Common filters used for analytics include:

• updated_gte — retrieve records updated after a specific timestamp
• contact_id — retrieve invoices or payments associated with a customer
• invoice_id — retrieve payments tied to a specific invoice

Using these filters allows applications to build efficient incremental sync pipelines.

Data Flow for Revenue Analytics

A typical revenue analytics pipeline follows this sequence.

1. Connect customer systems

Customers authorize Salesforce, Stripe, or QuickBooks through Unified Connect.

2. Perform an initial backfill

Retrieve deals, invoices, payments, and subscriptions using paginated list endpoints.

3. Store data locally

Save normalized objects in your application database or analytics warehouse.

4. Run incremental syncs

Use the updated_gte parameter to retrieve records updated since the last sync.

5. Subscribe to webhooks

Register webhook subscriptions for objects such as deals, invoices, and payments.

6. Update analytics metrics

Recalculate revenue metrics and update the dashboard.

This pattern keeps analytics data synchronized with customer systems.

Keeping Revenue Data Updated

Unified supports webhook events that notify applications when records change.

Webhook subscriptions specify:

• the object type (for example crm.deal, accounting.invoice, or payment.payment)
• event types such as created or updated
• a callback URL

Unified supports two event delivery models:

Native webhooks

Immediate push notifications when supported by the provider.

Virtual webhooks

Managed polling that simulates real-time events when native webhooks are unavailable.

These events allow analytics dashboards to react immediately to changes such as:

• deal stage updates
• invoice payments
• subscription renewals or cancellations

Supported CRM and Billing Platforms

Unified supports a broad set of integrations across CRM, payments, and accounting platforms.

CRM platforms (47+ integrations)

Examples include:

• Salesforce
• HubSpot
• Pipedrive
• Zoho CRM
• Microsoft Dynamics 365
• Copper
• Close
• Freshsales
• Insightly

Payment platforms (16+ integrations)

Examples include:

• Stripe
• PayPal
• Square
• Chargebee
• GoCardless

Accounting platforms (41+ integrations)

Examples include:

• QuickBooks
• Xero
• Zoho Books
• Sage Accounting

This allows revenue analytics products to support many customer environments without building separate connectors.

Why Product Teams Choose Unified

Building revenue analytics features across CRM, accounting, and payment systems usually requires dozens of integrations.

Unified simplifies this by providing:

• normalized data models across CRM, payments, and accounting categories
• consistent API endpoints for reading and writing data
• unified authorization flows across integrations
• webhook events that work across providers
• support for custom fields and provider-specific data

Instead of maintaining complex integration infrastructure, product teams can focus on building revenue analytics features and delivering insights to their users.

Start building revenue analytics across Stripe, QuickBooks, Salesforce, and dozens of other platforms today.

→ Start your 30-day free trial

→ Book a demo