ROI tracking

What our website script collects, and what it refuses to.

Fame podcast clients can install a small script on their own website so we can show them how many people their podcast drives there, and what those visitors do. This page is the full account of what that script does. If you are reviewing it before installing it, everything you need is below.

This is the whole thing you are being asked to add:

<script async src="https://roi.fame.so/s.js" data-client="YOUR-CODE"></script>

What it collects

  • Page views

    Which page was viewed, and when. The path only, never the full URL - so query strings on your pages are never collected.

  • Where the visit came from

    The referring domain, and any campaign tags on the link. That is what lets us separate podcast-driven visits from everything else.

  • Time on page

    How long the visit lasted, to tell a real read from a bounce.

  • Conversions

    Form submissions, plus any specific actions you have explicitly 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 the visits 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 you 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 site, 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 uniquely per client account. It cannot be reversed, and the same email address on a different Fame client's site produces a completely different value - so data can never be joined across clients.

Consent

  • The script respects your consent banner. Before consent it records a visit with no identifier at all and sets no cookie. Only after consent is a first-party identifier stored, scoped to your own domain, with a 13-month expiry.
  • 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.

Measuring this way under-counts in the EU, and we would rather say “at least this many visits” than imply a precision we do not have.

Performance

  • Under 2 KB gzipped, with no dependencies.
  • Loads asynchronously, after your page has rendered.
  • Uses sendBeacon, so it never blocks the main thread or delays page unload.
  • The size budget is enforced automatically on every build, so it cannot quietly grow.

Where the data lives

  • All data is collected and stored in the EU (Frankfurt).
  • Any client can request a full export of their data, or have all of it permanently deleted, at any time.

Questions, exports and deletion

Anything not answered here, or a request to export or delete your data:

team@fame.so