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 evaluated from available plugin evidence. 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 visitor-facing translation surface is currently confirmed.

Visit Opace Preferred Source Button & Analytics for Google ↗

AWAITING VERIFICATION

What the available evidence establishes for Opace Preferred Source Button & Analytics for Google.

Official plugin information supports the compatibility context documented for this category.

AWAITING VERIFICATION
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 concrete capabilities identified in the current evidence.

EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.

COMPATIBILITY REVIEW

How Opace Preferred Source Button & Analytics for Google compatibility is evaluated

01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.

02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.

03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.

04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.

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.

CONTENT BOUNDARY

Opace Preferred Source Button & Analytics for Google capabilities and translation scope are documented separately.

The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.

Functional capability alone is not treated as evidence that a value should be translated.

LIMITATIONS & QA

Verification notes

  • This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.

COMMON QUESTIONS

Opace Preferred Source Button & Analytics for Google and REEID Translate FAQ.

What does Opace Preferred Source Button & Analytics for Google do according to the available plugin evidence?

Opace Preferred Source Button & Analytics for Google has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.

Is a REEID translation surface currently confirmed for Opace Preferred Source Button & Analytics for Google?

No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.

What would establish translation scope for Opace Preferred Source Button & Analytics for Google?

The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.

RELATED GUIDES

Continue through the compatibility library.

  • Analytics Integrations — Browse documented Analytics integrations and compatibility guides.
  • REEID Translate Pro Features — Explore multilingual translation and workflow capabilities.
  • Architecture — Understand how REEID separates multilingual content from WordPress functionality.
  • Opensolr Search — Review Opensolr Search compatibility with REEID Translate based on available plugin evidence. No specific visitor-facing translation surface is currently confirmed.
  • oomates — Review oomates compatibility with REEID Translate based on available plugin evidence. No specific visitor-facing translation surface is currently confirmed.
  • Opinly — Review Opinly compatibility with REEID Translate based on available plugin evidence. No specific visitor-facing translation surface is currently confirmed.
  • Onsite Messaging by PushAlert – Exit Intent Popups, Email Optins, Discount Overlays — Review Onsite Messaging by PushAlert compatibility with REEID Translate based on available plugin evidence. No specific visitor-facing translation surface is currently confirmed.
  • Opt-Out for Google Analytics (DSGVO / GDPR) — Review Opt-Out for Google Analytics (DSGVO / GDPR) compatibility with REEID Translate based on available plugin evidence. No specific visitor-facing translation surface is currently confirmed.
  • OneSignal – Web Push Notifications — Review OneSignal compatibility with REEID Translate based on available plugin evidence. No specific visitor-facing text is currently confirmed for translation.

INTEGRATION EVIDENCE

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 evidence-backed translation support so compatibility claims remain specific and testable.

Translation scope will be published when concrete visitor-facing content is established by evidence.

Explore REEID Translate
View integrations
Shopping Cart
Scroll to Top