# What you did outside the game, and what happened next

Analytics can tell you that Tuesday tripled. Only you can tell it that a video went out on Monday. A touchpoint is that record: one thing you did outside the game, written down by you, so the platform can measure what happened next.

Record one in **Studio > Marketing** with a kind (ad, video, stream, post, press, launch, update, sale or other), a title, when it happened, and optionally a link, a channel name of your own, a spend and some notes. Or import a spreadsheet export as CSV with a header row naming `kind`, `title` and `occurred_at`, plus any of `url`, `channel`, `spend`, `notes` and `tags`. Column order does not matter. Tags are separated by a vertical bar so a tag can contain a comma, `spend` is a plain amount like 129.99, and every row that validates is imported while every row that does not comes back with its line number and the reason. One bad date does not refuse the file.

Each night, and on demand from the touchpoint itself, the platform measures the lift for every game in your studio that has events. In plain words: it counts the devices whose very first event for that game arrived in the 72 hours after the touchpoint, works out how many new players a 72 hour window would have seen anyway (the average day over the previous week, times three), and reports both numbers and their ratio. If your game had no new players at all in that previous week there is no ratio, and you get an empty one rather than an invented multiple.

Lift can only be measured while that baseline week is still inside the 90 day event window, which means touchpoints from roughly the last 83 days. An older one, such as a historic campaign imported from a CSV, gets no lift, and asking for it answers `422 lift_outside_retention` without changing anything. Moving a touchpoint's date clears the old measurement and measures the new moment, or leaves it with no lift when the new date is too old.

Read it as correlation, not proof. Two touchpoints inside the same 72 hours each show the whole lift, and a storefront feature you never recorded shows none of it. The number tells you which week to look at; you still decide what caused it. Touchpoints appear as markers on the game's history chart, on the Studio Intelligence evidence map with their strongest lift, and they can be cited as evidence in an investigation. The weekly digest names any touchpoint whose 72 hour window covers a day it calls a spike.

When filling the form in, the platform can offer a suggested kind and channel from the link's host and your own title and notes. It is only ever a suggestion: nothing is filled in for you, nothing is stored until you save, and when that helper is unavailable the form works exactly as it always does. Deleting a project keeps its touchpoints, because the money you spent and the lift it produced happened whether or not the project is still in your account.

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