Launch Metrics to Track: Eight Numbers and What Each One Tells You
Track eight numbers during a launch: visits by source, the share of those visits that reach the main action, the number who complete it, return visits a week later, comments and questions, votes, listing clicks where a platform shows them, and your own hours spent. Judge each source against your own results, not against anyone’s average. No outside benchmark is a fair target for a first launch.
What should a launch dashboard answer?
Three questions: where did people come from, did they do the thing the product exists for, and did any of them come back. Everything else is context. Votes and follower counts are pleasant, but they do not tell you whether to build the next feature, rewrite the headline or stop posting in a community. Pick the one action that proves a visitor got value, and call it the main action. For a note-taking extension it is saving the first note; for a booking tool it is a first booking; for a newsletter it is a confirmed subscription.
Nobody can give you a fair target number for a first launch. Traffic depends on your audience, your category and your timing, and any “average conversion rate” quoted without a source is a guess. The honest way to use a metric is against your own history: this source against that source, this week against next week, this headline against the one before.
Which eight numbers are worth writing down?
| Metric | How to get it | What it tells you | Watch out for |
|---|---|---|---|
| Visits by source | Your analytics, using tagged links from the UTM tagging guide | Which places send people at all | Untagged links hide in direct or referral traffic |
| Main-action rate | Completions divided by visits, per source | Which places send people who care | A tiny sample swings wildly; read the counts as well as the ratio |
| Main-action count | A raw tally from your product or analytics | The only number that is a result, not a reach | Do not count your own tests |
| Return visits at day 7 | Visitors who came back once in the week after | Whether the product is worth a second look | Needs a week; check it after, not on launch day |
| Comments and questions | Read every one and tag it as bug, confusion, idea or praise | What to fix first | Count themes, not only comments |
| Votes or reactions | Shown on the platform | Whether the pitch resonated with that audience | Easy to chase and weakly linked to use |
| Listing clicks | Where a platform shows them, otherwise visits by tagged source | How well a listing’s title and image pull | Not every platform shows them |
| Hours spent | A running log, using the launch time budget template | Which activities earned their time | Include the posting and replying, not only the building |
Record the sheet at the end of each launch day and again at day seven. If your analytics can show only a handful of dimensions, keep source, date and main action, and drop the rest.
What does reading the sheet look like?
Here is an invented example, to show the arithmetic, not any real result or benchmark. Suppose a developer launches a command-line tool and records three sources in the first week. A board listing sends 40 visits and 6 people run the install command. A community post sends 300 visits and 5 people run it. A direct message campaign to 12 people sends 10 visits and 4 installs.
- The listing converts 6 of 40 visits, 15 percent in this made-up case. A small, relevant audience.
- The community post converts 5 of 300, under 2 percent. It brought reach and few installs. The reply threads may hold the reason: read them.
- The direct messages convert 4 of 10. The highest ratio, the lowest volume. The lesson is to send more targeted messages, not that messages are best for everyone.
No source is simply “the winner”. The reading is that this product gains most from precise audiences, so the second week should go to more small, specific places and fewer broad posts. You can only draw that conclusion because the links were tagged and the main action was defined before launch.
How do you measure what numbers miss?
Comments are data. Make a short list of the themes that recur: “I could not find the settings”, “does it work offline”, “how is this different from X”. Three people asking the same question is a bigger signal than a hundred votes, and it often points at the first sentence of your page. The how to respond to launch comments answer covers the replies; the feedback request template helps you ask visitors who did not comment.
Keep a column for first-time questions. If many people from one source ask what the product is, the listing there is unclear. If they ask what it costs, the pricing is hard to find. If they ask about a feature you have, the page is hiding it.
What do you decide from it?
- Rank sources by main-action count first and by rate second. A high rate on a tiny sample is a lead, not a verdict.
- Repeat the places that brought completions, with fresh content, and drop the ones that brought none after a fair try.
- Fix the top confusion from the comment themes before you write another announcement.
- Compare hours with results. If one activity took most of your time and brought little, stop doing it.
- Set next month’s campaign name and run the same sheet again.
To get a first row of data, launch your product free on this board with a tagged link and send the main action from there into your sheet. For a wider view of how to read a launch, see how to measure a launch and post-launch checklist. If you are choosing what to build next, the finance ideas on the board show what people ask for.
Frequently asked questions
What is the most important launch metric?
The number of people who completed your main action, such as a first note saved or a first booking made. It is the only one that is a result, not reach. Visits and votes show attention; the completion count shows whether the product delivered what the page promised.
What conversion rate should I aim for after a launch?
No honest target exists for a first launch, because rates depend on audience, price and category, and we know of no source we could cite. Compare your own sources with each other and with your next launch instead. Track the rate and the raw counts together.
Are upvotes a good measure of launch success?
They are a weak one. Votes show that a pitch resonated with a platform’s audience, but they are easy to collect without anyone using the product. Read them beside the main-action count and the comments, and treat a high vote total with few completions as a message problem.
When should I check retention after a launch?
Check return visits seven days after each person’s first visit, which means looking again in the week after launch. Day-one numbers cannot show retention. If your analytics cannot follow individual visitors, count how many came back from a tagged email or link a week later.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.