Cookie, cookieless or consent first: which would you run, and why?

by•

Tally lets each site choose how it counts visitors, and each choice gives something up. Here's the trade-off as plainly as I can put it:

🍪 Cookie Mode

One first-party cookie, kept for a year.

Tally recognizes returning visitors across days and remembers the source that first brought them, even when they come back another way. So a sale made a week later can still be traced to that first visit.

⚠️ What it can't do: Follow the same person across browsers or devices, or after they clear cookies.

In the EU and the UK, a cookie like this usually needs consent.

🔒 Cookieless Mode

No cookie at all, so there's nothing for a cookie banner to cover from Tally's tracking.

Each visitor is counted once per day, using a hash with a salt that changes daily and is then deleted. Nobody can be followed from one day to the next.

⚠️ What it can't do: Tell you whether today's visitor came yesterday too, or connect visits that span days.

🤝 Consent First

Cookieless for everyone until your banner reports a yes, then a cookie from that visit on.

You get every visitor counted, and returning visitors from the moment they consent.

🛡️ Privacy in Every Mode

In every mode, the IP address is used to find the city and then dropped. It's never stored.

💬 So I'm curious:

Which would you pick for your site, and why?

🇪🇺 If you sell in the EU or the UK, how do you handle consent today?

And if you've moved away from cookies, what did you lose that you miss?

5 views

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.