| Feature | Tags | Tealium | GTM360 | Tags | Tealium | GTM360 | |||
|---|---|---|---|---|---|---|---|---|---|
| Cost | |||||||||
|
|||||||||
| LiscencingCost | Inlcuded in Experience Cloud | Additional Cost | Included in GMP 360 | 1 | -1 | 1 | |||
| Support hoursCost | Client care included | Additional Cost, and is part of service contract | Included in GMP 360 | 1 | -1 | 1 | |||
| Data Collection | |||||||||
|
|||||||||
| DataLayer handlingData Collection | Customer Driven dataLayer support | UDO is stength and weakness. Strength because its robust Weakeness because system relies heavily on it and has a steep learning curve |
Event-Driven dataLayer support | 1 | 1 | 1 | |||
| Native Event TrackingData Collection | Built in Event Types to detect 28 essential events, covering page load events, to clicks such as Mouse clicks with a global Element Selector possibility, SPA, and media events. | Built-in Load events only, specific to how Tealium loads on the page. | Built-in Triggers with 19 built-in dataLayer events, covering essential page load events, click events, SPA, scrolling, and youtube events. | 1 | 1 | 1 | |||
| Custom Event/Click trackingData Collection | Direct Calls with ability to pass additional data Also possibility to detect Direct Calls specific to Adobe Launch, with ability to pass addiitonal data. Possible to detect custom events as well |
Tealium has two options for tracking clicks and other events on a site: Configuring the jQuery extension in the iQ console. (more code) More advanced tracking, like tracking form submits, video plays, and scroll tracking, custom JavaScript code can be added through the Tealium extensions tab Coding utag.link() directly in the page As a result, the most stable and robust way to complete this tracking is to hard code all of the event information with the event trigger. While this approach certainly works, it takes away for the advantages you would otherwise get from a tag management system. |
dataLayer.push events with additional data Also possibility to detect custom dataLayer.push events, with ability to pass addiitonal data. |
1 | -1 | 1 | |||
| Keeps data recordedData Collection | Does not collect data | Can start collecting data for other teals like EventStream, and AudienceStream. Additional configuration needed to prevent PII data collection. | Does not collect data | 0 | 1 | 0 | |||
| Data Mapping to Analytics TagsData Collection | Can create Data Elements and map to variables Need to create custom code to translate Adobe variables to GA variables |
Create UDO dataLayer variables and map to tags. Has a custom code extension that can translate UDO for GA variables. |
Create GTM variables and map to tags Need to create custom code to translate GA variables to Adobe. |
0 | 1 | 0 | |||
| Multi-site Handling | |||||||||
|
|||||||||
| Deploy large groups of tags to same sites at same timeMulti-site Handling | Only way is to use the same launch embed code across multiple sites | Done via a Master Libraries. Master library with common tags across multiple sites can be linked to multiple profiles | Done via Zones and linking zones to one Container, but increases load time | 0 | 1 | 1 | |||
| Copy tag / variable across propertiesMulti-site Handling | Done via Properties with Copy function to destination property for both tags, data elements and extensions | Possible with the help of an external browser plugin, and custom code, but has known bugs | Can export/import rules across containers, but must pay attention at the tag level on what is being imported | 1 | 0 | 1 | |||
| Deploy individual tags to same siteMulti-site Handling | In multiple properties done at the Rule level. Must copy rule across multiple destinations. In Single property, can maintain a Data Element mapping multiple sites to property-specific values |
Must add rule to Master library and will be available to all linked profiles | Can export/import rules across containers, but must pay attention at the tag level on what is being imported | 0 | 1 | 0 | |||
| Use same tag w/ different ID configurationsMulti-site Handling | Maintain data element mapping IDs specific to sites to tags | Table Mapping Extension | Variable Table Mapping | 1 | 1 | 1 | |||
| Privacy | |||||||||
|
|||||||||
| Cookie Consent ManagementPrivacy | Supported Integration with Top Cookie Consent Providers, but requires contract with vendors | Built-in cookie consent management | Requires custom solutions to integrate | 0 | 1 | -1 | |||
| Site Performance | |||||||||
|
|||||||||
| Page Load SpeedSite Performance | Modern asynch event driven framework, lighter than other TMS | Asynch framework, template driven Possible to bundle tags to improve speed load… but only because tag framework makes it slow. Advanced setting that complicates deployment |
Async only, template driven | 1 | 0 | 0 | |||
| FrameworkSite Performance | Newer, modular and event-based. Will only load a portion of Launch that is needed, instead of the entire container. | Older, monolithic with ability to Extend through additional custom code. Will load the entire container every time. | Older, event-driven data collection. Will load entire container every time. | 1 | -1 | 0 | |||
| Async and Sync suportSite Performance | Both | Both | Async only | 1 | 1 | 0 | |||
| Support | |||||||||
|
|||||||||
| DocumentationSupport | Experience League. Help Documents | Tealium Learning Center. Articles not dated. Tough to know what is outdated | GTM Help pages | 1 | 0 | 1 | |||
| CommunitySupport | Avid community Slack Channel Blogs extensively post about Launch |
Has community forums Few individual blogs about Tealium |
Has community forums Blogs extensively post about GTM |
1 | 0 | 1 | |||
| Vendor SupportSupport | Free Client Care support | Billable support hours | Free SLA support | 1 | 1 | 1 | |||
| Tagging Functionality | |||||||||
|
|||||||||
| Tag GroupingTagging Functionality | must add label in tag name | ability to add labels | folders | -1 | 1 | 1 | |||
| Time-based Conditions (tag expirations)Tagging Functionality | Able to set Start and End Times at rule level | Able to set Start and End Times at tag level | Able to set Start and End Times at tag level | 1 | 1 | 1 | |||
| Sequencing TagsTagging Functionality | Sequencing controlled by the type of trigger and adding a rank that determins when to fire a rule | Must be familiar with Tealium's Order of Operations Advanced options provide additional control over sequence of tags. It does so in a complex manner. (Wait Flag) Must also sort tags and extensions in order you want to trigger them in. |
Posslible to create dependencies, but it forces a fire | 1 | 1 | 1 | |||
| Understanding SequencingTagging Functionality | Very straightforward | Must be aware of Tealium's Order of Operations (not just a page Order of Operations) Sequence is determined by how Tags/Extensions are scoped into the different Order of Operations, THEN by order in which they are sorted in the UI, Last row loads last |
Very straightforward. Built-in GTM Console gives visibility to sequence | 1 | -1 | 1 | |||
| Deploying Personalization ToolsTagging Functionality | Hiding script outside launch + asynch Can tailor hiding script to specific needs |
Additional code + asynch + extension configuration Synch with additional code, but cannot use mappings |
Hiding script outside GTM + asynch | 1 | 0 | 1 | |||
| Support for Adobe analytics libraryTagging Functionality | Adobe hosted Self hosted Custom Code |
Tealium hosted stays up to date Self-hosted |
The string length must be between 1 and 20000 characters Self hosted |
1 | 1 | 0 | |||
| Support for Adobe Analytics tagsTagging Functionality | Native UI built-in to manage variable mappings and beacon fires | Tag template built to support Adobe variables mapping | Custom code only | 1 | 0 | -1 | |||
| Support for Google Analytics libraryTagging Functionality | Extensions available for unversal analytics.js or global tag gtag.js libraries | Tag templates for both analytics.js and gtag.js supported | Native GTM variable to manage all library settings in user-friendly manner | 1 | 1 | 1 | |||
| Support for Google Analytics taggingTagging Functionality | Translation custom code layer needed to format data into GA format. Extensions do not support all GA functionality | Tag template available for analytcs.js library. Global tag gtag.js library does not support all google functionality | Native templates support all GA functionality | -1 | 0 | 1 | |||
| Library of Pre-built third party tagsTagging Functionality | Nascient Extension Marketplace | over 1,000 tag tempaltes | less than 100 tag templates | -1 | 1 | 0 | |||
| Support for Custom tags using HTML or JSTagging Functionality | Yes | Yes | Yes | 1 | 1 | 1 | |||
| Browser Extensions for Debugging TMSTagging Functionality | Many available and indsutry-recognized adoption. | Large amount of Tools and Extensions makes it difficult to debug issues Extensions require custom code to work |
Many available and industry-recognized adoption. Built-in Console. | 1 | -1 | 1 | |||
| Multiple triggers OR conditionsTagging Functionality | Able to add multiple triggers to one tag that will fire the tag on either of the events being set | Must create separte Load Rules for specific tags to fire one tag on either events being fired | Able to add multiple triggers to one tag that will fire on either of the events being set | 1 | 0 | 1 | |||
| 3rd Part Tags - DCMTagging Functionality | Extension available to implement DCM tags with user friendly UI, able to manage multiple IDs for the same site and across sites | DCM Template with friendly UI, able to manage multiple IDs for same site and across sites | DCM Template with friendly UI, able to manage multiple IDs for same site and across sites | 1 | 1 | 1 | |||
| 3rd Part Tags - FacebookTagging Functionality | Extension available to implement FB tags with use friendly UI, but currently only supports having one ID at the same time wtihin same profile. Can use Data Element to control different IDs across different sites. Must use custom code instead if need to use two FB account IDs on the same launch embed code |
FB template available and able to maintain multiple tags with different IDs | No template available, must be done via custom HTML | 0 | 1 | -1 | |||
| Create Custom Tag TemplatesTagging Functionality | Leverage API to create custom Extensions for specific use cases | Able to customize tag templates through use of Custom JS | Leverage Custom Templates and its APIs to create customized templates that anyone can use in the organization, without the need to resort custom HTML tags or JS variables | 1 | 1 | 1 | |||
| AEM IntegrationTagging Functionality | Native AEM Integration capabilities through AEM Extension | AEM Integration capabiltieis through Plugin | No AEM integration | 1 | 1 | -1 | |||
| Variable size LimitationsTagging Functionality | None known | None known | Up to 20,000 characters in variables | 1 | 1 | -1 | |||
| UI/UX | |||||||||
|
|||||||||
| Business User FriendlinessUI/UX | Dark theme Easy to navigate |
White theme Developer friendly |
White theme Easy to navigate |
1 | -1 | 1 | |||
| UI SpeedUI/UX | No impact on load time depending on number tags | UI takes a toll after many tags are implemented. Slow loads | No impact on UI load time | 1 | 0 | 1 | |||
| Multi-tab NavigationUI/UX | Able to have multiple tabs with Launch screens open | UI built on technology that does not allow multi-tab navigation, leading to switching back and forth between UI screens | Able to have multiple tabs open with GTM screens | 1 | 0 | 1 | |||
| DashboardsUI/UX | No built-in dashboard | built-in tag firing status reports, but no reports on status in workflow | No built-in dashboard | -1 | 1 | -1 | |||
| User Management | |||||||||
|
|||||||||
| User GroupsUser Management | Only at property level. Simplfied Develop Approve Publish Manage Extensions Manage Environments |
Comprehensive settings Manage Users Manage Tag Templates Manage Resource Locks Save Existing Versions Save As New Versions JavaScript Draft Promotion Publish to Dev Environment Publish to QA Environment Publish to Prod Environment |
Possible at account, or container level Read Edit Approve Publish |
0 | 1 | 0 | |||
| Tag-level restrictionsUser Management | Not possible | Possible to restrict by types of tags, but Markets still have access to view all tags | Can create Zones to limit tags and pages a zone can publish to. Useful for managing multiple TMS as a single one | -1 | 0 | 1 | |||
| Approval-only WorkflowUser Management | User permissions restrict local market-added tags to be approved by HQ. Flexible for HQ to publish, or allow to send back to Local markets for publishing No email notification is sent |
Permissions restrict users to request changes for approval before publishing, but must be published by HQ Email is sent to approver |
Permissions restrict users to request changes for approval before publishing, but must be published by HQ No email notification is sent |
1 | 1 | 0 | |||
| Workflow Governance | |||||||||
|
|||||||||
| Preview tags before launchWorkflow Governance | virtual libraries, simple swap of code with extension | must save and publish to environment | real-time validation with Preview link and GTM console | 0 | -1 | 1 | |||
| Versioning / Rolling BackWorkflow Governance | Version comparison and rollback available | Version comparison and rollback available | Version comparison and rollback available | 1 | 1 | 1 | |||
| Comparing ChangesWorkflow Governance | Possible to compare library changes side by side | Possible to compare published version side by side, although complex | Possible to compare workflow changes side by side | 1 | 1 | 1 | |||
| Concurrent workWorkflow Governance | By using Libraries there is the ability for different team members to work at the same time without affecting other's progress | Not possible to work at same time, but a notification is shown when someone else is editing a version. Once published you have ability to Save a new version or merge latest | By using workspaces, any change done in one workspace is completely isolated from other changes | 1 | 0 | 1 | |||
| EnvironmentsWorkflow Governance | Unlimited Dev, 1 stage, 1 prod | Unlimited Dev, 1 stage, 1 prod | Unlimited environments, one Live environment | 1 | 1 | 1 | |||
| Library ManagementWorkflow Governance | Unlimited Dev Libraries | No concept | Unlimited workspaces | 1 | 1 | 1 | |||
| Approval-only WorkflowWorkflow Governance | "User permissions restrict local market-added tags to be approved by HQ. Flexible for HQ to publish, or allow to send back to Local markets for publishing No email notification is sent" |
"Permissions restrict users to request changes for approval before publishing, but must be published by HQ. Email is sent to approver" |
"Permissions restrict users to request changes for approval before publishing, but must be published by HQ No email notification is sent" |
1 | 1 | 0 | |||
| Publishing WorkflowWorkflow Governance | Clearly defined stages. Only one library at a time | Notice is shown to users when working on a version currently being deployed | Stages defined by Environments. Not clearly identifiable | 1 | 1 | 0 | |||
| Working with Other Solutions | |||||||||
|
|||||||||
| Additional CDP OfferingsWorking with Other Solutions | Launch is foundation for the future Experience Platform CDP | AudienceStream and EventStream CDP existing capabilities | No known CDP capabilities | 0 | 1 | -1 | |||
| Fully custuomizableWorking with Other Solutions | Open API accesses every feature in Launch, with potential to building your own CDP | Closed system | GTM APIs available | 1 | -1 | 1 | |||
|
|||||||||