
TAGFLOW FOR GTM
TagFlow for GTM compatibility with REEID Translate
TagFlow for GTM compatibility with REEID Translate is being reviewed using official plugin documentation. Universal GTM snippet injection into the site’s “ and “ (noscript) without modifying theme files (described as “Universal GTM Injection”). No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What TagFlow for GTM does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
TagFlow for GTM is documented in the Analytics category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How TagFlow for GTM compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Universal GTM snippet injection into the site’s “ and “ (noscript) without modifying theme files (described as “Universal GTM Injection”).
- Pushes global page-level variables (e.g., `pageTitle`, `pageCategory`, `userRole`, and post IDs) on every page load (described as “Global Variables”).
- Implements WooCommerce/EDD GA4 e-commerce DataLayer schemas for customer journey events (e.g., `view_item_list`, `select_item`, `view_item`, `add_to_wishlist`, `add_to_cart`, `view_cart`, `remove_from_cart`, `begin_checkout`, `add_shipping_info`, `add_payment_info`, `purchase`).
- Tracks engagement behaviors including Scroll Depth, YouTube video plays, and Vimeo video progress (described as “Engagement Tracking”).
- Provides universal form tracking via 1-click DataLayer integration for multiple form plugins, with conditional enabling/disabling intended to strip JavaScript for disabled form trackers.
- Supports AJAX add-to-cart compatibility by using WooCommerce hooks/fragments/frontend fallbacks (as stated in the FAQ).
- Enhanced Conversions support via customer data mapping with a “deep 3-tier fallback system” intended to pass fields like Email, Phone, Address, First Name, and Last Name into the DataLayer when available.
TRANSLATION BOUNDARY
TagFlow for GTM capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
TagFlow for GTM and REEID Translate FAQ.
What does TagFlow for GTM do?
TagFlow for GTM has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does TagFlow for GTM have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from TagFlow for GTM?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate TagFlow for GTM in a multilingual WordPress workflow.
REEID documents TagFlow for GTM functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.