What is the difference between Segment and 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. We collect your data, and understand what it means so we can map it to each destination correctly. You don’t need to set up special parameters for each tool – we do that for you. 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 we store the data, we also have the ability to replay your historical data into new tools and give you acccess to your raw data in a SQL data warehouse.
|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 data into SQL databases|
|Device Compatibility||Tracks user events in mobile, web, and server-side environments. Server libraries include Python, Node, Ruby, PHP, .NET, Java, Clojure, Go, Rust & Xamarin||Operates on web; limited functionality on mobile; does not support server destinations|
|User Interface||Delivers sleek user experience; automatically configures tools when users switch on an destination||Requires users to designate a number of 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. It is often the case where Segment works well in tandem with a tag manager. In fact, Segment has a direct integration with Google Tag Manager (GTM) as a Destination.
While it is also possible to fire Segment’s Analytics.js library through a tag manager, we don’t recommended that you do this for a few key reasons:
Segment’s Engineering team conduct all QA and regression testing assuming a native installation of Analytics.js on the page. They do not check for a tag manager ‘hybrid’ approach. Therefore when it comes to troubleshooting, it can be difficult to pinpoint root cause of a technical issue.
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) through an additional tool like a Tag Manager, you introduce additional risk of data loss and make it difficult or impossible to troubleshoot.
This implementation architecture can cause major performance issues, such as delays with any 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.
Not every implementation of a TMS is the same, therefore the issue around data loss can be trivial or very high on a case by case basis.
Replay is available to customers on our Business tier plan.
This page was last modified: 20 Nov 2019
Questions? Problems? Need more info? Contact us, and we can help!