Shopify
OOONO
Shopify across markets
Shopify development across markets with theme changes, tracking and ongoing improvements to the store.
Read about my work for OOONOVisit ooono.comConsent Mode v2 is the link between your cookie banner and your tracking, and without it you lose both data and features in Google Ads. I test hands-on in the browser what really happens with and without consent, then fix the technical side; I have done that review many times across 400+ projects.

star reviews
Read every reviewA cookie banner is only the visible layer. Beneath the surface, the user's choice has to be translated into signals that the tag setup actually obeys, and that is where things most often go wrong. If the banner is a detached element with no link to GTM, nothing happens no matter what the user clicks. And a banner that blocks everything by default was configured, not designed; someone just switched it all off and moved on.
Consent Mode v2 is Google's format for exactly those signals. On refusal Google receives anonymous pings without identifiers, used to model conversions, and on consent measurement runs normally. The format is also a requirement if you want remarketing and full conversion data in Google Ads for European users.
The rules do not have to mean blindness. Anonymous, cookieless statistics are allowed without consent when they cannot recognise individuals, and they give a reliable picture of traffic and content.
I am happy to set up such a base measurement next to the consent-based one. That gives you a point of comparison, and you can see what share of your visitors actually decline; few people know that number for their own site.
Consent Mode v2 is Google's standard for telling Google's tools what the user has consented to. It works with four signals: two for storing cookies for statistics and advertising, and two newer ones for using data for ad purposes and personalisation. Your cookie banner sets the signals based on the user's choice, and GA4, Google Ads and GTM obey them.
The standard became urgent when Google made it mandatory for advertisers who want remarketing and full conversion features for users in the EU. Without correctly configured Consent Mode v2 you lose functionality in Google Ads, on top of the data already lost when consent is missing or the banner is wired wrong.
Every Danish site using Google's tools with visitors from the EU is in the target group; in practice that means nearly everyone advertising or measuring with GA4. The gain is biggest for webshops and lead businesses, where conversion data directly steers ad budget, and where Google's modelling on refusals can fill part of the gap.
I set up Consent Mode v2 in your existing GTM and with your existing cookie banner wherever at all possible. Afterwards I test each signal in the browser in both states, with consent and without, and document the result so you can show how the setup behaves.
Consent Mode v2 consists of four signals, each of which can be set to granted or denied. The first two already existed in the first version. ad_storage controls whether cookies and similar may be stored for advertising, and analytics_storage controls the same for analytics, for example the cookies GA4 uses to recognise a returning visitor. When analytics_storage is denied, GA4 stores no cookies, and the same goes for Google's ad tags when ad_storage is denied.
Version 2 added ad_user_data and ad_personalization. ad_user_data decides whether user data may be sent to Google for advertising purposes, such as the hashed customer details in enhanced conversions. ad_personalization decides whether data may be used for personalised advertising such as remarketing. The cookie banner therefore has to be able to set all four signals, and each signal has to follow the user's choice in the right category.
In practice the signals are tied to the categories in the cookie banner. Statistics typically controls analytics_storage, while marketing controls the three advertising signals. A classic error is that only ad_storage follows the marketing category, while ad_user_data and ad_personalization stay on denied. Everything then looks right in the banner, while Google Ads is not allowed to use the data for audiences and enhanced conversions. I always check that wiring signal by signal in Tag Assistant.
When a visitor declines cookies, the conversion does not disappear; it just becomes invisible to Google. Conversion modelling is Google's way of filling part of that gap. Based on the visitors who consented, and the cookieless pings Google's tags send on refusal in the advanced variant of Consent Mode, Google estimates how many conversions probably happened among those who said no.
Modelled numbers are estimates at an aggregate level. They do not show individuals and cannot be used to see which customer bought what. In Google Ads, modelled conversions are included in the regular conversion figures. In GA4 it is called behavioural modelling, and it requires the reporting identity to be set to Blended.
Modelling is not guaranteed. It needs a certain amount of traffic and consented data over a period before Google switches it on, so a smaller site may not get it at all. Nor is it on its own an argument for choosing advanced over basic; that choice is also about what your lawyer thinks of the cookieless pings. But once you have decided on advanced, I make sure the pings and signals are set up correctly, so the modelling has something to work with.
I take on Consent Mode and cookie banner work for businesses all over Denmark. Everything happens in the browser, in GTM and in the banner's admin panel, so it makes no difference whether the site is run from Copenhagen, Aarhus, Odense or Aalborg; I just need access.
I am based in Glostrup in the Copenhagen area myself and happily take an in-person meeting with nearby businesses when a review needs presenting to several people in the organisation. The great majority of engagements run fully remote, though, with a video kickoff and status updates by email.
The typical job is well bounded: a review of the current setup, fixes for what was found, and a documented handover. Precisely because the scope is manageable, the job suits a freelancer well; you pay for concrete hours spent hands-on in the setup rather than for an agency programme with many meetings. Write to hello@mikkeltschentscher.dk and you will have an answer the same day.
The most widespread error is scripts firing regardless of consent. Either because they are hardcoded into the site outside the tag manager, or because embedded content such as videos, maps and chat widgets sets its own cookies the moment the page loads. The banner can look perfectly correct; it simply does not control those parts.
Number two is the asymmetry between accepting and declining: one big button for yes and a hidden settings page for no. That conflicts with the requirements that consent be freely given and as easy to refuse, and it is a poor experience users can see through anyway.
Number three is consent that gets collected but never arrives. The banner registers the choice, but the signal is not translated into Consent Mode, or tags in GTM lack their consent conditions, so everything runs regardless. That error is invisible from the outside and requires exactly the browser test I start with.
A final note on roles: I am not a lawyer and issue no legal stamps of approval. My contribution is making the technology do what your policy promises, and documenting what gets set when, so a lawyer or DPO has a precise basis to assess from.
Concrete deliverables, not a report of recommendations someone else has to find time for.
Browser testing of what gets set when, with and without consent, collected in a list of findings and fixes.
All four consent signals wired from banner through GTM and on to Google, verified signal by signal.
An updated list of the cookies the site actually sets, as the basis for your cookie policy.
Anonymous statistics alongside the consent-based ones, so you can see the refusal share and have numbers to compare with.
Shopify
Shopify across markets
Shopify development across markets with theme changes, tracking and ongoing improvements to the store.
Read about my work for OOONOVisit ooono.comWordPress
Design focused on conversion
A new WordPress website for private and business customers with design, tracking and a simpler booking flow.
Visit 3x34.dkNext.js
Courses for companies and job seekers
A Next.js course platform with course listings, registration and tracking for companies and job seekers.
Visit bigum.coFour steps. You know what happens when, and you can stop after any of them.
Using preview mode and the network log, I work out which tags fire, which fail, and where the same purchase gets counted more than once. The result is a concrete list of what has to go and what is missing.
The container is rebuilt with consistent naming and a clean data layer, so anyone can open it a year from now and understand what happens. Old tags are archived rather than deleted, so nothing is lost.
I set up a server container on your own subdomain and wire in consent mode, so the consent choice controls what gets sent. Conversion tracking for Google Ads and Meta moves over with it.
For a period after launch, I compare orders in your backend with the numbers in GA4 and the ad platforms. Deviations are explained in writing, so you know how much weight the numbers can carry.
It depends on the starting point. The price is affected most by which cookie banner you have, how many domains and languages need covering, and how much of the existing setup needs fixing. Tell me which banner and which Google tools you use, and you get a concrete quote with a same-day reply.
ad_user_data and ad_personalization are the two signals Consent Mode v2 added. ad_user_data indicates whether the visitor has consented to personal data being sent to Google for advertising purposes, and ad_personalization indicates whether data may be used for personalised advertising such as remarketing. Both are set by the cookie banner, typically from the marketing category. Since March 2024 Google has required consent signals for visitors in the EEA if advertisers want to use their data for audiences and measurement in Google Ads.
Conversion modelling is Google's estimate of the conversions that cannot be measured directly because the visitor declined cookies. Google uses patterns from the visitors who consented to calculate how many conversions probably happened among the rest. The numbers are aggregate estimates without individuals, and they require a certain amount of data before they appear.
Usually through your cookie banner. Common consent management platforms, so-called CMPs such as Cookiebot and Cookie Information, can pass the consent signals on to Google's tags. First a default state is set, typically denied, which applies until the visitor has chosen. When the visitor accepts or declines, the banner updates the signals. It is usually all wired together in Google Tag Manager. Finally you check with Google's Tag Assistant that the signals actually change when someone clicks yes or no. I always run that test, signal by signal.
Yes. The principle is the same, but the setup differs. On WordPress, Consent Mode v2 is typically wired up through the cookie banner's plugin or through Google Tag Manager. On Shopify it goes through the banner's app together with Shopify's own customer privacy settings. On both platforms I work with the banner you already have wherever at all possible.
Not automatically. Consent Mode is Google's standard: Google's own tags follow the signals by themselves, but Meta's pixel and most other platforms' tags do not. They have to be controlled another way, typically with consent conditions in Google Tag Manager or by having the cookie banner block them until the visitor has said yes. It is one of the places where a setup that looks correct still sends data without consent.
If you use Google Ads or share GA4 data for advertising to users in the EEA, Google has required Consent Mode v2 since March 2024. Without it you lose the ability to target and measure ads for those visitors. For plain statistics without advertising it is not a Google requirement, but consent still has to be handled correctly.
Only if the site sets no cookies or similar technology that is not strictly necessary. As soon as there is analytics, ad pixels or embedded videos that track, consent has to be collected. It can, however, be done with a banner that gets in the way far less than most.
In the basic variant Google's tags do not load at all before consent, and Google receives nothing on refusal. In the advanced variant anonymous cookieless pings are sent on refusal, which Google uses to model conversions. Advanced gives a better data foundation, but the choice between the two should be made deliberately, ideally with your legal adviser.
Yes, all over Denmark. I am based in Glostrup near Copenhagen, and jobs for businesses in Aarhus, Odense and Aalborg are handled remotely with screen sharing; the setup lives in the browser and in GTM anyway.
Not automatically. Consent Mode v2 is a technical standard for passing consent signals to Google; it replaces neither a correct cookie banner, an accurate cookie policy nor your other GDPR obligations. I make sure the technology does what it should and document it, but the legal assessment has to come from a lawyer or DPO.
It depends on the need, and I have no partner deals colouring the recommendation. With one site and few third parties a simple solution is plenty; with many domains, languages and documentation requirements a larger platform makes sense. If you already have a banner that can send Consent Mode signals, we usually keep it.
Some, yes; visitors who decline may not be measured individually, and a correct setup has to reflect that. In return the remaining data becomes something you can safely build decisions on, Google's modelling fills part of the gap, and a cookieless base measurement can show the overall picture.
Yes, that is a bounded and quick job. I go through in the browser what gets set when, both with and without consent, and collect the findings in a list with recommendations. Most people are surprised by at least one item.
Your next step
Tell me about your project. I’ll get back to you with questions, options and a concrete next step.