Link page

A public page of your links, with every view and click counted, and tracking that can carry on after the click.

A link page is a title, a line about it, your social accounts and a list of links. A project can have up to 20 of them: one for the product, one for a launch, one for each person on the team. Put its address in a bio, a signature or a QR code. It is plain HTML with no script, so it loads at once.

Create one under Links in the app, then choose it to edit its links. Its address is https://snekot.co/l/your-name.

A link with no emoji of its own shows the logo of where it goes: GitHub, the App Store, Google Play, YouTube and about thirty more. The page wears the project’s logo and colour, both set under Setup.

What gets counted

Recorded as Counts against
Someone opens the page A page view of /l/your-name The month’s events
Someone clicks a link An event, Link clicked, in the links channel The month’s events

A click is an ordinary event. It shows in the feed as it happens, carries the link’s label as a link tag and the destination’s host as a host tag, and works in every chart. A list ranked by tag:link shows which links people follow.

Crawlers and link previews are not counted, so a link pasted into a chat does not inflate the numbers. A view of a page, or a click on one link, is counted once in half an hour from one address, so reloading does not either.

Socials

Add your handles on X, GitHub, YouTube, TikTok, Instagram and LinkedIn and they show under the page’s title, each with its audience. A click on one is counted like a click on a link.

GitHub’s follower count is read for you, once a day. For the others, type the number in.

Where visitors came from

Each page shows the sites and campaigns that sent its visitors, and the countries they were in.

  • A tag in the address wins: ?utm_source=newsletter, or ?ref=producthunt. Add utm_campaign to name a campaign.
  • Otherwise it is the site the visitor came from. Known sites are named and sorted into search, social, email and AI assistants.
  • A visit with neither is Direct: the address was typed, or the app it was opened from does not say.

No IP address is stored, and a link page keeps nothing on the visitor’s device. To count visitors and visits without a cookie, the address a request came from is mixed with a secret that is thrown away each day and kept only as that scramble, so the same person is a new visitor the next day and the address cannot be worked back out. Countries come from the network in front of the API, so they appear only where one reports them.

Clicks carry the visit’s source and country as source and country tags, so a list ranked by tag:source shows which sources send people who click.

Views count as events

A view of the page takes one from the month’s events, as a click does. Past the plan, views are held: stored and not shown until the 1st or a bigger plan. At twice the plan they stop being stored until the 1st. The page itself keeps working, and its links still open. See Limits.

Views chart the same way events do. In a chart or a funnel, pick Viewed /l/your-name, or any other path the browser script has seen. Over the API a view is named view:<path>:

curl "https://api.snekot.co/v1/charts?event=view:/l/your-name&days=30" -H "Authorization: Bearer YOUR_READ_KEY"

Carrying on after the click

By default a click is where the trail ends: you know the link was followed, and nothing about what happened next.

Turn on Carry the visitor over for a link and the trail continues. The redirect adds a random visitor id to the destination’s address:

https://your-site.example/signup?ev_vid=v_yVQR6-2AwyIbAOlkbjf8

If that site runs the browser script, the script keeps the id, takes it back out of the address, and uses it for the page views and events that follow. The click and what came after now belong to one visitor, so a funnel from Link clicked to Account created works.

When the visitor signs in and your page calls snekot('setUserId', id), everything recorded under the visitor id moves to that user. From a server, the same join is one call:

curl -X POST https://api.snekot.co/v1/alias \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "user_id": "user-123", "previous_id": "v_yVQR6-2AwyIbAOlkbjf8" }'

Only ids made by a link, which start with v_, can be joined this way.

Before you turn it on

  • The id names no one. It is made at the moment of the click and is not stored in a cookie on the link page.
  • It is still tracking across sites. In the EU and elsewhere that needs the visitor’s agreement. Turn it on only for sites of your own, where your consent notice covers it.
  • It does nothing on sites that do not run the script. The address just carries an extra parameter.

Limits

A project holds up to 20 pages, and a page up to 50 links. A link only ever goes to an http or https address. The page’s address is 3 to 32 lowercase letters, digits and dashes.