S2S CONVERSIONS
S2S Conversions compatibility with REEID Translate
S2S Conversions compatibility with REEID Translate is being evaluated from available plugin evidence. Server-side GA4 Measurement Protocol conversion sending: sends purchase and lead events directly from the server to Google Analytics 4 via the Measurement Protocol (as described in the provided plugin readme). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for S2S Conversions.
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
S2S Conversions is documented in the Analytics category with 7 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 S2S Conversions 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 GA4 Measurement Protocol conversion sending: sends purchase and lead events directly from the server to Google Analytics 4 via the Measurement Protocol (as described in the provided plugin readme).
- GA4 purchase event data coverage: purchase tracking is described as including complete purchase data such as items, revenue, tax, and shipping (as described in the provided plugin readme).
- GA4 lead event mapping for form submissions: tracks form submissions as generate_lead events (as described in the provided plugin readme).
- Session ID/client attribution handling: captures GA4 session data (client_id, session_id) before payment redirect and uses it to attribute conversions to the original traffic source/channel rather than Unassigned/Direct (as described in the provided plugin readme).
- Asynchronous conversion processing: uses Action Scheduler to process conversions asynchronously when WooCommerce is present; otherwise falls back to WordPress cron (as described in the provided plugin readme).
- Consent-tool integration for when events are sent: supports multiple cookie consent tools and states that consent is respected before sending GA4 events, with a custom banner option using a cookieConsent cookie (as described in the provided plugin readme).
- External service interactions: sends data to Google Analytics (analytics.google.com) via Measurement Protocol and performs a domain verification request to s2s-plugin.tj-da.com to verify DPA acceptance (as described in the provided plugin readme).
CONTENT BOUNDARY
S2S Conversions 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
S2S Conversions and REEID Translate FAQ.
What does S2S Conversions do according to the available plugin evidence?
S2S Conversions has 7 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 S2S Conversions?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for S2S Conversions?
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 S2S Conversions in a multilingual WordPress workflow.
REEID documents S2S Conversions 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.