Settings

Control how the app collects, classifies, and retains your attribution data.

Session window

The session window (default: 30 minutes) controls how long a visitor's session cookie lasts before a new visit from the same person is treated as a separate session.

Example: a visitor reads your blog at 9am, leaves, and comes back at 11am. With a 30-minute window, that's two sessions. With a 4-hour window, it might still be one, depending on when their cookie expired.

There's no single universally "correct" value. 30 minutes is the industry default (Google Analytics used it). If your site has longer typical reading or research sessions, extend this. If people typically visit briefly and you want to count return visits separately, keep it short.

Path exclusions

Any page path listed here won't be logged at all, even if the beacon fires on it. Useful for admin screens, payment confirmation pages, or internal tools that generate noise in your attribution data.

One path per line. A trailing * acts as a prefix wildcard:

/wp-admin
/checkout/complete
/internal-tools/*

/internal-tools/* would exclude /internal-tools/dashboard, /internal-tools/reports, and any other path under that prefix.

Self-referral exclusion

When enabled, traffic that arrives from your own domain (e.g. a visitor navigating between pages on the same site, or coming from a subdomain) is excluded from being logged. This prevents internal navigation from appearing as Referral traffic in your reports.

For most sites this should be on. Turn it off only if you're intentionally tracking cross-domain or cross-subdomain navigation.

Excluded channels

Tick any channel to exclude it from reports and charts completely. Sessions from that channel are still recorded in the database — this is a display filter, not a collection filter. Useful for removing "Internal" or "Direct" from charts when those channels are large and obscure the signals you care about.

Data retention

Set a number of days after which old session rows will be eligible for deletion. Set to 0 to keep data forever (the default). When a retention window is configured, click Purge now to remove rows older than the window immediately. The purge is manual — it doesn't run automatically on a schedule.

Debug logging

When enabled, every beacon hit and every skip decision (path exclusion, self-referral exclusion, etc.) is written to data/debug.log. This file is not web-accessible. Turn on debug logging if sessions aren't appearing and you want to understand why. Leave it off in normal operation — the file will grow indefinitely if left on.

Privacy by design

The app works without any third-party tracking script, pixel, or fingerprinting. It reads the referrer header and UTM parameters already present in every request — no extra code on visitor devices, no cross-site identifiers, no data shared with advertising networks. All attribution data stays on your server in a single SQLite database under your control. Nothing leaves unless you explicitly configure an Integrations destination.

Danger zone

Clear Attribution Log deletes every row from the sessions table. This cannot be undone. The database file itself remains, and the app continues working — it just has no historical data. Your AI Taxonomy, Tags, and Settings are unaffected.