measuremy.site

How to track Hacker News traffic

Smartphone displaying stock market data on papers with financial charts.
Photo by Leeloo The First on Pexels

Start with the referrer

When someone clicks through to your site from Hacker News, the request usually includes a referrer containing news.ycombinator.com. Check your analytics source report for “news.ycombinator.com”, “ycombinator.com”, or a source labelled Hacker News. Some setups show the full discussion thread path, others only the domain, because HN controls its referrer policy. Treat either version as HN traffic.

If your analytics shows a large block of “direct” traffic at the same time as a HN post, check whether your links redirect through a non-HTTPS or meta-refresh page that strips the referrer. A small technical fix can recover the source.

Add UTM parameters when you submit your own link

If you are posting your own page, add campaign parameters to the URL before submitting. Example:

https://example.com/launch?utm_source=hackernews&utm_medium=social&utm_campaign=launch

This makes the visit easy to isolate even if the referrer is missing or shown as a domain only. But do not rely on UTM tags alone. HN users sometimes remove tracking parameters, and someone else may submit your page with the clean URL. Use referrer data as the fallback.

Track the thread, not just the domain

A HN visit from one thread can behave very differently from another. If you can see the full referrer path, record the item id. In practice, many analytics tools only show the domain. In that case, create a separate UTM campaign per thread when you submit your own links, such as utm_campaign=launch_hn_october. That gives you a thread-level view without needing the full referrer.

Separate the spike from the result

HN traffic often arrives as a burst, then drops quickly. Look at hourly or daily visitors, not just totals. A large spike can hide a weak signup rate. Compare the HN segment against your usual traffic:

A thread that sends a lot of traffic but no signups is not necessarily a failure. HN readers are often technical, impatient, and reading on a phone or in a break. The useful question is whether the traffic tells you something about your positioning.

Use events and funnels

Pageviews alone do not tell you whether HN visitors took action. Set up a simple funnel:

Then filter the funnel by source or campaign. If your analytics supports custom events, tag the primary call-to-action click. In measuremy.site, the Sources report lists news.ycombinator.com alongside other referrers, so a HN thread appears as a source rather than a mysterious direct visit.

Ask your coding agent for the HN numbers

If your analytics tool has an MCP server, you can skip the dashboard and ask a coding agent to inspect the data. For example, you might ask:

The agent can read the source, page, event and funnel data and give you a short answer. If you use measuremy.site, the MCP server can provide that data to Claude Code, Cursor, or Codex. This is useful when you are already working in a terminal or repo and do not want to switch context.

Watch for bots, scrapers and second-order traffic

HN threads attract more than human readers. Scrapers, RSS tools and people writing follow-up posts may visit your site. Some of those visits still appear as HN referrers, but they may not behave like a normal reader. Look for unusual patterns such as many pageviews from one IP, a very high pageview count with zero events, or visits to many pages in a few seconds. Your analytics may or may not filter these. A server log can help you spot the difference.

Keep the long-term view

A single HN thread can bring a burst that disappears by the next day. The more useful long-term view is whether some of those visitors return, subscribe, or sign up later. A cookieless tracker that does not follow a person across days cannot show a full multi-day journey from first visit to signup. But it can still show the immediate funnel and the source of the signup on the day it happened. If you need multi-day attribution, use a signup form field such as “How did you hear about us?” as a supporting signal.

Check your own legal position before collecting that kind of information.

Keep the tracking simple

You do not need a complex setup to understand HN traffic. Start with three checks:

If you can answer those three questions, you will know which threads worked, which pages held attention, and whether the HN audience is a good fit.

Hacker News traffic is best tracked as a source and a spike rather than as a long-term audience. Start with referrer and UTM data, then connect the visits to a simple signup funnel. Once you have that, you can decide whether a HN thread is worth a follow-up post, a different landing page, or no further action at all.

See it on your own site

measuremy.site is cookieless analytics your coding agent can read. 30-day free trial, no card. Plans from $9/month.

Start free trial See the live demo

Add measuremy.site analytics to this project: connect the measuremy.site MCP server at https://a.measuremy.site/mcp for all my projects (claude mcp add --scope user; it signs in with OAuth, no key, and one sign-in covers every site), then tell me how to sign in. Details: measuremy.site/llms.txt

Free tools

All free tools

More from the blog