Ravensight

Your store numbers, pulled in

A connection links one of your store accounts to the records you already keep. Whatever it reads goes to one of three places: money in goes to the sales ledger, attention goes to Pulse, and money out is reserved for your marketing touchpoints (no connection writes ad spend yet). Steam is the first provider.

Connecting Steam. Create a Financial Web API group key on the Steamworks partner site and add it in Settings > Connections. Only the studio owner can add, change or remove a connection. The key is checked against Steam once, stored encrypted, and never shown again, not to you, your team, your agents or our logs: you see only its last four characters. Steam lets you restrict a group key to IP addresses; if you do, ask us for the addresses to allow. Ravensight then lists the apps the key can see, and you map each app to one of your titles. An app you have not mapped is skipped and named in every sync result, never guessed.

POST /api/v1/org/connections
Cookie: gt_session (dashboard sign-in, studio owner)

{ "provider": "steamworks", "key": "<your group key>",
  "feeds": ["revenue", "attention"], "label": "Steam" }

What it brings in. Once a day, after Steam's previous day is complete, a connection reads the dates whose sales changed and writes one ledger row per title, day, country and line item (base game, DLC or bundle), and reads wishlists into Pulse as one post per mapped store page with a daily snapshot of wishlist adds, deletes and purchases. The first sync reads the 90 most recent changed dates and the last 30 days of wishlists; bring older history in with Steam's own CSV export through the sales import. A sync that stops part way carries on from where it stopped the next time, and reading the same day again updates its rows rather than doubling them.

Two choices worth knowing. Every Steam row is in US dollars, from Steam's own dollar figures: nothing is converted, and rows you import in another currency stay separate rows in that currency. Units are units sold before returns, with returned units beside them, so returns are never subtracted twice. And your own records win: a synced row that matches one you entered by hand or imported is not written, and the sync result counts it.

How it is charged. A sync is weighted events on the same meter as everything else: a flat amount per sync, one event per byte read from Steam, and each new ledger row, snapshot or post at its own weight (see Rates). Rows a sync only updates cost nothing. The daily sync follows the same background opt-in as Pulse, and Sync now is charged like anything else you ask for. Adding and testing a key are free.

Deleting a connection keeps every row it wrote, in Sales and in Pulse, and deletes the stored key. AdMob and other ad revenue come in today by CSV, through the sales import with the admob storefront and the ads line item, not by a connection.