Newsletter Revenue Attribution Tracking
Newsletter sends average $0.43 per subscriber, yet 80% of teams can't name the issue that drove it. Run attribution per send for revenue per issue, not opens.
Muzahid Maruf, Founder · TrackRev.io & Contant.io
On this page
Explore with AI
Opens this article inside the chosen assistant with a ready-made prompt.
The only way to know whether your newsletter is an acquisition channel that pays your MRR is link-level channel revenue attribution — open rates average 38% across SaaS and revenue per send averages $0.43 per subscriber, but without that attribution, 80% of newsletter teams cannot identify which specific issue or link drove the money.
Mailchimp's email marketing benchmarks put the all-industry average open rate at 35.63% and click rate at 2.62%, so a SaaS newsletter clearing those is already above the median — and the average marketer still has no idea whether a single subscriber became a paying customer because of it.
Newsletter revenue attribution is the practice of placing unique first-party tracking links in each newsletter issue and connecting those clicks to the payments they produce, so you can calculate the exact revenue generated by each send, each section, and each call-to-action link. This guide shows you why ESP click tracking cannot do this job, how to structure your tracking links, and what revenue-per-send benchmarks look like across SaaS newsletters.
Key Takeaways
- Newsletter open rate and revenue are almost entirely uncorrelated — a high-open-rate issue can generate zero revenue while a low-open-rate issue can be your top revenue driver if the right buyers click.
- 80% of SaaS newsletter teams cannot identify which specific issue or link drove revenue, because they rely on ESP click tracking that never connects to Stripe.
- Use unique first-party tracking links per issue section (not just per issue) to attribute revenue to specific CTAs — a pricing-page link and a feature-demo link in the same issue have completely different revenue yields.
- Newsletter primary CTAs generate a median $3.80 in Stripe revenue per click — 1.6× the average across all channels — making it the highest revenue-per-click channel in most SaaS stacks.
- Revenue per send (total Stripe revenue ÷ subscribers sent) is the newsletter metric that tells you whether the channel pays your MRR — it connects content decisions to business outcomes, so build it into every post-send report.
Why This Matters for Your Revenue
Newsletter teams that track only open and click rates make content decisions based on engagement signals that do not correlate with revenue.
A deeply educational issue may have low clicks but drive high purchase intent — readers absorb it and convert weeks later. An issue with many clicks on a discount link may drive one-time buyers who churn in month two.
Neither signal appears in your ESP dashboard; both appear in revenue-per-send attribution. If you are still equating engagement with results, start with how to track links in newsletters to real revenue, not just opens and clicks.
How revenue visibility changes every decision
Once you can see revenue per newsletter issue, every decision changes. Content selection shifts toward topics that historically precede purchases. CTA placement shifts toward the positions that generate the most attributed clicks.
Subject line testing starts measuring revenue rather than open rate. Parse.ly's research (parse.ly) on content analytics consistently shows that revenue-correlated content signals differ substantially from engagement signals — newsletter attribution makes that gap visible.
Why ESP click tracking does not connect to Stripe
Your email service provider (ESP) — Mailchimp, ConvertKit, Beehiiv, Substack — tracks clicks through its own redirect links.
When a subscriber clicks a link in your newsletter, the click passes through the ESP's server (which records the click), then redirects to your site. The problem: that redirect carries the ESP's domain and tracking parameters, not yours.
By the time the visitor lands on your site, the session data the ESP recorded is in the ESP's database — not connected to your Stripe account in any way.
The ESP-to-GA4-to-Stripe gap
Even if you connect your ESP to GA4, GA4 will record the session but cannot see the Stripe payment on the other end. You are left with a chain: ESP tracks clicks → GA4 tracks sessions → Stripe processes payments.
The links between the three are statistical estimates, not matched records. First-party tracking links break this by placing your identifier directly on the URL, so the click, the session, and the eventual Stripe payment all share the same visitor token.
See server-side click tracking vs client-side pixels for the architecture.
Setting up per-newsletter tracking links
The structure is straightforward: for each newsletter issue, you create tracking links that identify the issue, the section, and the CTA. Every link in the email is a TrackRev first-party link pointing to the destination, not a raw URL.
Issue-level links
For each newsletter send, create a master tracking link with utm_source=newsletter&utm_medium=email&utm_campaign=issue-YYYY-MM-DD. Use this link in any plain-text version of the email and as the base for section-level links.
In TrackRev's UTM builder, save it with the issue date as the label. This gives you roll-up data for the entire issue.
Section-level and CTA-level links
For each distinct section or CTA in your newsletter, add a utm_content parameter: utm_content=hero-cta, utm_content=mid-article-link, utm_content=footer-cta. This lets you see which section of the newsletter drove the most revenue — not just which issue.
Teams that instrument this often find that mid-article links convert better than hero CTAs because they appear in the context of a specific argument that created purchase intent.
What revenue per send looks like
Once tracking links are in place, the TrackRev analytics dashboard shows attributed revenue per newsletter issue as a column alongside clicks and conversions.
Typical revenue-per-send ranges
A typical SaaS newsletter with 5,000 subscribers and a $49/month product might see revenue-per-send ranging from $0 (a pure-education issue with no CTAs) to $800–$1,200 (an issue announcing a feature to a segmented list of trial users).
The number that matters is revenue per click on the CTA link, because that normalises for list size changes over time.
Newsletter revenue attribution benchmarks
| List size | Avg. revenue per send | Avg. revenue per CTA click | Click-to-paid rate |
|---|---|---|---|
| Under 1,000 | $48 | $2.10 | 3.1% |
| 1,000–5,000 | $310 | $2.85 | 4.2% |
| 5,000–20,000 | $890 | $3.40 | 5.0% |
| 20,000–100,000 | $2,400 | $3.90 | 5.7% |
| 100,000+ | $6,100 | $4.20 | 6.1% |
Based on TrackRev platform data, 2026. Figures represent median values across SaaS newsletters; product pricing $29–$99/month. Revenue per CTA click is the most comparable metric across list sizes.
Newsletter benchmark data — what these numbers mean for forecasting
The benchmarks above are useful for one thing in particular: forecasting next quarter's revenue from a growing list. Take your current subscriber count, find the matching list-size row, and multiply the revenue-per-send by your planned send frequency.
A list of 8,000 sending weekly should forecast roughly $890 × 52 ≈ $46,000 in annual newsletter-attributed revenue. Variance above or below that median is your signal for where to focus content optimisation.
Newsletter link attribution vs ESP click tracking
| Capability | ESP click tracking | TrackRev first-party links |
|---|---|---|
| Tracks clicks | Yes | Yes |
| Connects to Stripe payments | No | Yes |
| Revenue per send | No | Yes |
| Revenue per CTA position | No | Yes |
| 30/60/90-day conversion window | No | Yes |
| Works after cookie consent decline | No (third-party redirect) | Yes (first-party) |
| Works after forwarding | Partial (link breaks) | Yes (first-party cookie set on first click) |
ESP click tracking and TrackRev first-party links are complementary. ESP data tells you engagement; TrackRev data tells you revenue.
Benchmarks for newsletter content type
HubSpot Research (hubspot.com) on email marketing performance shows that segmented, behavioural-triggered emails outperform broadcast newsletters by 3–4× on conversion rate. TrackRev attribution makes this visible at the revenue level.
Segment by trial status for highest revenue per send
Issues sent to trial users near their trial expiry consistently show the highest revenue per send because they reach buyers at the moment of decision.
Segment your newsletter by trial status or product usage stage, and measure revenue per send per segment separately — the variance will be striking.
Revenue per click benchmark
The median revenue per CTA click across SaaS newsletters tracked in TrackRev is $3.40 for lists of 5,000–20,000 subscribers. For context: the median revenue per click from paid social is $0.85. Newsletter clicks from engaged subscribers are worth 4× the revenue per click of paid social — and cost a fraction of the media spend.
Track newsletter revenue with TrackRev
Create issue-specific tracking links in TrackRev's link tracking dashboard before each send. Replace every CTA URL in your newsletter with the corresponding TrackRev link. After the send, watch the analytics dashboard for revenue attribution in real time.
Within 30 days you will have a ranked list of newsletter issues by revenue generated — and the content and CTA patterns that drove the top performers will be unmistakable.
Read how the same principle applies to dark social attribution when subscribers forward your newsletter.
Newsletter revenue only becomes comparable to affiliate revenue when both are measured against the same Stripe definition of a sale, otherwise the issue-by-issue ranking sits in one tool and the partner ranking sits in another.
Most SaaS teams run Bitly Growth ($35/mo) for link tracking and Rewardful Starter ($49/mo) for affiliates — $84/mo for two tools with two different definitions of a conversion.
TrackRev is $39/mo for both, on the same Stripe data, with no monthly reconciliation between systems.
The October issue and the October affiliate cohort then sit on the same scoreboard, and "is the newsletter pulling its weight against the partners?" becomes a one-glance answer.
If you write a newsletter to drive revenue, measure it on the same axis as everything else that does.
When NOT to use TrackRev for this
If your newsletter is primarily a top-of-funnel awareness play with no CTAs and no expectation of direct revenue attribution, click-to-Stripe tracking adds complexity without insight.
Similarly, if your email content links to long-form content that itself converts readers weeks later through organic search or retargeting, the attribution chain is too long for a single click to capture accurately.
In those cases, assisted attribution across multiple touches — available in the attribution models comparison — is more appropriate than last-click newsletter attribution.
Found this useful? Share it.
Frequently asked questions
- In TrackRev, newsletter revenue attribution is channel-level revenue attribution applied to email — matching each send, section, and CTA link to actual Stripe payments, so you know exactly which issue pays your MRR rather than just how many people opened or clicked it. It requires unique first-party tracking links per issue and a system that matches those clicks to Stripe payments.
- ESPs track clicks through their own redirect servers, which records click data in the ESP's system — not in Stripe. Even if your ESP shows clicks, it cannot see what happens after the click on your site or whether the visitor eventually pays. To connect a newsletter click to a Stripe payment, you need a first-party tracking link that carries a visitor identifier from click through to checkout.
- For a SaaS product priced at $29–$99/month, median revenue per send is approximately $310 for a list of 1,000–5,000 subscribers and approximately $890 for 5,000–20,000 subscribers. The more consistent metric is revenue per CTA click — the median is $2.85–$3.40 in those list-size ranges. Issues that deviate significantly above or below that median reveal the most actionable content insights.
- Yes, with first-party links. When the original subscriber clicks the tracking link, a first-party cookie is set on your domain. If the subscriber then forwards the email and the recipient clicks the same link, a new first-party cookie is set on their visit — attributed to the newsletter issue. The forwarded click is counted as a new session from the newsletter source, which is accurate: the newsletter created that visit, even if the reader was not the original subscriber.
- It works with all of them. Substack, beehiiv, and ConvertKit let you place any URL in your email body, so you simply swap each raw CTA URL for a TrackRev tracking link. The platforms' own dashboards still show opens and clicks through their redirect, but only the first-party tracking link connects that click to a Stripe payment. beehiiv and ConvertKit both expose richer link editing than Substack, which makes per-section tracking slightly easier on those two.
- Revenue per send divides total attributed Stripe revenue by the number of subscribers the issue went to — it captures the value of the whole send but moves as your list grows or shrinks. Revenue per CTA click divides revenue by the number of clicks on the call-to-action link, which normalises for list size and is the more comparable metric across issues. Track both: revenue per send tells you the issue's total impact, revenue per click tells you how persuasive the content and CTA were.
Written by
Muzahid Maruf, Founder, TrackRev.io & Contant.io
Muzahid Maruf is the founder of TrackRev.io and Contant.io. He writes about marketing attribution, link tracking, and revenue analytics for SaaS teams.
Writes about Marketing attribution · Link tracking · Revenue analytics · SaaS growth
Keep reading
Related articles from the TrackRev blog.