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.comA Google Tag Manager consultant needs to do more than create tags; half the work lives in the data layer and in the code on the site. I have been a developer since 2010, so I can both clean up the container and write the data layer it should read from.

star reviews
Read every reviewMany GTM containers have grown through years of campaigns and changing agencies, and nobody dares delete anything because nobody knows what is still in use. That is how an undocumented container rots, one forgotten tag at a time. I work out what actually fires and pause the rest, so there is always a way back.
Afterwards the remaining tags get a fixed naming convention, so their purpose can be read without opening them. That detail decides whether the container is still workable in two years.
What decides whether a GTM setup is robust is where the events come from. Automatic click triggers guessing at CSS classes snap when the design changes, and the error only shows up weeks later in the reports.
Instead I define a data layer with fixed names and fixed fields that the site itself sends. Because I am a developer, I can write the implementation myself or hand your team a precise specification.
Google Tag Manager, GTM for short, is a free Google tool that gathers all your tracking in one place. Instead of putting scripts from GA4, Google Ads, Meta and other platforms directly into the site's code, you install GTM once and then manage every tag from a central container with version history and a test environment.
The importance of a proper GTM setup has grown in recent years. Consent rules require tags to fire only for users who said yes, and that can only be managed reliably when all tracking flows through one system. At the same time GTM has become the gateway to server-side tracking and Consent Mode v2, making the container the backbone of your entire measurement.
Anyone with a website who advertises or wants to understand their visitors needs it: webshops, lead businesses, SaaS and media. The need for help typically appears when the container has grown into something nobody has an overview of anymore, or when the GA4 numbers stop matching reality.
My setup starts with cleanup and naming, continues with a defined data layer, and ends with GA4, Google Ads and Meta connected with consent management via Consent Mode v2. Everything is documented, so the container can be maintained by you or the next person who gets access.
The benefits of Google Tag Manager really show in everyday work. Once a data layer is in place, a new conversion, a campaign pixel or new measurement of clicks and forms (event tracking) can be set up in the container without waiting for a site release. That saves developer time, and it means marketing can act while the campaign is still running. The same triggers and variables can be reused across tags, so an event like a purchase only has to be defined once.
Another benefit is that GTM makes ecommerce tracking and consent consistent. When the purchase event comes from the data layer, GA4, Google Ads and Meta get the same products and the same order value, instead of each platform reading its own version. Each tag can also carry consent conditions, so it only fires when the visitor has said yes to the right category. That is far easier to check in one place than across ten different scripts.
For platforms outside Google there are ready-made templates in GTM's Community Template Gallery, so you can often avoid pasting in raw code. The benefits do assume the container is kept in order, though: a container without naming and documentation gives you the same problems as scripts scattered through the code, just gathered in one place.
Google Tag Manager has the tools built in that you need to change tracking without gambling with it. Changes are made in a workspace, where they do not affect the site until they are published. Several people can work in separate workspaces at the same time, and GTM flags it if two changes hit the same tag, so one does not quietly overwrite the other.
Before anything is published, it is tested in preview mode via Tag Assistant. The site opens with the new changes active only for you, and you can see every event, which tags fired, which did not, and what values the variables held. This is also where you check consent: does the tag fire only after a yes, and is it held back after a no?
Every publish is saved as a version. If the version gets a name and a short description of what changed and why, the history becomes a logbook the next person can use. If something goes wrong, an earlier version can be published again within minutes. I recommend a fixed routine: the change is made in its own workspace, tested in preview, saved as a descriptive version and only then published.
GTM work requires access to the container and a video call, not a physical visit. So I help businesses across all of Denmark, from Copenhagen and Aarhus to Odense, Aalborg and everywhere outside the big cities, even though my own base is in Glostrup on the outskirts of Copenhagen.
An engagement usually starts with you granting me access to the container and the GA4 property, after which I do a short review and give a concrete quote. Smaller jobs such as a single conversion setup are often done in a few days; a full cleanup with a data layer takes longer, and you get a time frame before we start.
As a freelance consultant I am the one on the job from the first email to handover. That means shorter communication lines than at an agency and a price without project management overhead. And the documentation means you never depend on me; everything sits in your own accounts.
Call +45 22 51 31 79 or write to hello@mikkeltschentscher.dk if you want a look at your container. You will hear from me the same day.
The pattern is the same almost everywhere. A tag gets created for a campaign, the campaign ends, and the person behind it has moved on. Nobody knows whether the tag is still used, so it stays. Repeat that for five years across changing agencies, and the container holds dozens of tags, many of which have not fired in years.
The consequence is more serious than a little extra load time. When nobody can survey the container, nobody dares change it, and new measurement gets layered on top instead of built into the structure. The mess reinforces itself, and the risk of double counting and consent errors grows with it.
Fortunately the cleanup is systematic work. GTM's version history and GA4's event reports together show fairly precisely what is active. Everything inactive gets paused with the option to undo, the rest gets named after a fixed pattern, and finally a short guide gets written so the next change can be made without fear. It is not glamorous work, but it is the investment in your measurement that lasts longest.
Concrete deliverables, not a report of recommendations someone else has to find time for.
Inactive tags paused rather than deleted, so the cleanup can be rolled back if something turns out to be in use.
A pattern for tags, triggers and variables, so anyone can read what they do without opening them.
Fixed event names and fields, implemented by me or handed over as a precise recipe for your developers.
Conversions on what matters, internal traffic filtered out and data retention set to the longest permitted period.
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 job. The price is driven mainly by the size and state of the container, by whether a data layer needs building from scratch, and by how many platforms and sites are involved. Give me read access to the container and I will come back with a concrete quote, with a same-day reply.
GA4 is the analytics tool that receives and reports on data. Google Tag Manager is the distribution system deciding which data gets sent to GA4 and to other platforms like Meta and Google Ads. They work together but solve different problems, and errors can occur in either link.
Event tracking is measuring specific actions on the site, such as clicks on a button, a submitted form, a download or a purchase. In GA4 everything is in principle an event, and GA4 measures some of them by itself, such as page views, scrolls and clicks on outbound links. The rest is typically set up in Google Tag Manager, preferably from a data layer, so measurement does not break when the design changes. Ecommerce tracking is event tracking of product views, the cart and purchases.
The GTM script itself is light; it is the tags the container loads that cost. Each tag can fetch its own script from a third party, so a container full of forgotten tags, chat widgets and testing tools can make the site heavier. The fix is to review the container, remove what is not used and consider moving some of the measurement to a server container.
Yes. Based in Glostrup near Copenhagen, with clients in Copenhagen, Aarhus, Odense, Aalborg and many smaller towns. GTM work happens over screen sharing, so geography plays no role in the quality.
GA4 can be used responsibly when the setup is right: consent collected before cookies are set, Consent Mode v2 configured, Google's data processing agreement accepted, and sensible settings for retention and sharing. I am not a lawyer and do not give legal assessments, but I make sure the technical side is in place and documented. If you prefer data kept in the EU, I am also happy to set up alternatives such as Matomo or Plausible.
Usually yes. Many setups were done in a rush when Universal Analytics shut down and have not been looked at since. A review typically reveals missing conversions, unfiltered internal traffic and a data retention period left on the default.
Yes, that is the whole method. I work in a workspace, test in preview before publishing and pause tags rather than delete them. Should something turn out to be in use after all, it can be reactivated in a minute.
Only the people who work with tracking, and as few as possible with the right to publish. GTM's user permissions have four levels on the container: read, edit, approve and publish. Always keep at least one person from your own company as administrator of the account. An agency or a freelancer can easily be given edit or publish rights, but the account should be owned by you, so access does not disappear when the collaboration ends. Review the user list once a year and remove people who have left.
Happily. I typically spend half a day walking through the naming, the data layer and the workflow together, so your own people can make changes confidently going forward. It is often the best-spent part of the whole job.
Yes. I have set up Matomo, Plausible and similar for clients where EU data storage weighed heavier than Google's reports. The recommendation depends on your needs, not on partner deals; I have none.
Your next step
Tell me about your project. I’ll get back to you with questions, options and a concrete next step.