Use case
Follow SaaS acquisition beyond the signup.
DATALYR helps SaaS teams connect marketing visits with product activity and billing outcomes. Trace the journey from a first session to activation and payment, then evaluate acquisition with a consistent definition of customer, revenue and observation period.
Compare plans and usage
Cheap signups can become expensive customers.
An acquisition campaign may generate accounts that never activate or pay. Another may look slower while bringing customers who retain. Reporting only the signup hides that distinction. SaaS measurement needs a deliberate event path and an identity connection between anonymous visits, authenticated users and the billing system.
In DATALYR
SaaS Marketing Attribution
Activation context
Define the product action that indicates a user received value. Comparing signup and activation behavior can reveal where campaign promises attract the wrong audience or onboarding loses otherwise relevant users.
Payment evidence
Connect supported billing events instead of treating a pricing-page visit or trial as revenue. Keep subscription state separate from collected cash when discussing recurring revenue and acquisition performance.
Cohort discipline
Compare customers acquired over consistent periods and give them equal time to pay. This prevents a recently launched campaign from looking weak simply because its trials have not finished yet.
The workflow
From setup to a useful answer.
Define your funnel
Choose a short sequence such as visit, account creation, activation and payment. Write down what each event means and which system owns it before collecting extra activity that will not change a decision.
Connect identity and billing
Identify the signed-in user consistently and preserve the visitor reference in the billing handoff. Verify one real journey so the account and payment are linked to recorded acquisition evidence.
Compare business outcomes
Review conversion through each stage and reconcile payment totals with the billing source. Use the same attribution model and time window across campaigns, while retaining unattributed customers in the business total.
Verify the result
Know what good looks like.
- One user can be followed from an acquisition visit to activation.
- The paid-customer definition excludes free accounts and unpaid trials.
- Campaign comparisons use matching cohort and attribution windows.
Go deeper
Use the guide for context, then follow the implementation reference for your setup.
A few practical questions.
Should trial starts be the main success metric?
They can be a useful early indicator, especially while waiting for paid outcomes. Keep them separate from acquired paying customers and check whether trial cohorts actually convert before reallocating a budget.
Does attribution prove a campaign caused payment?
No. Attribution assigns recorded credit under a model. Causal impact requires a suitable experiment or other causal evidence; a payment appearing after a touchpoint is not proof of incrementality.
Explore related workflows.
- Stripe Revenue Attribution ↗
Connect Stripe payments and subscriptions to marketing visits with DATALYR. Preserve checkout identity and separate collected revenue from subscription state.
- Web app funnel analytics ↗
Connect acquisition, signup, activation and payment events in DATALYR to analyze a web app funnel.
- Subscription revenue attribution ↗
Connect supported subscription revenue sources to DATALYR and distinguish first payments, renewals and refunds in your acquisition analysis.