OPACE PREFERRED SOURCE BUTTON & ANALYTICS FOR GOOGLE
Opace Preferred Source Button & Analytics for Google translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Opace Preferred Source Button & Analytics for Google does, but does not yet establish specific visitor-facing content values that REEID should translate.
Visit Opace Preferred Source Button & Analytics for Google ↗
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.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Frontend button/banner rendering via Gutenberg blocks and shortcodes (e.g., `[opace_preferred_source]`, `[opace_preferred_source_button]`, `[opsrc_button]`) with placement options including Smart placement and multiple insertion locations.
- Loads Google’s hosted `publisher.js` from `news.google.com` only on pages where the button/banner renders; native button behavior depends on JavaScript availability.
- Fallback behavior: if the Google script cannot load (or with JavaScript disabled), custom presets open a direct preferences link (`google.com/preferences/source`), and the native style can render a plain link fallback.
- Analytics/measurement: records anonymous aggregate impressions and clicks (and click-through rate) for configurable durations (30 or 90 days) with per-placement reporting; analytics are trigger-based and do not confirm completed Preferred Source additions.
- Consent/“two-click” mode: GDPR two-click mode defers loading the Google script until reader agreement; declining uses the direct preferences link instead of loading the Google script.
- Optional integration with an existing GA4/dataLayer setup: can emit click-related events (placement/style/popup-or-deeplink mode) but does not load GA4 itself; plugin analytics are stored as anonymous aggregate counts in the WordPress database.
- Eligibility handling: no automated eligibility API; plugin checks whether the WordPress address is a supported domain or subdomain format and links the owner to Google’s preferences tool for manual eligibility checking; subdirectories are treated as not eligible.
- Network activation-safe defaults and per-site settings, with optional network settings locking and a documented white-label filter for agency installations.
Distinctive features
Frontend button/banner rendering via Gutenberg blocks and shortcodes (e.g., `[opace_preferred_source]`, `[opace_preferred_source_button]`, `[opsrc_button]`) with placement options including Smart placement and multiple insertion locations. Loads Google’s hosted `publisher.js` from `news.google.com` only on pages where the button/banner renders; native button behavior depends on JavaScript availability. Fallback behavior: if the Google script cannot load (or with JavaScript disabled), custom presets open a direct preferences link (`google.com/preferences/source`), and the native style can render a plain link fallback. Analytics/measurement: records anonymous aggregate impressions and clicks (and click-through rate) for configurable durations (30 or 90 days) with per-placement reporting; analytics are trigger-based and do not confirm completed Preferred Source additions. Consent/“two-click” mode: GDPR two-click mode defers loading the Google script until reader agreement; declining uses the direct preferences link instead of loading the Google script. Optional integration with an existing GA4/dataLayer setup: can emit click-related events (placement/style/popup-or-deeplink mode) but does not load GA4 itself; plugin analytics are stored as anonymous aggregate counts in the WordPress database. Eligibility handling: no automated eligibility API; plugin checks whether the WordPress address is a supported domain or subdomain format and links the owner to Google’s preferences tool for manual eligibility checking; subdirectories are treated as not eligible. Network activation-safe defaults and per-site settings, with optional network settings locking and a documented white-label filter for agency installations.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Opace Preferred Source Button & Analytics for Google 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
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
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.