Attribution — Marketing ROI by Channel Without GA4
Add one script tag. It captures UTM, referrer, and landing page. When a lead or a sale happens, your dashboard shows exactly which channel earned it. No GA4, no teams of consultants.
You can't optimize spend
on a gut feeling.
Clicks lie, revenue doesn't
Every channel can show clicks. Very few can show revenue. Attribution pairs the visit with the lead or sale that happened later. Every marketing channel can show you clicks; attribution shows you which can show you revenue.
Enterprise tools oversold it
Tag-manager setup, multi-touch models, consultant billings. This inverts the trade-off: one script tag, first-touch, a 30/90-day window — simple numbers, fast decisions.
The evidence changes the war
When organic and newsletter drive revenue while paid social eats budget, you reallocate. When a channel you wrote off is quietly converting, you reinvest. That's marketing on evidence, not hope.
From script tag to
revenue by source.
First-touch attribution, deliberately simple — which makes the numbers defensible and the decisions fast.
One script tag. It just works.
Paste the pixel into your site head — or a tag manager if you have one. From that second, every visitor's UTM parameters, referring site, and landing page are captured and stored per visit.
<script src="https://www.launchatdawn.com/api/attribution/pixel.js?uid=YOUR_UID" async></script>
Then trigger the sale on your thank-you page or Stripe webhook — the visit, channel, and landing page are already attributed.
Fire an event on conversion.
One fetch on your thank-you page, form handler, or Stripe webhook. Say whether it's a lead or a sale and, for sales, what it's worth — the visit data is already waiting server-side.
fetch('/api/attribution/event', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({
event_type: 'sale',
value: 49,
uid: 'YOUR_UID'
})
})From Stripe it's the same call inside a webhook handler — the sale attaches to whatever visit started that customer's journey.
See which channel earned it.
The dashboard rolls visits → leads → sales → revenue by source, with a 30/90-day window and per-user isolation. Reallocate the budget the data points to.
| Source | Visits | Leads | Sales | Revenue |
|---|---|---|---|---|
| 1,240 | 86 | 12 | $588 | |
| 610 | 41 | 3 | $147 | |
| Newsletter | 180 | 22 | 9 | $441 |
Know where revenue
comes from.
Automatic UTM capture
Pixel reads the whole URL — utm_source, utm_medium, utm_campaign stored with the visit.
Channel rollup
Google, Facebook, newsletter, direct — aggregated into one clean table automatically.
Revenue by channel
Attach a dollar value to each sale and see real ROI per source, last 30/90 days.
Stripe ready
POST /api/attribution/event from your webhook — value and channel attributed on the spot.
Lead events
Track leads (form fills) separately from sales, so you can see funnel quality.
No GA4 needed
Zero tag-manager config, zero dashboards to build. One tag and you're data-rich.
Per-user isolated
attribution_events are RLS-isolated to your login. Nothing cross-contaminates.
1-line install
Script tag + a fetch on conversion. Replace YOUR_UID from your own user id.
Separate SaaS
Own /attribution dashboard, pixel, and billing — isolated from Launch at Dawn core.
Attribution tools
- • Dashboard: visits → leads → sales → revenue by source
- • Get-pixel page with copy-paste script + event snippet
- • Test events so you can validate before going live
- • 30d default, 90d max via ?days=90
Integrations
- • Stripe — webhook → POST /api/attribution/event
- • UTM builder (planned) and CSV export (planned)
- • Zapier/Make — fire events from any form
- • Auto-sale detection from Stripe webhooks (next)
From launch-day channels
to full-funnel ROI.
SaaS & product sites
Track which content, ads, and referrals land in paid accounts — tie Stripe webhooks straight to revenue.
Agencies
Attribution per client means clean reporting on channel performance — proof of ROI, not activity.
Local & service businesses
See whether Google Business Profile, ads, or the newsletter drove the phone calls and bookings this month.
Attribution also completes the visibility story. Visible content, citations, and AI referral traffic should end in revenue you can measure — and when it does, you know exactly which of your SEO ROI metrics actually mattered. The pixel works alongside GA4, so the analytics stack stays undisturbed while you gain a clean revenue view.
Attribution,
answered.
Is it first-touch or last-touch?
First-touch by default — the channel that introduced the visitor. Simple and defensible for small budgets.
How do I attribute Stripe sales?
POST event_type="sale" with the value from your webhook. Channel comes from the stored visit for that user.
Does it work alongside GA4?
Yes. Many run it as the single source of truth for ROI while GA4 stays for behavior.
Do I need to sign in?
Yes — events and the dashboard are per-user. The pixel uses your own user id as the UID.
Does it capture all my UTM parameters?
Yes — the pixel reads the full URL, so utm_source, utm_medium, utm_campaign, and any custom values are stored with the visit and rolled up by channel.
What if a visitor comes from multiple channels?
First-touch attribution credits the channel that introduced them. It's the least gameable model and the right fit for lean budgets before you need multi-touch.
How do I know it's working?
Use the test event flow before going live — confirm a visit appears, then confirm the sale event attaches to the same channel in the dashboard.
Can I run it for multiple businesses?
Yes. Every user is isolated via RLS, so an agency can track each client's pixel and events without any cross-contamination.
One tag.
Proof of every dollar.
Add the pixel, fire events on conversion, and see which channel actually earned the sale.