Which Marketing Channel Produces Your Paying Customers?

A founder on r/SaaS put the problem plainly: "Do you actually know which marketing channel produces your paying customers?" The post attracted responses from dozens of SaaS operators, and the honest answer from most was no — or not reliably. They could see which channel produced trial signups. They could not see which channel produced customers who stayed and paid.

This is a traceability problem, not an attribution model problem. Most discussions about improving marketing analytics jump straight to model selection — should we use first-touch, U-shaped, or data-driven? But model selection is irrelevant when the underlying data cannot reconstruct the journey from marketing touchpoint to paid conversion. Fixing traceability is always the higher-value intervention. This post is a practical diagnostic for identifying where your setup breaks down.

Why channel-to-revenue traceability is harder than it looks

Three distinct failure modes compound each other in most SaaS attribution setups. The first is UTM inconsistency: paid ad campaigns are tagged, but email sends, LinkedIn organic posts, partner newsletters, and event sponsor placements are not. Every untagged source inflates the 'direct' bucket in your analytics tool and makes paid channels look more efficient than they are, because the comparison pool is padded with traffic that actually came from other sources.

The second failure mode is cross-device identity loss. A B2B buyer clicks a LinkedIn ad on their phone during a commute, does comparison research on their work desktop, and signs up for a trial from a bookmarked link. The trial signup session shows as 'direct' even though LinkedIn drove the initial intent. Without cross-device identity resolution — which requires either a login event before the signup or probabilistic matching — mobile-initiated journeys are systematically misattributed. The cookieless attribution accuracy benchmarks show that cross-device gap alone can account for 20-35% of 'direct' traffic in B2B SaaS with high mobile research behaviour.

The third failure mode is the trial-to-paid delay. Most analytics setups capture the acquisition source at trial signup. But in SaaS, trial-to-paid conversion happens days or weeks later — sometimes after the original session attribution has aged out of the analytics window, and often in a different session classified as 'direct' because the user navigated directly to the pricing page. If your analytics tool treats trial signup and paid conversion as separate events with no user-level join, you are measuring which channel produces trials, not which channel produces customers.

The four diagnostic questions to run first

Before auditing your attribution model, answer these four questions about your tracking setup. They reveal which of the three failure modes is dominant in your data.

Question one: What percentage of new trial signups are classified as 'direct' or '(not set)' in your analytics tool over the past 90 days? Pull this number. If it exceeds 25%, UTM inconsistency or cross-device loss is significant. Genuinely direct traffic — users who type your URL directly or use a bookmark on the same device — rarely exceeds 15-20% for a SaaS product actively running paid acquisition. Anything above that is likely mismapped attribution, not actual direct intent.

Question two: Do your analytics tool and your CRM agree on the acquisition source for individual trial signups? Pick 20 recent signups and compare the source field in both systems. If they agree for fewer than 80%, you have a data pipeline problem — either the source parameter is not being passed through the signup form, or the CRM is overwriting it with a different source on first contact. The analytics data quality audit has a cross-system reconciliation checklist for this check.

Question three: Can you produce a cohort of paying customers joined to their trial signup event, with acquisition source on both? This is the minimum for channel-to-revenue traceability. If your data model does not have this join — if paid conversions are tracked as separate events from trial signups with no shared user identifier — you are not measuring channel ROI, you are measuring channel trial volume.

Question four: Do your ad platform spend numbers and your analytics attributed revenue numbers directionally agree by channel? If LinkedIn shows 15% of your ad spend but your analytics tool gives it 2% of attributed revenue, one of three things is true: LinkedIn's conversion tracking is overcounting, your analytics tool is undercounting LinkedIn (likely cross-device loss), or LinkedIn genuinely delivers poor ROI despite high impression volume. You need to know which — and the way to find out is to instrument a post-signup survey asking new customers how they first heard about you, then compare self-reported channel data to your tracked attribution.

The UTM audit: what to check and what to fix

UTM coverage is the easiest failure mode to fix and the one most teams ignore longest because it requires operational discipline rather than technical implementation. The audit takes about an hour.

Pull every traffic source in your analytics tool that drove more than 50 sessions in the past 90 days. For each source marked 'direct', look for clustering by date. A spike in 'direct' signups on the same day as an email send is almost always an untagged email. A sustained lift in 'direct' traffic following a press mention is almost always an untagged earned media hit. A burst of 'direct' sessions on the day of an event or webinar is that audience navigating directly from their memory of your brand — which should be tagged via UTMs on your event confirmation and follow-up emails.

Build a channel tagging matrix: a spreadsheet listing every outbound marketing activity (paid ads, email sequences, newsletter sponsorships, podcast appearances, partner co-marketing, event placements) with a column for whether UTMs are applied. Any row without UTMs is a leak. For ongoing paid activity, enforce UTMs in your ad platform campaign naming convention. For episodic activity like newsletters and events, add UTM generation to the production checklist. The event taxonomy and tracking plan guide covers how to standardise UTM conventions across a team so different people do not create contradictory channel names.

The trial-to-paid join: making revenue data attributable

The technical problem with trial-to-paid attribution is that most SaaS setups use separate event systems for product analytics (which captures the trial signup and the acquisition source) and billing (which captures the paid conversion). Joining them requires a persistent user identifier present in both systems — typically the email address or a user ID that is passed to the billing system at the point of trial signup.

If your billing system (Stripe, Paddle, Chargebee) receives the user ID from your product at trial creation, you can build a join at the data warehouse level: trial signup events keyed on user ID, matched to payment events keyed on the same user ID, with the acquisition source from the signup event carried through to the payment cohort. This is the minimal viable join for channel-to-revenue traceability.

If the join does not exist yet, the fastest interim approach is to run it manually for a sample of paying customers. Export your paying customer list for the past 90 days, look up each customer's acquisition source in your analytics tool or CRM, and build a simple channel-to-revenue table. This gives you a directional read on which channels actually produce paying customers without requiring infrastructure changes. It also tells you whether the answer differs significantly from what your trial-signup attribution data suggests — if high-signup channels are low on the paying-customer list, you have a qualification problem, not an attribution problem. The CRM and revenue data join problem post covers the infrastructure side of this in more depth.

When traceability is good enough: what you can now answer

Traceability is good enough when you can consistently answer three questions: Which channels produced paying customers in the past 90 days (by channel, by count, and by revenue)? What is the trial-to-paid conversion rate by acquisition channel (not just overall)? And are there channels producing high trial volume but low paid conversion that are distorting your overall funnel metrics?

The third question is often the most valuable and the most ignored. It is common to find that one channel — usually a high-volume, low-cost channel like SEO or content — produces a large share of trials but a disproportionately small share of paying customers, because the traffic intent doesn't match the product's ICP. Running budget allocation decisions on trial volume without the paid conversion layer systematically overinvests in intent-mismatched channels.

Once you can answer these three questions reliably, attribution model selection becomes a tractable problem rather than an exercise in building on sand. The multi-touch attribution model selection guide covers which model fits which funnel shape — but it only produces useful outputs when the underlying traceability is sound.

The self-reported channel survey: your calibration check

No analytics setup captures everything. Cross-device journeys, dark social, podcast mentions, word-of-mouth, and analyst recommendations leave no UTM trail. The only way to measure these channels is to ask customers directly. A single-question post-signup survey — "How did you first hear about us?" with a short multiple-choice list — run for 30 days gives you a calibration dataset against which to compare your tracked attribution.

The delta between self-reported data and tracked attribution reveals which channels are systematically undercounted in your tool. If 'a colleague recommended it' accounts for 30% of self-reported responses but 0% of your tracked attribution, word-of-mouth is a major source that your model is assigning to 'direct'. If podcast mentions appear frequently in self-reports but not in your attribution data, those campaigns are untagged or driving untrackable direct traffic. This calibration exercise does not fix your tracking, but it tells you how much your tracking is missing and in which direction the bias runs — which is the starting point for deciding whether infrastructure investment is justified.

Moving to model selection only after traceability is verified

The sequence matters. Traceability audit first. UTM coverage fix second. Trial-to-paid join third. Only then does it make sense to think about first-touch versus multi-touch versus data-driven attribution — because only then do you have the data quality that makes model outputs meaningful.

Teams that skip to model selection without traceability verification typically see one of two failure modes: confident attribution dashboards built on 40% UTM coverage that overstate paid channel performance, or attribution models that agree with each other because the 'direct' bucket is so large that any model has the same black hole to fill. In both cases, the output is decorative, not actionable. Solving traceability is less intellectually interesting than debating attribution models, but it consistently has a larger impact on measurement quality. Fix the data first, then optimise the model. The dark funnel attribution gap post covers what remains unmeasurable even after traceability is maximised — and how to account for it without overclaiming.