> ## Documentation Index
> Fetch the complete documentation index at: https://leadtrackr.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Cookies Used by LeadTrackr
> Every cookie LeadTrackr writes on your website, what it is for, how long it lives and which part of LeadTrackr sets it.
LeadTrackr writes a small number of **first-party cookies** on your own domain. They are never shared with another website and none of them contains a name, an email address or a unique visitor identifier.
Use this page when you fill in your cookie policy or configure your consent banner.
## Overview
| Cookie | What it is for | Lifetime | Set by |
| ---------------- | --------------------------------------------------------------- | -------------------------------- | ---------------------------------- |
| `lt_channelflow` | The visitor's marketing channel path | 395 days | GTM tag, WordPress plugin, LeadBot |
| `lt_session` | Whether the visitor is still in the same session | 30 minutes of inactivity | GTM tag, WordPress plugin, LeadBot |
| `lt_consent` | The visitor's consent status, so it travels along with the lead | 30 minutes of inactivity | WordPress plugin |
| `lt_probe` | Technical check, written and deleted immediately | Removed within the same pageview | WordPress plugin |
All LeadTrackr cookies are written with `SameSite=Lax` and, on an HTTPS site, the `Secure` flag.
## lt\_channelflow
The `lt_channelflow` cookie stores the visitor's marketing channel path. It contains attribution data such as the source, medium, campaign and landing page for each recorded session. The cookie does not contain personal information or a unique visitor identifier and is used solely for first-party analytical attribution.
It is read only when a visitor becomes a lead. At that moment the stored channel path is attached to the lead, which is what lets you see that a "direct" conversion actually started with a Google Ads click three weeks earlier.
Example value, of a visitor who arrived through a Google Ads campaign and came back directly five days later:
```json theme={null}
[
{
"t": 1784615580000,
"ch": { "s": "google", "m": "cpc", "cm": "zomeractie", "ct": "tekstadvertentie" },
"lp": "/conversion-tracking"
},
{ "t": 1785085320000, "ch": { "s": "direct", "m": "none" }, "lp": "/pricing" }
]
```
The keys are short to keep the cookie under the 4 KB browser limit:
| Key | Meaning | Example |
| ------- | ------------------------------------------------ | ------------------------------------- |
| `t` | Timestamp of the session start, in milliseconds | `1784615580000` |
| `ch.s` | Source | `google`, `direct`, `www.example.com` |
| `ch.m` | Medium | `cpc`, `organic`, `referral`, `none` |
| `ch.cm` | Campaign, only when a `utm_campaign` was present | `zomeractie` |
| `ch.ct` | Content, only when a `utm_content` was present | `tekstadvertentie` |
| `ch.tm` | Term, only when a `utm_term` was present | `conversion tracking` |
| `lp` | Landing page path, truncated at 100 characters | `/conversion-tracking` |
The value is stored URL-encoded, so in your browser's developer tools you will see `%5B%7B%22t%22%3A1784615580000…` rather than the readable JSON above.
See [Channel Flow Tracker](/docs/lead-sources/channel-flow-tracker) for how the path is built and how a channel is determined.
## lt\_session
The `lt_session` cookie is a lightweight session cookie used to determine whether a visitor is still within the same browsing session. By default, it expires after 30 minutes of inactivity — the same window GA4 uses. It does not store any visitor information and simply indicates whether a new Channel Flow session should be started.
Example value:
```
1
```
That is the entire contents. The cookie's existence is the signal that a session is running; its expiry is left to the browser.
The GTM route lets you change the session timeout on the tag. The WordPress plugin and the LeadBot always use 30 minutes.
## lt\_consent
The `lt_consent` cookie records the visitor's Google Consent Mode status — whether analytics and advertising storage were granted or denied — so that the consent status is sent along with the lead into LeadTrackr. Every lead then carries the consent state that applied at the moment it was submitted, and your conversion destinations can act on it.
It stores nothing but `granted` and `denied` values, holds no visitor information, and is rewritten the moment a visitor changes their choice in your consent banner. If the site has no Consent Mode at all, the cookie is not set.
Example value, of a visitor who accepted analytics but declined personalised advertising:
```json theme={null}
{
"ad_storage": "granted",
"analytics_storage": "granted",
"ad_user_data": "granted",
"ad_personalization": "denied"
}
```
A consent type the site never sets is left out of the cookie entirely, rather than being guessed at. This value is also stored URL-encoded.
Only the WordPress plugin uses this cookie. With the GTM route, the tag reads the consent status directly from Consent Mode inside Tag Manager, so no cookie is needed.
## lt\_probe
The `lt_probe` cookie is a purely technical check. The WordPress plugin writes it once to find out on which domain cookies can be stored — a `.co.uk` or `.com.au` site works differently from a `.nl` site — and deletes it again in the same instant. It holds no data, no visitor information, and never survives the pageview it was created in.
Example value:
```
1
```
A cookie scanner may still pick it up while scanning, which is why it is listed here.
## Privacy by Design
LeadTrackr's cookies were designed according to privacy-by-design principles. Instead of generating or storing a unique visitor identifier, they store only the visitor's marketing channel path in a first-party cookie. In other words, LeadTrackr stores the marketing journey, not the identity of the visitor.
The cookies do not contain personal information or a unique identifier. They store only attribution data, such as the marketing source, medium, campaign and landing page of each session. They are not used for advertising, profiling, remarketing or cross-site tracking.
The channel path is only read when a visitor submits a form or otherwise becomes a converted lead. At that point it is attached to the lead in LeadTrackr for first-party attribution reporting.
When determining how to classify these cookies, you may want to consider the following:
* No unique visitor identifier is generated or stored.
* The cookies are first-party and remain on your own domain.
* They store only marketing attribution data for analytical purposes.
* They are not used for advertising, profiling or cross-site tracking.
* The channel path is only read when a lead is created and the attribution data is attached to that lead.
Whether these cookies should be classified as functional or analytical depends on your own legal assessment, local regulations and the way LeadTrackr is implemented within your organisation.
## Where These Cookies Come From
Writes all four `lt_` cookies when Channel Flow is enabled
Writes `lt_channelflow` and `lt_session` through GTM
Writes `lt_channelflow` and `lt_session`