Subscription LTV attribution: credit every renewal to its channel

Subscription LTV attribution credits every renewal, upgrade and refund on a subscription to the channel that won the customer. A $49 plan that renews for 12 months produces $588, and a first-invoice report credits the channel with $49 of it.

In Stripe the fix takes one join and one rule: tie the first charge to a click, then let every later invoice on the same subscription ID inherit that channel.

What the first invoice leaves out

Assume a customer pays the same price every month and each month carries the same chance of ending the subscription.

Lifetime revenue is then the price divided by the monthly churn rate, the arithmetic Paddle's CLV guide gives as average revenue per user divided by churn.

The first invoice is one month of that lifetime, so its share equals the churn rate.

Take two channels that both deliver $49 on the first invoice, with newsletter readers churning at 3% a month and cold paid social at 8%. A first-invoice report calls them equal.

Over a lifetime the newsletter customer is worth $1,633 and the paid-social customer $612.50, a 2.7x gap. Both churn rates are assumptions.

Real churn is not constant.

David Skok's SaaS metrics essay uses cohort analysis to check whether a business loses most of its customers in the first couple of months, so use actual paid invoices for any cohort old enough to have them.

How subscription LTV attribution works in Stripe

Four links connect an ad click to the ninth invoice of a subscription. Each lives in a different system, and a break at any one of them orphans every invoice after it.

The first two links are identity problems. If the visitor ID never reaches Stripe Checkout, nothing downstream can recover the channel, and Stripe metadata attribution setup covers the write side.

When you start from a charge, as a refund event does, links 3 and 4 depend on your Stripe API version.

Stripe's subscription webhook documentation moves the subscription ID at 2025-03-31.basil, and a handler written for one version reads an empty field on the other.

You can also stamp the source on the subscription once. Stripe's metadata guide says each invoice a subscription creates gets a one-time snapshot of its metadata under parent.subscription_details.metadata, so every invoice.paid event carries the channel without a lookup.

Fixing a typo after month 3 leaves invoices 1 to 3 as they were.

Stripe events that change a channel's lifetime revenue

Stripe retries a failed live-mode webhook delivery for up to 3 days with exponential backoff, so key each revenue row by invoice ID and a replayed event changes nothing.

Three ways to credit renewals

A customer who pays $49 for 12 months produces $588, and the credit rule decides how much of it the winning channel books: all of it, 70% of it, or a forecast made on day one.

Carry the first credit forward

The channel that won the customer keeps all 12 invoices, $588 on a $49 plan, which answers which channel pays your MRR directly and costs one lookup per invoice.

It over-credits acquisition when a lifecycle email sequence or an onboarding call is what keeps people subscribed. I would start here and add complexity only when a budget decision demands it.

Decay the credit over time

A decay rule gives the acquisition channel a falling share and moves the remainder to a retention bucket.

With 100% for months 1 to 3, 80% for months 4 to 6, 60% for months 7 to 9 and 40% for months 10 to 12, a $49 plan credits the channel 49 x (3 x 1.0 + 3 x 0.8 + 3 x 0.6 + 3 x 0.4) = $411.60 of the $588 paid that year, or 70%.

The schedule is arbitrary and earns its place only when someone owns retention spend.

Book a projected lifetime value at signup

Forecasting books expected lifetime revenue to the channel at the first payment: $980 for a $49 plan at 5% churn. A team can judge a campaign in its first week instead of its twelfth month.

The cost is a churn estimate per channel, and an estimate from a 3-month-old cohort is mostly noise, so keep actual paid revenue beside the projection.

Upgrades, refunds and trials

Take a newsletter subscriber on the $49 plan who upgrades to $99 at the month 6 renewal, cancels after month 9 and gets the last invoice refunded.

The newsletter ends with $542 credited, and the opening $49 is 9% of it. First-invoice attribution would hold $49 and never see the upgrade or the refund.

A mid-cycle upgrade lands differently.

Stripe's proration documentation works through a customer who upgrades from a $10 plan to $20 halfway through the period: a $5 credit for unused time plus $10 for the rest of the period on the new plan, so $5 more is billed.

The default create_prorations creates those items without invoicing them at once, so they usually land on the next invoice. Expansion revenue then arrives one cycle late, and a daily MRR chart disagrees with an invoice-based table until it is paid.

Upgrades made through the billing portal are covered in Stripe Customer Portal attribution.

Trials and the attribution window

A free-trial subscription sits in trialing status and becomes active when the first payment arrives, so there is nothing to credit before then. The click that won the customer happened before the trial began.

A 14-day trial and a visitor who clicked 20 days before signing up put the first charge 34 days after the click, outside a 30-day window. That charge receives no channel, and every renewal after it inherits none either.

Set the window to cover the trial plus a normal consideration period.

Comparing channels by lifetime value

All-time revenue per customer rewards age. Compare cohorts of equal age, or fix one window, such as the first 6 months, and apply it to every channel.

Plan mix distorts the comparison too.

ChartMogul's SaaS Retention Report, covering more than 2,100 SaaS businesses, found net revenue retention above 100% at 2.7% of companies with ARPA under $10 a month and at 41.1% of those with ARPA over $500.

A channel that sells your top plan will retain better for reasons unrelated to the channel, so split by plan before crediting the channel with the difference.

TrackRev's attribution benchmarks, built from Q2 2026 workspace data, report a median 12-month LTV multiplier of 2.1x for organic search and 0.8x for paid social, measured against each workspace's average customer, with a median of 12.4 months to first churn for organic search against 6.2 for paid social.

Lifetime revenue becomes a budget signal once it meets cost.

Paddle puts the SaaS benchmark for CLV to CAC above 3:1, and Skok adds that many of the best businesses recover CAC in 5 to 7 months, with profitability turning anemic past 12.

Paid social recovers its cost a month sooner and still fails the 3:1 test, while the newsletter passes it and takes a month longer.

What TrackRev does with a renewal

TrackRev reads Stripe with a read-only restricted key and syncs charges hourly, with instant syncs from a Stripe webhook when the key allows it.

The first charge for a subscription finds its visitor from metadata.vid, then the Checkout Session's client_reference_id, then the buyer's email.

It earns credit from clicks inside the attribution window under your model: last touch (the default), first touch or linear, as the attribution model comparison lays out. The window defaults to 30 days and accepts 1 to 365.

Every later charge whose invoice carries the same subscription ID copies the first order's channel and link split, rescaled to the renewal amount. A $49 plan that becomes $99 credits $99 to the same channel from then on.

The same carry-forward runs for Paddle, Polar and Lemon Squeezy subscriptions, keyed on each provider's own subscription ID.

A Stripe charge reported as refunded drops out of the lifetime table, and a partly refunded charge loses its whole credit instead of only the refunded portion.

The Channels page lists customers, orders including renewals, lifetime revenue and average LTV per customer for each channel, as described on the channel analytics page. It sums all time with no cohort-age cut, so apply the comparison rules above.

Revenue figures need a paid plan: Starter at $39 a month, Growth at $99 or Scale at $199 (pricing). The free plan tracks links only. Setup steps are on the Stripe integration page.

A renewal whose first order earned no credit earns none either, and the first sync reaches back 30 days, so subscriptions that began before you connected arrive without their original click. Changing the attribution model affects new orders only.

Cases the join can't see

An invoice a sales rep sends by hand has no browser session behind it, so no visitor gets credit. Billing in Chargebee or Recurly sits outside the four processors TrackRev reads: Stripe, Paddle, Polar and Lemon Squeezy.

For those deals a CRM field holding the source is the better record. The click-to-charge walkthrough is in attributing Stripe revenue to marketing channels.