Ravensight

MarketingAnalyticsPrivacy

One link per place you share your game

A trailer description, a newsletter and a streamer all say "check out the game", and the store page only sees the total. A tracked link for each one tells you which one people actually followed.

A raven perched on a wooden signpost with three arrow boards at a crossroads at night. Glowing amber threads run from its base to a video screen, an envelope with a letter, a streamer's desk and a lit shop on a hill, with a different tally of marks beside each thread.

Here's the kind of week where this matters. You put the new trailer on YouTube on Tuesday, with the Steam link in the description. On Wednesday the same link goes out in the newsletter. On Friday a streamer you've never met plays an hour of the demo and pastes the same link in chat. By Monday the store page shows a bump in visits, and you have no idea which of the three it came from.

The store can't tell you, because all three sent people to the same address. So give each place its own.

A link for each place

In Ravensight that's a campaign link.1 You paste the address you want people to land on, say where you'll share it, and group it under a campaign like "Launch week". You get a short address back, something like https://go.ravensight.io/k7Qm2xR, with a copy button next to it. Anyone who opens it is sent straight on to your page.

Make one per place. The trailer description, the newsletter and the streamer's chat each point at the same Steam page and each get a different link. A label like "Trailer description" is only there so you can find it again in a month.

Nothing goes into your game. There's no SDK to update and no build to ship, so you can make a link on the morning of a stream.

What the numbers say, and what they don't

The page shows total clicks, valid clicks and filtered clicks, then splits them by source, campaign, link, destination, device and day. Next to the totals it says "referral clicks, not conversions", and I mean that literally.

A click shows that someone followed your link. It doesn't show that they installed, wishlisted or bought, that the same person didn't click three times, or that the page loaded. If the streamer's link got four times the clicks of the newsletter's, that's a good reason to look at what the streamer did. It isn't a reason to say the stream sold four times as many copies.

Filtered clicks are the ones that look automated: crawlers, the fetchers that build a link preview when you paste into a chat, requests with no browser name, prefetches, and a burst of more than twenty requests a minute from one visitor on one link. They're stored so you can see them, and they're never billed. It's a heuristic. A bot that dresses as a browser will count as valid, and a person on an odd setup might be filtered.

What's kept

You'd want to know before you paste one of these into a post, so here it is. For each click Ravensight keeps the time, the game, the campaign and link, the source and medium you chose, the referring site's domain, and whether the visitor was on a phone, a desktop, a tablet or something else.

It does not keep an IP address, the full address of the page they came from, or anything that works as a fingerprint. The only use of the connecting address is a keyed hash that spots a burst from one visitor, and it rotates every day. Click records go after 90 days, like events.2

What it costs, and what happens at the limit

A valid click is one event on the same monthly meter your game events use. Filtered clicks cost nothing.

The part I care about most is that a link never breaks because of billing. If your included allowance runs out, the visitor is still sent where they were going and the click is still counted. The statistics page tells you how many clicks arrived after the limit, and the usual rules apply to what you're charged for them. A shared link is a promise to whoever clicks it, and I didn't want an empty balance to turn into a dead link in a trailer description.

What it can't do yet

This is a beta. There's no custom domain, so every link is on go.ravensight.io. There's no install or purchase attribution, because a click on a link can't see what happens in someone's store account. A Steamworks import that could line clicks up against wishlists and sales is the obvious next step, and it isn't built.

A routine that fits

Before you post anything with a link in it, make a fresh campaign link for that place and use it there. A week later, open the page and look at clicks by source. Keep doing what drew the most clicks, then check your store numbers to see whether that attention turned into anything.

One link per place doesn't tell you everything. It tells you where to look first, which is more than a single store address ever did.

Questions people ask

How do I track which video or post sent players to my Steam page?
Make one campaign link per place you share, each pointing at the same store page, and name the source on each. Ravensight counts the visits to each link and splits them by source, campaign, link, device and day. It counts referral clicks, so it shows where attention went, not how many of those visitors wishlisted or bought.
Do Ravensight campaign links store my visitors' IP addresses?
No. A click keeps the time, the game, the campaign, the link, the source you chose, the referring site's domain, a device class of phone, desktop, tablet or other, and whether it was filtered. A short-lived keyed hash of the connecting address is used only to spot a burst from one visitor on one link, it rotates daily, and it is not stored with the click.
What happens to a campaign link when my event allowance runs out?
It keeps redirecting. The visitor is sent on, the click is still counted, and the statistics page says how many clicks arrived after the allowance ran out. Clicks filtered as crawlers or previews are never billed.

Sources

  1. Ravensight docs, "Campaign links", including what a destination may be, exactly what is kept and the API. ravensight.io/docs ↩︎
  2. Ravensight docs, "What is kept" under campaign links. ravensight.io/docs ↩︎