OPACE PREFERRED SOURCE BUTTON & ANALYTICS FOR GOOGLE
Opace Preferred Source Button & Analytics for Google compatibility with REEID Translate
Opace Preferred Source Button & Analytics for Google compatibility with REEID Translate is being reviewed using official plugin documentation. 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. No specific text shown to visitors is currently confirmed for translation.
Visit Opace Preferred Source Button & Analytics for Google ↗
AWAITING VERIFICATION
What Opace Preferred Source Button & Analytics for Google 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
Opace Preferred Source Button & Analytics for Google is documented in the Analytics category with 8 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.
PLUGIN INFORMATION
What the plugin does
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.
TRANSLATION BOUNDARY
Opace Preferred Source Button & Analytics for Google 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.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Opace Preferred Source Button & Analytics for Google in a multilingual WordPress workflow.
REEID documents Opace Preferred Source Button & Analytics for Google 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.