What does a conversion actually require?
Strip the concept to its parts and it is surprisingly simple. A conversion is an event: someone completed a purchase, submitted a form, signed up, booked a call. To count it you need to know that the event fired and, usually, which page or session context it fired in. None of that requires knowing who the visitor is, storing an identifier on their device, or recognising them next week.
Cookies entered the picture because advertising platforms wanted more than the count -- they wanted to connect the conversion to an ad click from days earlier, on another site, possibly on another device, and to build an audience profile around it. That attribution ambition is what drags in cookies, consent banners, and everything that comes with them.
If your question is "does my site convert, and which channels drive it?" -- the analytics question rather than the ad-network question -- cookieless measurement answers it cleanly.
How does cookieless conversion tracking work?
A cookieless tool counts a conversion the same way it counts a pageview: the browser fires a small request when the goal happens, the tool increments the relevant counters -- total conversions, conversions per page, per referrer source, per campaign -- and stores nothing about the individual. Within a single session, the source that brought the visitor is still known (the referrer and any UTM parameters arrived with them), so "12 signups from organic search, 8 from the newsletter" works without any persistent identifier.
In practice you define conversions in one of two ways:
- Page-based goals: reaching
/thank-youor/order-completecounts as a conversion. Zero extra code -- if your flow ends on a distinct URL, you already have conversion tracking. - Event goals: a small snippet fires on a button click or form submit that does not change the URL. One line of JavaScript on the action you care about.
Revenue works the same way: the purchase event carries an order value, and the tool aggregates totals and averages -- €4,200 from 38 orders this month, €1,900 of it from organic search -- without a customer profile anywhere in the system. This is exactly how TrackTrendy's goals and revenue tracking are built, and why they need no banner in front of them.
What do you give up compared to cookie-based tracking?
Be clear-eyed about the trade:
Cross-session attribution. A visitor who discovers you on Tuesday and buys on Friday is two sessions with no link between them. The conversion credits Friday's source. Over a whole month this evens out more than you might expect -- Tuesday's channel gets credited for the conversions of other people it drove on their buying day -- but individual journey stories are gone.
Cross-device journeys. Phone research, laptop purchase: two visitors as far as the data is concerned.
Remarketing audiences. No profiles means no audience lists to hand to ad platforms. (Ad platforms build those from their own click data anyway.)
What you get back: every conversion from every visitor, including the 20-40% who would have declined a consent banner and the blocker users GA4 never saw. For most small businesses that trade is strongly positive -- a complete count of real conversions beats a fractional count with elaborate attribution, especially when the fraction is biased. We looked at that bias in why your GA numbers are wrong.
A practical setup, step by step
Here is the whole process for a typical small business site:
- 1. List your conversions. Most sites have two to five that matter: purchase, contact form, signup, quote request, phone click.
- 2. Prefer thank-you pages. Where a flow can end on its own URL, let it -- page goals are the most robust kind and need no code.
- 3. Add event snippets where URLs do not change. One line on the submit handler or button click.
- 4. Pass the order value on purchases so revenue reporting works, not just counts.
- 5. Tag your campaigns with UTM parameters. Conversion-per-campaign reporting is only as good as your links. (Guide coming later in this series.)
From there, the report you check weekly is: conversions by source, conversion rate by landing page, revenue by campaign. Those three views answer most marketing questions a small business actually has.
When would you still add a cookie-based tool?
If you spend seriously on Google or Meta ads and need their platforms to optimise bidding against conversions, you will end up running their pixels with a consent banner for that purpose. That is an advertising-platform requirement, not an analytics one -- and it can sit alongside cookieless analytics that remains your source of truth for what actually happened on the site.