Tracking modes
Privacy-friendly or full attribution: what each mode collects, what it costs you, and what changes when you switch.
Every project uses one of two tracking modes. The choice decides whether Clakta saves anything in the visitor's browser, which affects both how precise attribution is and which privacy rules apply to you.
Choose it when you create the project, or change it later in Project settings → General.
Privacy-friendly
The default. No cookies and nothing saved on the visitor's device.
Instead, Clakta builds an anonymous id for the day from the visitor's IP address, browser and your site's domain. The same visitor gets the same id for the rest of that day, which is enough to group their pages into a session. The IP is only used to build that id; it isn't stored as is.
What you give up:
- No memory across days. Someone who clicks an ad on Monday and buys on Thursday shows up as two different people.
- No memory across devices. Phone and computer are always separate visitors.
- People on the same network can blur together, for example in the same office with similar browsers.
- No personal data on orders. Orders can't carry name, email, phone, gender, date of birth, address or customer id.
Full attribution
The script saves an id in the visitor's browser, so Clakta recognizes the same person across pages, visits and days.
What you get:
- Real customer journeys. The first and last click can be days apart and still belong to the same person.
- Multi-touch models that work. Linear, Linear Paid and Triple Attribution need journeys longer than one day.
- Customer records. Orders can carry name, email, phone and address, and you can identify customers.
- The Users section fills up, because there are real people to list.
The cost: saving an id on a visitor's device usually requires their consent under GDPR and similar laws. See Consent management.
Side by side
| Privacy-friendly | Full attribution | |
|---|---|---|
| Cookies or browser storage | None | An id from your own site |
| How long a session lasts | One day | Across visits |
| Across devices | No | Yes |
| Personal data on orders | Rejected | Accepted |
| Users section | Empty | Filled |
| Multi-touch attribution | Same day only | Full journeys |
| Usually needs a consent banner | No | Yes |
Which one to choose
Choose privacy-friendly when privacy rules come first, when most people buy on the same day they click, or when you want to start collecting data today without a consent banner.
Choose full attribution when people take days to decide, when you run retargeting and want it credited correctly, or when you want reports per customer, and you can handle consent.
Many teams start with privacy-friendly to get numbers flowing, then switch to full attribution once their consent banner is ready.
Switching modes
You can switch at any time, but the change only applies from then on:
- Past data stays the way it was collected.
- A visitor active before and after the switch counts as two people.
- Reports that cover the switch date mix both, so a jump in the numbers around that date is expected.
The Orders API follows the project's current mode. After switching to
privacy-friendly, orders with customer personal data are rejected. After
switching to full attribution, your orders keep working, but start sending
sessionId to get the benefit.
Related articles
How Clakta tracking works
The path from an ad click to a sale in Clakta, step by step, and where to look when something is missing.
Track ecommerce events
Record product views, add to cart, checkout started and payment submitted from your site, to see where visitors give up before buying.
Identify customers
Tell Clakta who the visitor is with clakta.identify(), so their journey follows the person instead of the browser.