Segment vs. Tag Managers
Tag managers, also known as Tag Management Systems (TMS), were a popular solution before the mainstream adoption of mobile apps. They primarily helped Digital Analytics and Online Marketers manage web tags or “beacons” on a website.
In addition to ad networks, today’s data-driven businesses use a variety of tools to optimize their product and marketing spends. In order to a/b test copy, nurture sales leads, email customers, and provide fast support, businesses integrate variety of analytics and marketing tools. Segment makes it easy to install, try, and use them all. Tag managers primarily focus on ad networks, and can’t support modern tools without extensive customization.
Rather than “firing and forgetting,” Segment takes a data-centric, deliberate approach to destinations. You don’t need to set up special parameters for each tool – Segment does that for you. Segment structures your data so we can understand what it is, and can translate it correctly for each destination we send it to. Segment works because all of these tools operate on the same customer data: who is on your app and what are they doing. Segment collects this data once, then translates and sends it to every tool you use. Because Segment also archives the data, Segment can replay your historical data into new tools, and send your raw data to a data storage solution for later analysis.
|Data Storage||Stores clickstream data in one comprehensive set; replays historical data into new tools; exports data into SQL databases and internal systems||Does not store data; cannot load historical data into new tools; cannot translate and load historical data into SQL databases|
|Device Compatibility||Tracks user events in mobile, web, and server environments. Server libraries include Python, Node, Ruby, PHP, .NET, Java, Clojure, Go, Rust and Xamarin||Operates on web; limited functionality on mobile; does not support server destinations|
|User Interface||Delivers sleek user experience; automatically translate data for new tools when you enable a destination||Requires that you configure settings and rules for each pixel to fire|
|Tool Integrations||Fully integrates analytics, advertising, email, customer support, marketing automation, usability tracking, error testing, and CRM tools with the flick of a switch||Manages ad pixels; requires custom engineering work to integrate any other complex tool|
Every organization’s data stack and business requirements are unique. Segment also works well in tandem with a tag manager. For example, Segment sends data directly to the Google Tag Manager (GTM) destination.
While you can use Segment’s Analytics.js library through a tag manager, Segment doesn’t recommended this for a few reasons:
A hybrid approach makes it difficult to determine the root cause of technical problems, and complicates troubleshooting. Segment cannot guarantee destination compatibility in a “hybrid” Segment-tag-manager installation, and cannot guarantee support on these installations. All QA and regression testing assumes a native installation of Analytics.js on the page.
One of Segment’s main charters is to not lose data. Our system and cloud infrastructure is designed to ensure that data loss does not happen. If you implement the entry point of data capture (Segment’s libraries) using a Tag Manager, you introduce risk of data loss and make it difficult or impossible to troubleshoot.
This implementation behind a tag manager can introduce major delays and performance issues, which can cause delays with events that need to occur early in your funnel.
The biggest challenge is around triggering cascading events. Browsers are notorious for dropping calls. When you use a TMS to initiate Segment events you are introducing a second point of failure for those events.
This page was last modified: 16 Feb 2023
Questions? Problems? Need more info? Contact Segment Support for assistance!