How to Measure a Product Hunt Launch

To measure a Product Hunt launch, tag your launch URL with utm_source=producthunt, record a two-week baseline before launch day, track signups and payments by source rather than upvotes, and judge the result on what it produced 30 days later: paying customers, revenue per visitor and the lift in direct and branded search it leaves behind. Upvotes and rank measure how the launch went on Product Hunt. Those four numbers measure what it did for your business.

How much traffic does a Product Hunt launch bring?

Less than the legends, and it depends almost entirely on whether you are Featured. Since Product Hunt moved to editorial curation in 2024, only a minority of launches appear on the homepage — commonly cited estimates put it around 10% — and non-featured launches see a small fraction of the traffic. Aggregated launch data compiled by Shno puts featured launches at roughly 1,000–5,000 visitors on launch day and non-featured ones at 100–500, with a #1 Product of the Day typically in the 5,000–10,000+ range.

Real case studies cluster around that. One well-documented launch, own.page at #2 Product of the Day, reported 17,300 visits and 2,021 registrations over the 22 days after launch (own.page) — an unusually high signup rate for a free tool with a strong hook. For a paid B2B SaaS, a few hundred signups and a handful of paying customers in the first month is a normal, healthy outcome.

What should you measure for a Product Hunt launch?

Notice what is not on that list: upvotes, comments and rank. They matter for getting Featured and for the badge on your site, but they don't correlate tightly with business outcomes. A #4 launch with a sharp landing page for a paid product can easily out-earn a #1 launch of a free toy.

How do you set up tracking before launch day?

1. 1.Record a baseline. Note your daily visitors, signups, direct visitors and branded search clicks for the 14 days before launch. Without it you can't measure the halo afterwards.
2. 2.Tag the launch link. Use https://yoursite.com/?utm_source=producthunt&utm_medium=community&utm_campaign=2026-10-launch as the product URL. Product Hunt also appends ?ref=producthunt to outbound links, but many analytics tools don't read the ref parameter as a source, so your own UTMs are what make the traffic unambiguous. Build it with a UTM builder.
3. 3.Tag every launch-day share. The X thread, the LinkedIn post, the email to your list and the community posts each get the same campaign with their own source, so you can see what the launch drove beyond Product Hunt itself.
4. 4.Track signups as an event, fired after your backend confirms the account (not on button click). The custom events docs show the one-line call.
5. 5.Connect payments to visitors so launch-day signups who pay in week three are still credited to the launch. The revenue-by-source guide covers the Stripe setup.
6. 6.Make sure your analytics filters bots. Launch days attract scrapers, directory crawlers and automated upvote-checkers that load your page with JavaScript.
7. 7.Test the whole path once: open the tagged URL in a private window, sign up, and confirm the signup appears under source producthunt.

What should you watch on launch day?

Launch day is the one day when real-time analytics earns its keep. You want to see three things, roughly every hour: human visitors from the launch, signups from the launch, and where else traffic is coming from (X, LinkedIn, newsletters, other directories that copy Product Hunt's daily list).

• Signup rate by hour. If visitors climb but signups don't, the landing page is the problem — fix the headline or the CTA while the traffic is still there, not next week.
• Device split. A large share of Product Hunt traffic is mobile. If mobile signup rate is a fraction of desktop, your signup form is the bottleneck.
• Bots versus humans. Launch-day traffic spikes are exactly when bot traffic is highest, and it drags signup rates down. Count humans; see bot traffic in analytics for how filtering works.
• Referrers you didn't expect. Newsletters, aggregator sites and other launch directories often pick up a top launch within hours. Note them; they are your next distribution targets.

VisitTrack's live view and live globe are built for days like this — you see visitors arrive, signups land and payments burst on the map in real time — and its bot filtering keeps launch-day scrapers out of the counts. If the launch gets picked up on Hacker News or Bluesky, the Mentions tab shows those posts next to the traffic they sent. None of this is required to measure a launch, but having it on a second screen makes the hourly fixes above much easier to spot.

How do you measure the launch after day one?

The spike decays fast. Launch-report data compiled by Shno shows day-two traffic at roughly 20–36% of day one and under 10% by days three to seven. But the money often arrives later: trial users convert at the end of their trial, people who bookmarked you come back, and other sites write about top launches. That is why day 30 is the real verdict.

Revenue per visitor is the number that lets you compare the launch with everything else you do. In the example, $0.13 per launch visitor is close to the product's organic search average, which makes the launch worth repeating in a year with a new major version — but not worth treating as a growth channel in itself. If your launch converts at a fraction of your other channels, that's normal for a broad audience and not a failure. Plug your own numbers into the revenue per visitor calculator and the conversion rate calculator.

How do you measure the halo effect of a launch?

Some of the launch's value never shows up under source “producthunt”. People see the launch, then search your name on Google a week later, or type your URL directly, or click a link in a newsletter that covered top launches. To estimate it:

1. 1.Compare direct visitors per day for days 7–30 after launch with your 14-day baseline. The difference, minus normal growth, is a rough halo estimate.
2. 2.Do the same for branded search clicks in Google Search Console (queries containing your product name). VisitTrack can show these keywords next to your traffic if you connect Search Console.
3. 3.Check first-touch attribution for customers in the 30 days after launch. Customers whose first touch was producthunt.com or utm_source=producthunt but who paid on a later direct visit are launch customers that last-touch reporting would miss. First-touch vs last-touch attribution explains why that matters.
4. 4.List new referring domains from the launch week. Directories and blogs that link to top launches give you backlinks that keep sending a little traffic for months.

Is a Product Hunt launch worth it?

For most products, yes, as a one-time event with modest expectations. It is a good way to get early users, feedback, backlinks and a credibility badge. It is rarely a repeatable acquisition channel: you can only launch the same product a few times, and the audience is broad and tool-curious rather than your exact buyer. Developer tools, AI products and productivity apps tend to do best; niche vertical B2B products often see a lot of upvotes and very few customers.

The way to decide whether to launch again is the day-30 scorecard. If launch revenue per visitor was within range of your best channels, plan the next one around a major release. If it was far below, put the effort into the channels that win on paying customers instead; which marketing channels bring paying customers shows how to compare them. For more on setting up analytics for AI products specifically, see the AI startups use case.