How to Separate First Sales and Renewals in Subscription Revenue Attribution

What Should Subscription Revenue Attribution Tell You?

Start with the decision you need to make. “Which channel brought new paying customers?” and “Which sources received credit for this month’s payments?” are both useful questions. They need different totals. Combining them can make a mature subscription business look as though it acquired the same customers again each month.

My recommendation is to show first paid sales beside later subscription payments in the weekly marketing review. Use the combined amount for the period-payment question, with refunds visible. Use billing or finance reports for subscription health and reconciliation. Do not ask one dashboard number to answer every question.

If your immediate problem is a trial that converts weeks after signup, first verify the trial-to-payment handoff. This guide starts after that: how to report the first sale and subsequent payments without confusing recurring value with fresh acquisition.

How Can Renewals Make Acquisition Look Better Than It Is?

Suppose a period contains $1,000 in verified first payments, $4,000 in later subscription payments and $200 in refunds, all on the same USD amount basis. Payments before refunds are $5,000. Payments less refunds are $4,800. Later payments account for 80% of positive payment value.

Calling the full $4,800 “new customer revenue” would overstate what the acquisition report establishes. Calling the later $4,000 irrelevant would also hide useful value. Keep both amounts, but name them correctly. Allocate the $200 refund deduction to first or later payments only when the underlying records establish where it belongs.

A $1,200 annual payment adds another trap: receiving it in November does not make it $1,200 of monthly recurring revenue. Stripe’s Billing analytics guide defines recurring metrics and reporting separately. Keep the billing definition when discussing MRR rather than dividing or relabeling a payment total ad hoc.

The same distinction matters for ROAS. Revenue credited under an attribution rule is not proof that this period’s advertising created every renewal. If you compare attributed payment value with ad spend, state whether the numerator includes existing subscribers and keep the spend dates explicit.

Which Subscription Events Does Attriboo Record?

Attriboo records supported provider payment events and stores types such as subscription new, subscription renewal and refund. Those are integration classifications. They are not a universal lifecycle model or a guarantee that a customer has never paid you before.

Stripe documents separate invoice reasons for creation, cycles, updates and thresholds. Polar’s order reference also lists its billing reasons, including metered cycles. These provider distinctions explain why you should inspect the original record rather than assume every charge in a renewal bucket is an unchanged monthly subscription.

Lemon Squeezy’s invoice reference distinguishes initial, renewal and updated invoices. Paddle’s transaction-origin explanation separates recurring renewals, immediate subscription changes and one-time subscription charges. Attriboo’s broader buckets should be reconciled against that detail when expansion revenue matters.

How Do Later Payments Stay Connected to Marketing?

The first useful connection is between a recorded website visitor and the receiving provider’s customer or checkout record. Later billing events can then resolve through the known provider customer, a supported reference or previously identified email. Matching is scoped to the website and provider; it does not create visits that were never recorded.

1. Confirm the script or plugin is installed on the correct published website and that Attriboo receives a visit.
2. Open Setup → Connect your payment provider and connect the account or store that receives the subscription payments.
3. Check one existing authorized first payment and one later payment from the same subscription, where available. Compare the provider IDs, currency, amount basis, date and stored type.
4. Confirm the payments have the intended visitor/customer connection. Leave unresolved records unmatched rather than assigning a convenient campaign.
5. Open the Sources report with fixed reporting dates, attribution rule and lookback window. Describe the output as recorded credit under those settings.

For a standard Stripe hosted link, verify the supported visitor reference survives checkout. A server-created checkout or an existing business reference needs its documented matching route. Do not replace a working order identifier simply to populate an attribution field.

Keeping the customer connection does not permanently freeze every later payment to the original acquisition channel. Attribution rules and lookback settings determine eligible recorded credit. If you need a fixed acquisition cohort, preserve the group and acquisition-source definition separately. A later email click near an automatic renewal is not evidence that the email caused the renewal.

Where Do You Check Payment Types and Refunds?

Open Dashboard, select View all under the summary’s number cards, then use Revenue & payments → Payments & refunds. Read the provider and stored payment type beneath each buyer label. Keep the website, actual date range, reporting time zone and attribution settings visible while reconciling the rows.

Download CSV exports the current report rows. Check whether a search is active before using an export as a complete ledger. The screen’s New comparison label describes a prior-period comparison, not customer acquisition. For a substantial reconciliation, use authorized provider exports or the documented sales report alongside this view; keep customer details private.

For another useful check, go to Where customers come from → Revenue sources and choose Repeat & LTV. It offers new/repeat order and 30/60/90-day value views. These use available recorded customer history and source credit; they are not the same as provider subscription billing reasons. Verify identity, history coverage and the underlying payment rows before using them as an acquisition-cohort comparison.

The chart combines recorded sales, refund deductions and net revenue. It does not present a native first-payment-versus-renewal cohort breakdown. Journeys has a different purpose: Linked purchase value excludes renewals and refunds. Use it to inspect eligible new-purchase paths, not to reconcile the full subscription payment total.

What Can Historical Imports and Refunds Change?

The native Stripe, Polar, Lemon Squeezy and Paddle Billing connections have bounded recent-history imports based on the last 90 days, with provider-specific pagination limits. This is payment import coverage, not a promise of complete customer history. Importing a payment cannot reconstruct the marketing visits or checkout reference that were missing when it happened.

Refund history also differs. Stripe’s recent-history importer reads paid checkouts and invoices, not historical refund events. Polar and Lemon Squeezy can derive refund deductions from imported order or invoice information. Paddle imports supported approved adjustments within its bounded history. Reconcile actual imported records before comparing totals across providers.

For one supported connection, compare the original positive payment and its refund deduction instead of deleting the original payment from your working report. Partial refunds, dates and cumulative refund updates need particular attention. A refund processed this month can relate to a sale from an earlier month, so a negative period net can be valid.

Keep currency groups and amount definitions separate. The current Stripe flow uses paid amounts; the merchant-of-record integrations discussed here use amounts before tax. Fees, tax treatment, bank settlement and recognized accounting revenue are not interchangeable. Let finance choose the accounting basis and use the payment-connection guide for your provider’s supported scope.

Build a Clear Subscription Reporting Summary

Choose the question your report must answer and enter reconciled amounts from one scope. The worksheet shows first payments, later payments, refunds and the later-payment share. It does not inspect your account, identify customers or infer missing classifications.

For a period review, enter all included first and later subscription payments within your stated dates. For a fixed-cohort review, include only payments belonging to that customer group and keep its observation window explicit. For acquisition, verify the first paid sale and allocate its refunds before describing a net first-sale amount.

Finish the review with one decision and one unresolved check. For example: “Later subscription charges account for most payment value, so we will review first paid sales before increasing acquisition spend. Finance will reconcile whether the refund deductions belong to new or existing subscribers.” That is more useful than an unlabeled revenue total.

Common questions