# What people said back

Marketing memory records what you put out. Pulse keeps what came back: your own posts, how their engagement moved over time, the comments, replies and quotes people left, and the people behind them. Every post you record in Pulse is also a marketing touchpoint, so the new players it was followed by sit right beside the conversation it started.

A post gets into Pulse four ways. Record it by hand in **Studio > Pulse** with its platform, its link or id, when it went out, its text and, if you have them, its numbers. Import a spreadsheet export as CSV, up to 2,000 rows a file, through a column mapping you confirm before anything is stored, as with the sales ledger. Add a **source**, a Bluesky handle, a YouTube channel or a Reddit account (up to ten per studio), and Pulse finds your new posts once a day and reads them on a schedule. Or **watch a link** to any public page, up to ten at a time, and Pulse reads that page for you (see [the crawler](https://ravensight.io/docs/pulse/#pulse-crawl) below). **Refresh** reads a polled or watched post again right now.

A polled post is read hourly for its first two days, every six hours to a week, daily to thirty days and weekly to ninety, then left alone, and at most fifty posts per studio are read on that schedule at once, the newest first. A reading only becomes a new snapshot when a number moved or a day has passed. Pulse keeps up to 500 comments and 1,000 reactions per post; past that, the post's own counters still say how many there were.

## What each platform lets Pulse see

Platforms do not all say the same things, and Pulse never fills a gap with a guess. A number a platform does not report is shown as not reported, never as zero.

| Where | Comments and replies | Who reacted | Numbers |
| --- | --- | --- | --- |
| Bluesky | Yes, and quote posts | Yes: likers and reposters by handle | Likes, replies, reposts, quotes |
| YouTube | Yes | No: YouTube never says who liked | Views, likes, comments |
| Reddit | Yes | No: Reddit never says who voted | Score, comment count |
| A watched link | Where the page shows them, such as Steam store and community pages and itch.io pages | No | What the page publishes |
| Anywhere else | By hand or CSV | By hand | By hand or CSV |

LinkedIn and X show most posts only to signed-in readers, so a link to one usually comes back as behind a login, and you record that post by hand instead. Pulse holds no account of yours on any platform and asks for no sign-in: a source is a public handle you type in.

## Huginn's summary of what they said

Ask Huginn to summarise the comments on one post, or every post in a date range (the newest 50 in it), and it answers in a short paragraph with the themes, the questions people asked, the features they requested, their objections and an overall sentiment. Each summary is one shared AI unit from the included allowance, then the prepaid balance, and asking again about a post with no new comments returns the stored summary for free. What Huginn reads is bounded (up to 200 comments or 40,000 characters, newest and most-replied first) and anonymous: each comment is labelled by a number, never by a handle or name, and it is read as material to summarise, never as instructions. Each summary is also filed as a dated finding in Muninn, so the analyst and your brainstorms can cite what people asked for. That finding belongs to the newest game of the post's project, or your studio's newest game when the post has no project, so deleting that game deletes the finding with it (the summary on the post stays), and a studio with no game yet gets no finding. In the dashboard, **Summarize** on a post and **Summarize this period** on the Posts tab say what they will use before you click. Over the API it is `POST /api/v1/org/pulse/posts//summary`, or `POST /api/v1/org/pulse/summary` with a date range. It is never available over MCP, because it is a model call.

## People, and matching them across platforms

Everyone who commented on, replied to, quoted or (where the platform says) reacted to your posts becomes a person in Pulse, with how many times and on how many of your posts. The people who came back to the most posts are listed first, and you can keep your own notes and tags on each. When the same handle appears on two platforms, or two profiles link to the same page, Pulse proposes that they are one person. Nothing is merged until someone in your studio confirms it, a rejected pair is never proposed again, and a confirmed merge is permanent.

Posts can be cited as evidence in a Studio Intelligence investigation and on a brainstorm card, and Studio Intelligence's search reads post and comment text beside your documents and touchpoints. The studio graph holds only how often repeat engagers came back to which posts: no handle, name or comment text ever goes into it.

## How Pulse is charged

There is no Pulse price. Everything Pulse stores is weighted events on the same monthly event meter as your player events, charged once for each row actually stored, so reading a post again that has not changed costs only the read. The weights per post, snapshot, comment and reaction, and the per-byte rate for watched links, are in [Rates](https://ravensight.io/docs/limits/#rates). People, matching and reading what you stored are free.

Anything you ask for (recording, importing, adding a link, Refresh) is charged to the studio's owner and can use the prepaid balance. Scheduled reading in the background uses only the included monthly events unless the studio owner opts in, and then only up to the studio's background budget. Without that opt-in, a source or link that would need the balance pauses and says so, and it picks up again after a top-up, a new month or the opt-in.

## Other people's handles, and deleting

Pulse stores what was public on your own posts: each person's handle, display name and profile link on that platform, and the text of what they wrote to you. It reads nothing about them beyond your posts, and it is shown only to your own studio. Treat it as you would any correspondence you keep.

Deleting a post deletes its snapshots, its comments and reactions and its marketing touchpoint. Deleting a source stops reading it and keeps every post it found. Stopping a watched link keeps what it read. A person record (the handle, display name, profile link and your notes) stays after their comments are deleted. To remove someone entirely, open them in Pulse, People and choose **Delete person** (the API is `DELETE /api/v1/org/pulse/people/`). Their comments and reactions are removed from Pulse, the counts on your posts drop to match, and it cannot be undone. Deleting is not charged, and it does not refund what was charged to store those rows.

## The crawler: RavensightPulse

If you run a website and found `RavensightPulse` in your logs: it reads one public page that a studio using Ravensight saved as a link, usually a post, an announcement or a thread about their own game, to keep track of the replies to it. It identifies itself as:

```
RavensightPulse/1.0 (+https://ravensight.io/docs/#pulse-crawl)
```

- It fetches only pages a studio saved, over https, with a plain GET: no sign-in, no cookies, no forms and no scripts run.
- It reads a saved page at most once a day for its first thirty days, then once a week until ninety days, then stops. It stops sooner after three unchanged reads, or three refusals, missing pages or login pages in a row.
- It visits a host at most once every five seconds from each of our servers (robots.txt and the page are one visit), runs at most two visits at once, and reads at most 2 MB of a page.
- It reads `/robots.txt` first (cached for up to a day) and honours every `Disallow` under `User-agent: *` or any user agent containing `ravensight`. A disallow with a wildcard blocks the whole host for it, and `Allow` lines are not read, so a disallow always wins.
- A page behind a login or consent wall is not read: the studio is told to record it by hand.

To keep it off your site entirely, add this to robots.txt:

```
User-agent: RavensightPulse
Disallow: /
```

Questions, or a problem with it: write to [support@realityse.com](mailto:support@realityse.com) with your host name and we will look into it.

Source: https://ravensight.io/docs/pulse/
Last updated: 2026-11-15
