Explore

Analytics

The Two Things Every Vibe-Coded Launch Needs: Email Signup and Analytics That Tell You Who Came (and From Where)

Before you post your vibe-coded app anywhere, add two things: an email signup that saves, and analytics that alert you when people use it and show traffic by source. GA4 vs PostHog, set up in an afternoon.

Published 2026-11-11.

Score your launch page freeRead the blog

You can launch without a logo, a pricing page, or a company. You can't really launch without these two things:

  1. An email signup that actually saves the address, so a visitor who isn't ready today can still hear from you.
  2. Analytics that tell you when someone uses it and where they came from, so you know which post, directory or friend sent them.

Without the first, every visitor who leaves is gone. Without the second, you can't tell which of your launch posts worked, so you can't do more of it. Everything else can come later.

This post covers what to set up, Google Analytics 4 vs PostHog for a solo builder, and how to get a ping on your phone the moment someone signs up. (If you want the signup-testing detail, our analytics and signup alerts guide goes deeper on proving the pipeline works.)

Why these two, and not ten

When builders argue on X about whose launch "worked," the fair answer is always the same: show the number. In September, @shadrac_matata asked people to settle traffic arguments with Cloudflare, GA4 or PostHog instead of vibes. In November, @yusukelp polled other builders on what they use to track a site, and the replies split between GA4, PostHog and Search Console.

That's the point. A launch is a handful of experiments: a Reddit post, a Product Hunt listing, a directory, a DM to a friend. Analytics by source is how you find out which one did anything. The email list is how you get a second chance with everyone it brought.

1. Email signup: make it save, then make it say something

Most vibe-coded landing pages have a signup box. A surprising number of them don't store anything. The button animates, a toast says "Thanks!", and the address goes nowhere. Before you share the link, check:

  • It saves. Sign up with a real address from an incognito window, then find that address in your database or email tool.
  • It confirms. The person gets a short email within a minute, from your domain, not landing in spam.
  • It tells you. You get a notification (more on that below).
  • It asks one thing. One email field and one button. Add "what are you hoping it does?" as an optional second field if you want to learn something.

Where to store it:

ToolFree tier (vendor pricing pages, Nov 2026)Good for
Resend3,000 emails/month (100/day), 1,000 marketing contactsConfirmation emails sent from your own code
LoopsFirst 1,000 subscribed contacts, 4,000 sends per 30 daysA waitlist plus a simple welcome sequence
Your own database tableFreeThe simplest option, as long as you also send a confirmation

Loops has been leaning into agents this fall. In November it said an agent can read, write and send email through its MCP server, skills and CLI, so you can have Claude Code or Codex wire up the welcome email for you.

Whatever you pick, set up SPF, DKIM and DMARC on your sending domain before the first email goes out. It's the difference between "Thanks for signing up" and the spam folder.

2. Analytics: GA4 or PostHog?

Both are free at launch scale. They answer different questions.

Google Analytics 4PostHog
Cost at launchFreeFree up to 1M events/month, no card required
Best atTraffic: which sites, campaigns and searches send peopleProduct: what people do after they land, funnels, replays
Traffic by sourceYes (Acquisition reports)Yes (Web analytics: referring domains, UTMs, device)
Signup alertsNot built inYes, send any event to Slack
Session replayNo5,000 recordings/month free
Learning curveSteeper than people expectEasier to start, lots of features to ignore

Pricing and limits from PostHog's pricing page and PostHog's GA4 comparison, checked November 2026.

Our pick for a vibe-coded app: PostHog, because it covers both questions in one tool and can alert you on signups. Add GA4 too if you'll run Google Ads or care about Search Console data, which plug in natively. Even PostHog's own comparison says to keep GA4 if you live in Google Ads.

Not everyone agrees. A r/TheFounders thread called PostHog overkill for someone who just wants to know where users bounce, and a solo-developer comparison from DevToolPicks recommends Plausible for a plain marketing site. On the other side, one builder in r/SaaS installed PostHog on ChatGPT's recommendation and, after one day, noticed that visitors arriving from ChatGPT were reading the product most closely. That's the "where they came from" insight in practice.

A fair middle ground: if your site is only a landing page, a simple tool like Plausible is enough. Once there's a product behind the signup, use PostHog.

3. Get an alert when someone signs up

The first week after launch, you want to know the moment it happens, partly so you can reply personally. Three ways, from simplest:

  • Email to yourself from the same code path that saves the signup. One line in your signup handler.
  • PostHog to Slack. PostHog's Slack destination can send a message for a filtered event like signup_completed, right away or on a schedule.
  • A daily digest. PostHog insight subscriptions (available on the free tier) can email you a chart every morning: signups by source.

Fire the alert only after the signup is saved, not when the button is clicked. Otherwise you'll celebrate signups that failed.

4. Make "traffic by source" actually work

Analytics only knows where people came from if the link tells it. For every place you post:

  • Add UTM tags. ?utm_source=reddit&utm_medium=post&utm_campaign=launch. Use a different utm_source for each place.
  • Tag your own links too: your X bio, your email signature, the link in your Product Hunt maker comment.
  • Expect "direct" and "unknown." Some apps strip referrers. Leave unknown as unknown rather than guessing.
  • Use a reverse proxy for PostHog if your audience is technical. Ad blockers drop a lot of analytics requests otherwise, and PostHog recommends one in its docs.

Then, after each launch post, check the same three numbers by source: visits, signups, and signups who came back.

A prompt for your coding agent

Paste this into Claude Code or Codex:

Add PostHog to this app with a reverse proxy. Track three events: page_viewed, signup_completed (only after the email is saved to the database), and first_value_reached (define it as [your core action]). Capture UTM parameters on the first visit and attach them to the person. Send signup_completed to Slack via a PostHog destination. Send a confirmation email from our domain with Resend. Don't put the email address into analytics event properties. Then test it end to end from an incognito window and show me each step worked.

Run one test signup with a tagged link like ?utm_source=test. You should see: the address saved, a confirmation email in your inbox (not spam), a Slack or email alert, and the visit in analytics attributed to "test." If all four happen, you're ready to post.

Want a second pair of eyes first? The free LaunchBuddy scan checks whether your public site has a working signup and measurement, among other launch gaps.

Related LaunchBuddy resources

Before You Promote Your App, Prove Analytics and Signup Alerts WorkIs My Vibe-Coded App Ready to Launch? The 7-Part Technical Check (With Free Tools for Each)Product Launch Metrics: The Day-Two Dashboard and Daily Checks for an MVPA pre-launch waitlist people can actually join
The Two Things Every Vibe-Coded Launch Needs: Email Signup and Analytics That Tell You Who Came (and From Where)