Skip to content
← Back to writing
Tracking·November 17, 2026·7 min read

Google Tag Manager and the other tag managers: when moving is worth it

Most sites that use a tag manager use Google Tag Manager. It costs nothing, it has a template for almost every tag a marketing team asks for, and it is the tool most people who do tracking learned first.

There are others. Tealium, Adobe Experience Platform Tags, Segment, Matomo and Piwik PRO come up when a company grows, signs a bigger software contract, or starts caring where its data is stored. Each one handles something Google Tag Manager handles badly or not at all. None of them is a better default.

What follows is what each one is for, what it costs, and when moving is worth the work.

What every tag manager does

Take the names away and they all do four things. They hold the tags, the snippets that send data to analytics tools and ad platforms. They decide when each tag fires, from rules about the page and what the visitor did. They read values from the page and from the data layer. And they let you test a change before visitors see it, then publish it as a version you can roll back.

The words change from tool to tool. Google Tag Manager has tags, triggers and variables. Adobe has rules, events and data elements. Tealium reads from one data layer object on every page and loads tags against it.

The work underneath is the same in all of them. That matters when you think about switching.

Google Tag Manager

It is free, and it is the default for good reasons. It has built-in tags for GA4 and Google Ads, a gallery of community templates for most other platforms, and Preview mode, which lists every event on a page with the tags that fired and the conditions that did not match. It works with Google's consent mode, so tags can wait for a visitor's choice.

The limits show when more people work in the same container. The free version allows three workspaces at a time, the default one and two more, so a fourth person with a separate change waits. There is no approval step either. Anyone with publish rights can push a change live.

Tag Manager 360, the paid version sold through Google Marketing Platform, adds approvals, unlimited workspaces and zones. Zones let another team or an agency run its own container on part of your site, with limits on which tags it can fire.

Server-side tagging is the cost people miss. The server container is free, but the servers it runs on are yours to pay for. Google suggests at least three of them for live traffic and puts each one at about $30 to $50 a month, before logging and network charges.

None of that is a reason to leave. Set user permissions properly and keep a written tracking plan. With no approval step, the plan is the only record of what the container is supposed to do.

Tealium iQ

Tealium is the usual choice for a large company with a long list of vendors. Its tag manager, iQ, is built around a single data layer object on every page, and the tags read from that object instead of from the page. It has a large catalogue of vendor integrations. Its server-side product, EventStream, sends the same events to vendors from Tealium's servers instead of the visitor's browser.

There is no public price. It is sold on contract, often with Tealium's customer data platform. Companies choose it for control: who can change what, and where each piece of data is allowed to go.

If your site has a few dozen tags and a team of three, you would be paying for controls nobody uses.

Adobe Experience Platform Tags

Adobe's tag manager was called Launch, and before that DTM. It is now Tags in Adobe Experience Platform. Adobe includes it for Experience Cloud customers at no extra charge and does not sell it on its own, so in practice you use it because you already pay for Adobe Analytics or Adobe Target.

It does the same job with different words: rules made of events, conditions and actions, data elements for the values, and extensions where Google Tag Manager has templates. Changes move through development, staging and production before they go live, which gives you the approval step the free Google Tag Manager lacks. Adobe's server-side option is called event forwarding. Ask your Adobe account team what your licence includes.

If the site reports in Adobe Analytics, use Adobe's tags. Running Google Tag Manager beside them means two places to check every time a number looks wrong.

Segment

Segment works the other way round. A developer installs its library and writes a call for each event: a product view, a sign-up, a purchase. Segment then passes each event on to the analytics tools, ad platforms and warehouse you have connected. Many of those destinations receive the event from its servers. Some still need their own code in the browser.

That suits a product team that wants one definition of each event for every tool, and has developers to write the calls. It suits a marketing team less. Connecting a new platform is a setting, but adding a new event is a code change and a release.

It is priced by monthly visitors: free up to 1,000, then $120 a month for 10,000 on the Team plan, rising from there.

Matomo and Piwik PRO

These two come up when the question is where the data lives. Both are analytics suites built around privacy rules, and both include a tag manager.

Matomo's tag manager is open source and free when you host Matomo yourself, with no limit on tags. Matomo's hosted cloud includes it on the Business plan. Piwik PRO ended its free plan in early 2026. Its Business plan, which includes the tag manager, starts at about €35 a month.

Choose one of these when the analytics has to run on your own servers or stay in a particular country, and someone has agreed to look after it. Most of the tags you load will still belong to ad platforms that send data to their own servers. The tag manager alone does not decide where your data goes.

Shopify checkout, where Google Tag Manager does not run

One case is not a choice. On a Shopify store, the checkout pages do not run the theme's code, so a Tag Manager container installed in the theme stops at the cart. Anything that records the checkout runs as a pixel in the store's customer events settings, in a sandbox that cannot see the page.

Shopify describes Tag Manager inside a custom pixel as an unsupported setup, and Tag Assistant cannot see tags inside the sandbox. Google points stores to its Google & YouTube app for the Google tags. Plan the checkout events in Shopify's terms first, then decide what Tag Manager still does on the rest of the store.

The options side by side

Tag managerWhat it costsChoose it when
Google Tag ManagerFree. Tag Manager 360 is paid. Server-side needs servers you pay for.Almost always. It is the default.
Tealium iQSold on contract, no public priceThe vendor list is long and changes need tight control
Adobe Experience Platform TagsIncluded with Adobe Experience CloudThe site already runs Adobe Analytics or Adobe Target
SegmentFree to 1,000 visitors a month, then from $120 a monthDevelopers own the tracking and want one event stream
Matomo Tag ManagerFree if you host Matomo yourselfThe data has to stay on your own servers
Piwik PRO Tag ManagerFrom about €35 a monthYou want a hosted suite built around privacy rules

What moving to another tag manager takes

The tool is the easy part to move. The hard part is the data layer and the list of events, and those carry over to any tag manager if they were built properly.

A site that pushes a clean purchase event, with the order ID, the value and the items, can be connected to Tealium, Adobe or Segment in a few days. A site where every tag scrapes the page for its own copy of the price has to be rebuilt in all of them, including a fresh Google Tag Manager container.

So if you are weighing a move, fix the data layer first. You need that work either way, and it is what makes the move cheap.

Learning Google Tag Manager

Whatever a site ends up on, Google Tag Manager is where most people learn this work, and the skills carry over. A trigger with a condition is a rule in Adobe. A Data Layer Variable is a data element. Reading Preview mode to find out why a tag did not fire is a habit you use in every one of these tools.

The hard part is finding somewhere to practise. Watching a course does not stick until you build something, and the containers most people can reach belong to live sites, where a mistake costs real data.

I built Tag Practice for that. It has 28 hands-on exercises in a workspace laid out like Tag Manager, with the same menus, tag types, triggers and variables, and a practice shop to test your work on in Preview. Each lesson gives you one task. When you check it, the exercise plays the scenario through, including the awkward cases like a click on the icon inside a button or a form sent empty, and tells you what went wrong and why. It costs $49, paid once, plus any sales tax. You can see all 28 lessons before you buy.

If you would rather have the tracking set up for you, that is my website tracking work.

Choosing a tag manager starts with the data layer and the tracking plan, then the tool that fits the contracts and the people you already have. Learning one starts in Google Tag Manager, by building things in it.

Free Checklist

Tag Audit Checklist

21 Checks Before You Trust the Numbers

Run this against your own site before you compare GA4 to an ad platform again. Each item is a yes or a no. Every no is a reason the numbers disagree.

Email only. No other fields.

Learning Google Tag Manager? Tag Practice has 28 hands-on exercises in a workspace laid out like Tag Manager, with a practice shop to test them on. See Tag Practice →

Related reading

← Back to writing