Fame · ROI tracking

This domain serves a small analytics script

If you have found roi.fame.so/s.js on a website you look after, that site's owner is a Fame podcast client. It measures how many people their podcast sends to their website, and what those visitors do when they arrive.

It is under 2 KB, loads asynchronously after your page has rendered, and has no dependencies. It is built not to be noticeable.

What it collects

Page views
Which pages were viewed, and when. The path only - never the full URL, so query strings on your pages are not collected. Every visit is recorded, whatever brought it - see the note below on what Fame actually reports.
Where the visit came from
The referring domain and any campaign tags on the link, so we can tell podcast-driven visits from everything else.
Time on page
How long a visit lasted, to tell a real read from a bounce.
Conversions
Form submissions, and any specific actions the site's owner has asked us to count.

It records every visit, but Fame only reports the podcast ones. The script identifies where each visit came from, and Fame's reporting counts only those it can attribute to the podcast. The rest - search, ads, social, direct - is used solely as the baseline needed to answer “did visits rise after this episode went out?”, and is never presented to the site's owner as podcast performance.

What it deliberately does not do

No IP addresses are stored
An IP is used momentarily to group a single visit, then discarded. It is never written to storage.
No cross-site tracking
First-party only. Nothing follows a visitor to any other website, and there is no advertising identity of any kind.
No fingerprinting
No canvas, font or device fingerprinting.
No session replay
No recording of mouse movement, clicks, keystrokes or screen contents.
No readable personal data
If a form is submitted, the email is stored as a one-way hash, salted per account. It cannot be reversed, and the same address on another Fame client's site produces an entirely different value.

Consent

The script respects the site's consent banner. Before consent it records a visit with no identifier at all and sets no cookie. Only after consent does it store a first-party identifier, scoped to that site's own domain.

It detects Google Consent Mode and IAB TCF automatically, and can be driven directly with fameROI.consent(true). A data-before-send hook lets you inspect, rewrite or cancel every payload before it leaves the page.

Questions, or want it removed from a site you manage? team@fame.so

More about what Fame does: fame.so