Disclosure: I work on LaunchReach, which generates a tagged link per submission. The convention below works with any spreadsheet and any analytics setup, and I note where the product fits at the end.
If you submit a product to a handful of launch directories and communities, you will probably look at GA4 a week later and see traffic split across producthunt, ProductHunt, product_hunt and ph. Each one is a separate row. Nothing is broken; the tags were just never agreed on.
This tutorial sets up a small naming convention you can write down before launch week, so the reports roll up by destination without cleanup afterwards.
What the three parameters do
GA4 reads these UTM parameters from your landing URL:
-
utm_source: where the visitor came from (the specific destination) -
utm_medium: the type of channel -
utm_campaign: the effort this link belongs to
GA4 is case-sensitive about values. Directory and directory are two different mediums. That is the main reason a convention matters.
Step 1: Fix the rules before you write any link
Four rules cover most of it:
- Lowercase only. No exceptions.
- Hyphens for spaces, no other punctuation.
show-hn, notShow HNorshow_hn. - One name per destination, forever. Decide it once and put it in a sheet.
- No personal or sensitive data in any value. UTM values show up in URLs, reports and sometimes shared screenshots.
Step 2: Choose source = the destination
Source is the one you will filter by most, so make it the destination's name in its simplest form:
utm_source=producthunt utm_source=show-hn utm_source=indie-hackers utm_source=devto Do not put the campaign or date in the source. If you do, the same destination ends up with several sources and you lose the rollup you wanted.
Step 3: Choose a small, closed list for medium
Medium should come from a short list you never extend casually. For a launch, three or four values are enough:
-
directory: listing sites where you submit a product page -
community: forums and discussion sites where you post -
email: messages you send to your own list -
social: posts on social networks
The point of a closed list is that you can group by medium and compare types of channel. If you invent a new medium for every launch, that comparison disappears.
Step 4: Make campaign describe the launch, not the place
Campaign is the effort, so every link in the same launch shares it:
utm_campaign=launch-v1 If you ship a second launch later, use launch-v2 or something like pricing-relaunch. Keep a pattern: <what>-<version or month>. Then you can compare launches by campaign, and destinations within a launch by source.
Step 5: Build a sheet with one row per destination
A plain spreadsheet is enough:
| destination | source | medium | campaign | final URL |
|---|---|---|---|---|
| Product Hunt | producthunt | directory | launch-v1 | https://example.com/?utm_source=producthunt&utm_medium=directory&utm_campaign=launch-v1 |
| Show HN | show-hn | community | launch-v1 | https://example.com/?utm_source=show-hn&utm_medium=community&utm_campaign=launch-v1 |
| Dev.to | devto | community | launch-v1 | https://example.com/?utm_source=devto&utm_medium=community&utm_campaign=launch-v1 |
(example.com is a placeholder. Use your own landing page.)
Two habits keep this sheet useful:
- Fill it before you submit anywhere, so nobody is typing tags from memory at the last minute.
- Add a column for the date you submitted and the outcome. Later you can match it against what GA4 shows.
Step 6: Point each link at a page that can convert
A tagged link only tells you where someone came from. Decide where they land. Sending every destination to the same homepage is fine for a first launch, but think about whether a community audience would be better served by a page that matches what you wrote in the post. If you change landing pages per destination, record that in the sheet too, because it changes how you read the numbers.
Step 7: Check the tags before launch day
Before you submit, open each link yourself once. Then in GA4, look at the real-time report and confirm your visit shows the source and medium you expect. It takes a few minutes and catches typos while they are cheap to fix.
Also check that your signup or key event is configured as a conversion in GA4. Without that you will see sessions per source but not which source produced signups.
Step 8: Read the report by source first, then by medium
After launch week, in GA4's traffic acquisition view, look at session source / medium. Because you stuck to the convention you should see one clean row per destination, such as show-hn / community. Group by medium to compare directories against communities, and filter by campaign to isolate this launch.
One caveat: UTM tags only measure visits that came through the tagged link. Someone who sees your product on a directory and later types your URL will show up as direct. Treat the numbers as a floor for a destination, not an exact total.
Common mistakes
- Mixed case. Fixed by rule 1.
- Tagging internal links. Do not add UTMs to links on your own site; they overwrite the original source.
- Reusing a tagged link everywhere. One link shared across destinations gives you one row and no comparison.
- Changing names mid-launch. If you rename a source after the first posts, the old and new names will sit side by side in reports.
Where LaunchReach fits
If you would rather not maintain the sheet by hand: according to its website, LaunchReach gives every submission and campaign its own tagged link and connects GA4 and Search Console read-only, so traffic and signups can be attributed per destination. It also states that it does not claim attribution the data cannot support, which matches the caveat in step 8. You can use the convention above either way; it just makes the by-hand version predictable.
The short version
- Lowercase, hyphens, no sensitive data.
- Source = destination, medium = a short closed list, campaign = the launch.
- One row per destination in a sheet, filled in before you submit.
- Test each link, then read GA4 by source, then by medium.
What naming rules do you use that I missed? I would like to hear how others handle sources for destinations that appear under several names.
Try LaunchReach: 7-day Growth trial for $1 at mambatxhub.com

