Growth

How to measure a Product Hunt launch beyond upvotes

Ownlytics team · · 6 min read

To measure a Product Hunt launch, tag every link you control, pin the launch day on your chart, and compare the launch window to a normal week on visitors, signups, sales and revenue per visitor. Upvotes tell you how the launch felt. Revenue and what happens in the following weeks tell you whether it worked.

yourapp.comToday7d30d9 online
Visitors3,619+42.1%
Revenue$2,226+67.0%
Conversion0.41%+8.4%
Revenue/visitor$0.11+17.6%
1.4k7000
SourceVisitorsSalesRevenue
Yproducthunt.com3,9006$294
Xx.com2,8005$245
@newsletter9004$196
Ggoogle.com7002$98
Rreddit.com6400$0

Fig.A launch week, by source. Sample data, not a real site.

Launch day is noisy. Traffic spikes, sources blur together and the numbers look impressive for 24 hours. A little setup beforehand makes the aftermath readable.

What should you set up before launch day?

Do these a few days ahead, not that morning.

  1. Decide your tag scheme. Use utm_source=producthunt for links you place in your listing, maker comment and replies. Add utm_medium=listing or utm_medium=comment so you can tell them apart.
  2. Tag the links you send elsewhere. Your launch tweet, newsletter and Slack or Discord announcements each get their own utm_source and utm_medium. Otherwise their traffic mixes into the Product Hunt total or lands in Direct.
  3. Define your goals. Decide what counts as success: a signup goal, a checkout click, a purchase. Goals and funnels can be set with a data attribute on a button.
  4. Confirm sales are linked to visits. Run one test purchase and check it shows a source. Our revenue attribution setup lists the three ways a sale gets linked.
  5. Note the baseline. Write down your normal weekly visitors, signups and revenue. Without a baseline, "we got 3,000 visitors" means nothing.

On the day, pin a note to the chart ("Launched on Product Hunt") so the spike has its label. Chart notes are built for exactly this.

Which numbers matter after the launch?

Look at them in this order.

  1. Visitors by source and campaign. How much came from the listing, how much from your own announcements? This shows which of your efforts mattered, not just the platform.
  2. Conversion to your first goal. Of the visitors, how many signed up or started checkout? A huge visit count with a tiny signup rate means the audience was curious, not in market.
  3. Sales and revenue by source. The honest scoreboard. Remember some buyers take days, so check again at one week and one month.
  4. Revenue per visitor. Launch traffic is often browsing traffic. Compare its revenue per visitor to your normal sources before deciding the launch was a bargain or a bust.
  5. The tail. What do visitors, signups and sales look like on days 3 to 14? A launch that leaves your baseline higher has done something. One that snaps back to where you started gave you a spike.
Ownlytics alertsbot · online
New sale · $49Dodo Payments · India
Source: x.com → /blog/setup-guide
3 visits over 12 days
New sale · $9Polar · Germany
Source: google.com → /pricing

Fig.A sale alert in Telegram: the source and the page, not just the amount. Sample data, not a real site.

Example (made-up numbers for illustration)

Imagine a normal week for a small tool: 800 visitors, 24 signups, 4 sales, $196 revenue. After a launch, the first 7 days look like this.

SourceVisitorsSignupsSalesRevenueRevenue per visitor
producthunt (listing and comments)2,400603$147$0.06
x (launch thread)500254$196$0.39
newsletter220306$294$1.34
everything else900254$196$0.22

The Product Hunt listing delivered the most visitors and the weakest revenue per visitor. Your own newsletter was tiny and the best payer. The decisions this triggers: do not count the launch as a failure because the listing converts low, since it widened the funnel and made the other numbers possible. But also do not read it as proof of fit. Put the next unit of effort where revenue per visitor is highest, and treat the listing as reach.

What decision should each result trigger?

When this does not apply

If you launched without tagged links, you can still reconstruct some of it from referrers, but expect gaps: many links arrive with no referrer or from in-app browsers. Do the best you can with the data and tag properly next time. Also, a launch is one event. Do not generalize from a single day to a channel strategy. If you want a repeatable picture of channels, track a thread launch from click to sale uses the same approach for a smaller event.

At a glance

StepWhenWhat to do
Choose UTM schemeA few days beforeproducthunt source, medium per placement
Tag outside linksBefore launchOwn source and medium for tweet, newsletter, chat
Record baselineBefore launchWeekly visitors, signups, revenue
Pin the launch noteLaunch dayOne chart note on the day
First reviewDay 7Source table, revenue per visitor
Second reviewDay 30Late buyers, new baseline

If you want the source table and notes ready for your own launch, the live demo shows how they look with sample data.

FAQ

Should I send Product Hunt traffic to my home page?

Not necessarily. A page written for launch visitors that explains the product and links to the next step often works better. Tag the link either way so you can compare it to the home page.

Why did upvotes not translate into revenue?

Upvotes come from people interested in the launch, not necessarily buyers. Compare revenue per visitor to your other sources to see how well the traffic matches your product.

How long should I wait before judging the launch?

At least until you know your normal time to buy. If customers typically take a week or two, a day-one verdict will undercount. Check at one week and again at one month.

Can I measure a launch if I forgot to tag links?

Partly. Referrers and campaign data still help, but some visits will appear as Direct or from apps that hide the origin. Use what you have and tag from the next launch onward.

See the live demo · View pricing

Keep reading