Returning visitors

Who comes back, how often, and what they did before they started or bought a forge (#11265). Settings → Traffic ("Who comes back"), the Billing page ("What led to a forge") and GET /api/v1/admin/traffic/visitors?days=30 (admin token) answer the same; the API's probe counts the stored rows again.

Settings → Traffic or in the terminal ("Who comes back", t). Nothing a child collects reaches its host.

(when the forge is https), SameSite=Lax, 13 months, no Domain (this host only).

/48 (v6) prefix; the salt lives in visitor_salt and rotates every 30 days. Shown as "guessed", never merged with a cookie id. A cookie-keeping browser's very first view is recorded as probable (the cookie does not exist yet); later views are the cookie id's. No client probing.

Scrapers get no id. The forge_measure=off cookie stores nothing at all.

visit's ordered paths (no query string; a gap over 30 minutes starts a new visit). No IP, no user agent. Rows not seen for 13 months are deleted by the visitor-retention maintenance duty.

(started a forge; paid when a gift/plan code was redeemed). Stripe-paid checkouts are not linked yet.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs