Campaign links
Make a short link for each place you share your game, and see how many people followed it. It works for any game with a page to send people to, and nothing has to be added to the game itself. It is in beta.
Make and share a link
- Open Campaign links in the Live data group of the dashboard.
- Paste the address people should land on, for example your store page. It must start with
https://. - Choose the traffic source, such as a video, a newsletter or a community post, or type your own. Pick an existing campaign or name a new one. A medium and a label are optional and help you tell links apart.
- Create the link and press Copy link. The link looks like
https://go.ravensight.io/k7Qm2xR. Share it where you chose.
A link can be disabled, which stops it redirecting and can be undone,
or deleted, which cannot be undone. A game can hold up to 200
campaigns, and a campaign up to 500 links. The destination is checked
when you create or edit the link: it must be an https://
address with a site name, no username or password, no custom port, no
numeric address, nothing on a private network, nothing with
look-alike characters in the site name, and nothing that points at
another campaign link. It can be up to 2,048 characters. The link
redirects to the address you saved, plus the tags below when they
apply, whatever is added after it in the shared link.
Tags added to the address
For two kinds of destination the redirect adds a few tags to the address, built only from what you saved on the link. A tag the address already carries is never replaced, and the rest of the address is kept as you saved it. Each link's details row shows the tags, the address visitors land on and an Add tags switch. Tags are on by default; turned off, visitors land on the address exactly as saved.
- A Steam store page (
store.steampowered.com) getsutm_source(the link's source),utm_medium(its medium, when it has one) andutm_campaign(the campaign name in lower case, words joined by dashes). Steam reports wishlists for these tags in Steamworks, under UTM analytics, so you can see visits and wishlists per link there. Ravensight does not import that report. - Your own web page, your site or a web build you host, gets
rs_link, the link's id. The JavaScript SDK (0.8.0 or later) reads it on that page and counts the player, see below. The other SDKs, a Godot web export among them, do not read it yet. - An App Store, Google Play, Epic, Discord, Kickstarter or itch.io address, and a Steam address that is not the store page, gets nothing. An itch.io browser game plays in a frame that itch.io serves from its own address, which would never see the tag.
Players who arrived by a link
When the JavaScript SDK runs on the page a link reaches, it reads
rs_link from the address once, when it starts, and sends it
with the first session it opens. Ravensight keeps it only when it names a
link of the same game, and adds it to that session's events. The Clicks
tab then shows Players who arrived (different devices)
and Sessions from links in the window, and the same
split by link; each web link's details row shows its own. It counts
people who arrived by the link and played, nothing about what they did
next, and playtest and doctor sessions never count. The link id is one
you created, not personal data, and the SDK sends it under the same
consent as everything else: with opt in, only after the player's yes,
and never for a player who opted out. An itch.io link counts clicks and
no players, because it gets no tag.
Lift estimate per campaign
Each campaign is also a Marketing touchpoint, made when the campaign is made (or, for a campaign older than this, the first time its estimate is shown) and dated by its first link. Its name, kind, channel and date follow the campaign, so they change in Campaign links; notes, spend, tags and the game stay yours to edit in Marketing, and it cannot be deleted there. Choose a campaign on the Clicks tab to see its estimate: the new players in the 72 hours from the first link against the 7 days before, measured overnight like every touchpoint, and, where a Steamworks connection reports wishlists for the game's title, the wishlist adds in the same days the same way. It is an estimate, compared with the days before: anything else you did in those days counts too. Deleting a game keeps the touchpoint in Marketing as an ordinary one you can edit or delete.
What a click does and does not prove
A click is a referral click: a browser asked for your link and was sent on. It shows that the link was followed. It does not show that the visitor installed, wishlisted or bought anything, that the same person did not click twice, or that the page they reached loaded. The page calls these referral clicks for that reason, and no number on it is a conversion rate.
- Total clicks is every request for a link that was answered with a redirect.
- Valid clicks leaves out the ones that look automated: crawlers, link preview fetchers, requests with no browser name, browser prefetches, and a burst of more than 20 requests a minute from one visitor on one link.
- Filtered clicks is the difference. They are stored so you can see them, and they are not billed.
- A request that only checks the link, a
HEADrequest, is answered the same way and is not recorded. - Detection is a heuristic. A bot that looks like a browser counts as valid, and a person on an unusual setup may be filtered.
What is kept
For each click Ravensight keeps:
- the time, the game, campaign and link, and the source, medium and destination type you chose;
- the referring site's domain only, never the full referring address. The Clicks tab lists the top ten, then the clicks with no referring site, then the rest as one row;
- a device class: phone, desktop, tablet or other;
- whether it was filtered, and whether it was billed.
No IP address is stored. No fingerprint is built. The only thing that touches the connecting address is a short-lived keyed hash used to spot a burst from one visitor, which is rotated daily, cannot be queried and is not written to the click record. Click records are kept for 90 days, like events, and deleting a game deletes its campaigns, links and clicks.
Cost
One valid click is one event on the shared event meter, the same meter as game events. Filtered clicks are not billed. A link never stops working because an allowance ran out or a balance is empty: the visitor is still sent on, the click is still counted, and the stats page says how many clicks were not billed. Reading the numbers in the dashboard is not a billed action.
API
GETandPOST /api/v1/games/:gameId/campaigns,PATCH /api/v1/games/:gameId/campaigns/:id: list, create and rename campaigns.POST /api/v1/games/:gameId/campaigns/:id/linkswith{ destination, source, medium?, label?, tagDestination? }, thenPATCHandDELETE /api/v1/games/:gameId/links/:id. A refused destination answers400 invalid_destinationwith areasonand a plainmessage. A link answerstags(steam,playersor null),tagDestination(true unless turned off,400 invalid_tag_destinationfor anything but true or false) andredirectsTo, the address visitors land on.GET /api/v1/games/:gameId/campaigns/statswith optionalfromandtoas whole days (2026-11-01, both included, counted intz, a time zone name such asEurope/Berlin, default UTC),campaignId,linkIdandsource: totals plus the split by day, source, link, campaign, destination type, device and referring site (byReferrer, with(none)and(other)),totals.players,totals.sessionsandplayersByLink, and with a campaign,campaignLift. Left out, the window is the last 30 days ending today; it is at most 90 days. Any other date form answers400 invalid_range, and an unknown zone400 invalid_tz.
Not yet
Custom link domains, importing Steam's UTM report or matching clicks to wishlists or sales one by one, install and purchase attribution, players for native builds, store pages and the SDKs other than JavaScript, QR codes and splitting traffic between destinations are not part of this beta.