WP GLOBAL SITE TAG
WP Global Site Tag translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what WP Global Site Tag does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Installs a Google tag or Google Tag Manager container on the public site.
- Connects an administrator to Google Analytics with read-only access and shows reports inside WordPress.
- Supports a guided Google Analytics connection with property and website data-stream selection.
- Provides an Analytics overview, daily traffic trend, and top-five content reports for the last 7 days.
- Supports plugin-managed, externally managed, or disabled tag installation modes to avoid duplicate output.
- Supports GT-, G-, AW-, and DC- identifiers through gtag.js, plus GTM- container snippets.
- Preserves existing legacy UA- tracking IDs and trusted custom gtag commands on existing sites.
- Offers optional Consent Mode v2 denied defaults for gtag.js output.
Distinctive features
Supports both Google tag and Google Tag Manager container output, plus guided Google Analytics connection with property and website data-stream selection. It also offers optional Consent Mode v2 denied defaults for gtag.js output and preserves legacy UA- tracking IDs on existing sites.
Dynamic content
Dynamic analytics content is documented for an Analytics overview, a daily traffic trend, and top-five content reports for the last 7 days. Official evidence for additional dynamic report surfaces was not found.
SEO and metadata
SEO or metadata behavior is not established in the supplied evidence beyond analytics-related reporting and tag output.
URLs and navigation
URL or navigation behavior is not established in the supplied evidence.
Forms and commerce
Forms or commerce behavior is not established in the supplied evidence.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what WP Global Site Tag does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- Evidence is limited to the documented public-site tag output, Google Analytics connection, and the reports described in the supplied intelligence. Official evidence for additional analytics surfaces, unsupported report fields, custom dimensions, event-level measurement behavior, server-side tracking, data export in Free, or non-Google analytics integrations was not found.
COMMON QUESTIONS
WP Global Site Tag and REEID Translate FAQ.
Does the current evidence establish translation scope for WP Global Site Tag?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.