Cookies and cookieless mode

The two first-party cookies Trakily sets, the cookieless script, and what changes between them.

Default: two first-party cookies

The standard script (https://trakily.com/js/script.js) sets two cookies on your own domain. They are first-party: they belong to your site, not to Trakily, and are never shared across unrelated websites.

Cookie	Contents	Lifetime
`_trakily_vid`	A random visitor id, the time this visitor was first seen, and their visit count.	1 year
`_trakily_sid`	A random session id.	30 minutes, extended on every event

Cookie: _trakily_vid
Contents: A random visitor id, the time this visitor was first seen, and their visit count.
Lifetime: 1 year

Cookie: _trakily_sid
Contents: A random session id.
Lifetime: 30 minutes, extended on every event

Both are set with SameSite=Lax, Secure on HTTPS pages, and on .yourdomain.com so they work across your subdomains. A session ends after 30 minutes without activity; the next visit starts a new session and increases the visit count.

Remembering the visitor is what lets Trakily credit a payment made days after the first visit to the channel that brought that visitor, and show returning visitors and customer journeys.

Cookieless mode

Turn on Track without cookies in Settings → Tracking to switch to https://trakily.com/js/script.cookieless.js. That build sets no cookies:

It keeps only a per-tab session id in sessionStorage, which expires after 30 minutes of inactivity and disappears when the tab closes.
The server derives an anonymous visitor id from a hash of a secret salt, your site, the IP address and the browser's user agent. The salt rotates every day (UTC), so the same person gets a new id each day and can't be followed over time.
It never links visitors across domains.

Your snippet in the app updates automatically when you switch. If you pasted it by hand, update the src.

What changes in cookieless mode

	Cookies (default)	Cookieless
Visitor ids	Stable for up to a year	Rotate every 24 hours
Revenue attribution across days	Yes	Weaker: a visitor who pays on a later day looks like a new visitor
User and Journey tabs	Yes	Not available
Returning-visitor breakdowns	Yes	Not available
Cross-domain tracking	Yes	No
Pageviews, sources, goals, revenue totals	Yes	Yes

: Visitor ids
Cookies (default): Stable for up to a year
Cookieless: Rotate every 24 hours

: Revenue attribution across days
Cookies (default): Yes
Cookieless: Weaker: a visitor who pays on a later day looks like a new visitor

: User and Journey tabs
Cookies (default): Yes
Cookieless: Not available

: Returning-visitor breakdowns
Cookies (default): Yes
Cookieless: Not available

: Cross-domain tracking
Cookies (default): Yes
Cookieless: No

: Pageviews, sources, goals, revenue totals
Cookies (default): Yes
Cookieless: Yes

Which one should I use?

If revenue attribution is why you use Trakily, keep the default cookies and mention them in your cookie notice. Use cookieless mode when avoiding cookies matters more to you than multi-day attribution. Whether you need consent depends on your jurisdiction and setup; this page is not legal advice. Our cookie policy lists exactly what is stored.

Other browser storage

trakily_payment_<provider>_<id> in sessionStorage: remembers that a checkout success page was already reported, so a reload doesn't send it twice.
trakily_ignore in localStorage: read, never written. Set it to true in your own browser to exclude your visits (see Exclusions).