Skip to main content
Connect the system that owns the final payment record. Datalyr combines that revenue with customer activity; it should not replace your billing platform as the ledger.

Choose the source

Business modelRecommended sourceTypical data
Shopify storeShopifyOrders, customers, checkouts, cancellations, refunds
SaaS or web subscriptionStripePayments, subscriptions, invoices, refunds, disputes
Mobile subscriptionRevenueCat or SuperwallTrials, purchases, renewals, cancellations, billing failures
Whop businessWhopPurchases, subscriptions, cancellations
Checkout funnelCheckout ChampPurchases, rebills, refunds, chargebacks, cancellations

Connect revenue

1

Verify behavioral tracking

Confirm a visit or app event appears before connecting revenue. Attribution needs the activity that happened before payment.
2

Open Sources

Find the platform that owns the transaction and select Connect.
3

Complete its setup

Authorize the account or enter the credentials and webhook values requested in the connection dialog.
4

Create a test transaction

Use a sandbox or test mode where supported. Keep the transaction ID for comparison.
5

Inspect the result

Open Events, find the transaction, and check its amount, currency, customer, source, and transaction ID.

Use one owner per transaction

Do not send the same purchase from an integration, a webhook, and custom SDK code. Duplicate reporting can inflate revenue even when the event names differ. When two systems observe the same payment, choose the platform that creates the final charge. For example, use Stripe for a Stripe-hosted SaaS checkout and Shopify for a Shopify order.

Source guides

Shopify

Orders, refunds, customers, and storefront attribution.

Stripe

Payments, subscriptions, invoices, and visitor metadata.

Whop

Creator purchases and subscriptions.

CheckoutChamp

Funnel orders, upsells, rebills, refunds, and chargebacks.

RevenueCat

Mobile subscriptions and purchases.

Superwall

Paywall, trial, and subscription events.

What to verify

A correct transaction includes a unique transaction or order ID, numeric amount, ISO currency, source, timestamp, and a customer identifier when available. The customer journey should contain the landing visit before the purchase.

Ecommerce

Orders, customers, and store revenue.

Subscriptions

Trials, renewals, and cancellations.

Refunds

How returned money affects reporting.

Profit

Move from revenue to contribution profit.