How to choose a tag manager

A tag manager lets someone add or change tracking and marketing pixels on a site through a web interface instead of asking a developer to edit source code and wait for a deploy. Almost every site with more than one analytics or ad pixel benefits from one; the question is rarely whether to use a tag manager, but which one, and whether client-side tagging in the browser is still enough for what you need to measure.

Start with the one that is free

Google Tag Manager costs nothing, covers web, app and server-side containers, and ships a template gallery covering most vendors you are likely to fire a tag for. For the majority of sites — one property, a handful of marketing pixels, a team that already lives in the Google ecosystem — it is the default, and there is little reason to pay for anything else. The decisions below are really about when GTM alone stops being enough.

Client-side vs. server-side

Every tag manager here can fire tags in the browser. Browser tracking prevention, ad blockers and cookie restrictions have made that alone less reliable than it used to be, which is why server-side tagging — running the tag container on a server you control instead of the visitor's browser — has become a real decision point rather than a niche one.

• Google Tag Manager's server container runs the same tags server-side, but you host and pay for the infrastructure yourself, typically on Google Cloud.
• Stape exists specifically to remove that hosting burden: it manages GTM server containers for you and adds prebuilt gateways to Meta, TikTok, Snapchat and Google's own conversion APIs, so first-party data reaches ad platforms without you building the plumbing.
• Addingwell, built by consent-platform vendor Didomi, takes the same server-side foundation but is designed around one specific problem: making sure a visitor's consent choice travels with every event through the pipeline, not just at the browser.
• Tealium iQ and Adobe Experience Platform Tags both support client- and server-side delivery as part of a larger enterprise data platform, rather than as a standalone hosting decision.

If you are not sure whether you need server-side tagging yet, you probably do not — it adds real engineering and hosting cost for a specific resilience and privacy benefit. Revisit it when ad-platform conversion tracking starts visibly under-reporting.

Free and open source vs. bundled and enterprise

Matomo Tag Manager is free and unlimited with self-hosted Matomo Community, under the same open-source licence as Matomo's analytics product — a genuine option if you are already self-hosting Matomo and do not want a second vendor relationship for tagging. On Matomo Cloud, it is bundled into the Business plan rather than priced separately.

At the other end, Tealium iQ and Adobe Experience Platform Tags are not sold as standalone tag managers at all. Tealium iQ is the tagging layer of Tealium's Customer Data Hub, and Adobe's product ships as an included feature for organizations already on Adobe Experience Cloud. Neither publishes a price list; you get access by buying the platform around it. Choosing either one is really a decision about the platform, not the tag manager specifically — do not evaluate them as if they compete on tagging features alone.

Governance: how many vendors, how many people touch it

A tag manager that works fine for three tags and one person managing them can become a liability at fifty tags and a dozen contributors. What changes at scale:

• A standardized data layer. Tealium centers on this explicitly — every tag reading the same, governed definitions of customer events, rather than each integration inventing its own variable names.
• Approval workflows and environments. Adobe's Enterprise Publishing and Tealium's environment management let large teams stage and approve changes before they go live sitewide; GTM's workspaces and version history cover smaller-team needs but were not built for formal sign-off chains.
• Auditing what each vendor tag actually collects. Tealium explicitly markets a governance feature for this; it matters once "which of our forty tags is reading this field" becomes a real question, often triggered by a privacy audit rather than a marketing request.

Consent, front to back

Consent handling is worth checking regardless of vendor. Ask whether a declined visitor's tags are simply blocked client-side, or whether the consent state is actually attached to the event as it moves server-side — the difference matters once you add a server container, since a poorly wired server-side setup can silently ignore a browser-level opt-out. Addingwell's whole pitch is solving this specific gap; it is worth understanding even if you do not buy that product, because it describes a failure mode any server-side setup can hit.

A shortlist by situation

• If you have no strong reason to look elsewhere, start with Google Tag Manager — it is free and covers most needs.
• If you want server-side tagging without managing your own cloud hosting, look at Stape.
• If consent state getting lost between browser and server is your specific worry, look at Addingwell.
• If you already self-host Matomo, add Matomo Tag Manager rather than a separate vendor.
• If you are coordinating dozens of vendor tags across a large organization and need governed data-layer definitions, look at Tealium iQ.
• If your stack is already built on Adobe Experience Cloud, use Adobe Experience Platform Tags rather than adding a second tag manager.

Questions to ask

1. Does the free tier or base plan cover server-side containers, or is that a separate cost?
2. If we add a server container, who hosts it, and what does that hosting cost on top of the tag manager itself?
3. Does a visitor's consent choice actually block server-side firing, or only the browser-side script?
4. What does an approval workflow look like before a tag change goes live on the production site?
5. For Tealium or Adobe: is tag management available on its own, or does adopting it commit us to the wider platform?

Common mistakes

The most common mistake is treating tag management as a set-and-forget install: containers accumulate unused tags for years, each one a small performance and privacy liability nobody is assigned to clean up. The second is adding server-side tagging before there is a concrete problem it solves — it is real engineering overhead, not a free upgrade. The third is assuming event tracking fired through the tag manager is automatically accurate; a tag manager fires what you configure, faithfully, including mistakes, so the underlying data layer still needs someone who owns its definitions.

For head-to-head detail, see Adobe Experience Platform Tags vs Google Tag Manager and Google Tag Manager vs Tealium iQ, or browse every tool in this category.