Stripe Attribution for Solo Founders: The Plug-In Playbook
You ship a feature on Monday. By Friday, two paid upgrades have landed in Stripe. You have no idea which channel, post, or page earned them. Most solo founders accept this. The fix takes an afternoon.
Stripe sees the charge. Your site (Next.js, Astro, Webflow — pick one) sees the visit. Resend or Loops sees the email. X sees the click. PostHog or Plausible sees the events.
Five tools, five slices of the truth. None of them join the data for you. The result: when MRR moves, you guess.
CRMs solve this for marketing teams with budgets. They are also $1,500 a month, take a week to set up, and assume you have a sales motion. Solo founders running freemium-to-paid funnels need something different — a thin attribution layer that plugs into the tools they already pay for.
Three properties:
- Every paid signup carries a first touch. The specific tweet, ad, blog post, or referral that earned them.
- Every step between first touch and conversion is on the same record. Email opens, page views, trial events, the Stripe upgrade.
- You can ask the data questions in English. "Which post drove last month's paid signups?" should be a 5-second query, not a half-day spreadsheet exercise.
If you have all three, you have attribution. If you don't, you have a dashboard.
Most teams remember UTMs for paid ads and forget them for organic posts. Don't. Tag every link from X, LinkedIn, your newsletter, and your blog with utm_source, utm_medium, and utm_campaign.
Use a consistent naming convention. x-thread-2026-05-04 is better than twitter-post. Naming sloppiness compounds; future-you will thank present-you for being explicit.
Don't trust session cookies. They get cleared. Don't trust document.referrer. It gets truncated half the time. When a user signs up, capture the UTM params on the server and store them in the user record (or a dedicated signups_attribution table if you want to keep auth clean).
If your stack is Next.js + Supabase + Stripe, this is one extra line in your signup handler:
await supabase.from('users').update({
utm_source: req.cookies.utm_source,
utm_medium: req.cookies.utm_medium,
utm_campaign: req.cookies.utm_campaign,
}).eq('id', userId);
(Set the cookie when the user first hits the site with a UTM. That's another 5 lines of middleware.)
When a user upgrades to paid, your Stripe webhook handler should update the user with paid_at, plan, and mrr_value. Now every paid user has a complete chain: first touch → activation events → Stripe upgrade.
case 'customer.subscription.created':
await supabase.from('users').update({
paid_at: new Date(),
plan: subscription.items.data[0].price.nickname,
mrr_value: subscription.items.data[0].price.unit_amount / 100,
}).eq('stripe_customer_id', subscription.customer);
break;
Email opens, email clicks, key page views (PostHog event), and trial actions all join the same user record on user_id. If you can't be bothered with PostHog, skip it for v1 — first touch + Stripe is 80% of the value.
Pipe the user table into a tool that lets you ask questions in plain English. FunnelFizz does this natively over its MCP server (mcp.funnelfizz.com) — point Claude or Cursor at it and ask "which X post drove last month's paid signups?" without writing SQL. A Claude project pointed at your warehouse can do a version of it too. The point: you should be 5 seconds from question to answer.
- Tagging paid ads but skipping organic. Then concluding organic doesn't work. It does — you can't see it.
- Using last-touch attribution. A user who saw the X thread, came back via Google three days later, and signed up gets credited to "google/organic." The thread gets nothing.
- Building a dashboard and stopping. Dashboards are not insights. The point is to act on the data.
- Skipping UTMs because "I'll add them later." Later never happens. Fix this first.
If you'd rather not write the wiring yourself, FunnelFizz connects your tracking script, Stripe, and your provider accounts (X, YouTube, LinkedIn, GSC, Google Ads, and more) into one attribution timeline. It also runs the email side natively — drag-and-drop MJML editor, dynamic recipient lists keyed to funnel stage, and automations as DAGs (Send / Wait / Split). Self-serve. FREE plan available; HOBBY and PRO unlock more. Built for solo founders and small SaaS teams running freemium funnels.
If you'd rather build the attribution layer yourself, the playbook above is what we'd build. Either way: stop guessing where your paying users came from.
Pick one: tag your next 5 outbound links with UTMs today, or sign up for FunnelFizz and let it instrument the chain for you. The worst outcome is another month of guessing.
