SYNCBEACON
SyncBeacon compatibility with REEID Translate
SyncBeacon compatibility with REEID Translate is being evaluated from available plugin evidence. Server-side conversion tracking via WooCommerce order webhooks forwarded to ad platforms (e.g., Meta CAPI, Google Ads) through the SyncBeacon cloud service. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for SyncBeacon.
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
SyncBeacon is documented in the Analytics category with 6 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 SyncBeacon 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
- Server-side conversion tracking via WooCommerce order webhooks forwarded to ad platforms (e.g., Meta CAPI, Google Ads) through the SyncBeacon cloud service.
- Browser-side storefront tracking via injection/loading of a single lightweight `sb.js` tag (no Google Tag Manager), capturing PageView, AddToCart, and checkout funnel steps.
- Automatic deduplication between browser events and server-side (webhook) order events so the same purchase is not double-counted by connected platforms.
- Consent gating before events are forwarded to ad platforms, described as “GDPR-ready by design,” with hashing/matching handled under configured consent rules.
- Configuration storage in WordPress limited to non-customer data (e.g., public key, merchant ID, script URL, API URL, timestamps), with claims that customer order PII is not stored in WordPress options.
- Auto ad-pause on out-of-stock products by syncing product/catalogue/stock signals and pausing linked ads when configured SKUs/variants go out of stock.
CONTENT BOUNDARY
SyncBeacon 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
SyncBeacon and REEID Translate FAQ.
What does SyncBeacon do according to the available plugin evidence?
SyncBeacon has 6 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 SyncBeacon?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for SyncBeacon?
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.
INTEGRATION EVIDENCE
Evaluate SyncBeacon in a multilingual WordPress workflow.
REEID documents SyncBeacon 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.