What Mayfly does and doesn’t measure
Mayfly counts visits without cookies and without following anyone across days. That makes some reports possible and rules others out, and this page says which.
How a visitor is counted
Nothing is stored in the visitor’s browser: no cookie, no localStorage identifier. Instead, each event is attributed to a hash computed on the server:
visitor_id = sha256( daily_salt + site_id + ip_address + user_agent )- The salt is random and changes at midnight UTC. Old salts are deleted from the live database once they are two UTC days old, after which Mayfly can no longer work a hash back to an address. Database backups can hold a deleted salt until they expire.
- The site ID is part of the hash, so the same person on two different websites gets two unrelated identifiers.
- Raw IP addresses and User-Agent strings are used while the visit is processed and are not stored with events.
What that means for your reports
- Daily uniques, not people. Over a 30-day period, someone who visits on three days counts three times.
- No cross-day reports. There are no returning-visitor cohorts, retention curves, lifetime value or journeys that span days, and Mayfly doesn’t offer reports that imply them.
- Attribution within a visit. A visit’s source is decided when it starts and carried by every event in it. A visit ends after 30 minutes of inactivity, or at midnight UTC.
- Approximate edges. People sharing an IP address and browser can merge; one person changing network can split.
What the script collects
| Field | Detail |
|---|---|
| Page address | Query strings are removed by default. Identifier- and credential-shaped values are redacted before storage. |
| Page title | As the page reports it, with email addresses and token-shaped values redacted. |
| Referrer | The referring host only, resolved to a source name. Links within your own site are not referrers. |
| Campaign tags | UTM source, medium and campaign, when the address carries them. |
| Country, region and city | Looked up from the IP address when the visit arrives. The address is then discarded. |
| Browser, operating system, device class | Read from the User-Agent header. |
| Screen size | One of five size classes, not the exact dimensions. |
| Time on page and scroll depth | Milliseconds with the tab in front, and the furthest scroll position. |
| Outbound clicks and downloads | The destination’s origin and path, never its query string. |
| Core Web Vitals | LCP, INP, CLS, TTFB and FCP, as the browser measures them. |
| Custom events | Only the names, properties and revenue your site sends. |
What it doesn’t
- Cookies or any identifier stored in the browser.
- Raw IP addresses in the event store.
- Names, email addresses or account IDs as analytics fields. Common accidental identifiers are dropped, and sites must not send personal data.
- Device fingerprints: no canvas, audio, font or WebGL probing.
- Browsing across other websites.
Visits that are never counted
Browsers that send Do Not Track, visitors who block the script or have JavaScript off, detected bots, localhost and .local hosts, and anyone who has set mayfly_ignore on their device. Reports count accepted events, not every human who loaded a page.
Core Web Vitals
The Overview reports LCP, INP and CLS for each page at the 75th percentile of the measurements your visitors’ browsers sent in the period.
- A metric is shown only once it has 30 measurements on that page. Below that you see a dash, never a made-up zero.
- A page is Good only when all three metrics have 30 measurements and pass: LCP up to 2.5 s, INP up to 200 ms, CLS up to 0.1. Otherwise it shows the worst threshold crossed, or Partial data.
- INP is an approximation: the longest observed interaction, not the full reference algorithm.
- These are Mayfly’s own field measurements, not Google’s CrUX data or a Lighthouse lab score.
How long data is kept
- Raw events: 25 months. Daily totals: 37 months.
- Imported Search Console data: 37 months.
- Audit results: 13 months.
Data is stored in the United States. The services involved are listed on Subprocessors, and the full account is on Privacy.
Something here doesn’t match what you see? Write to kirylapps@gmail.com.