
AG DATA FOR POSTHOG
AG Data for PostHog compatibility with REEID Translate
AG Data for PostHog compatibility with REEID Translate is being evaluated from available plugin evidence. Server-side WooCommerce e-commerce event tracking sent to PostHog for order lifecycle events (e.g., Order Completed, Order Refunded, Order Status Changed). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for AG Data for PostHog.
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
AG Data for PostHog 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 AG Data for PostHog 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 WooCommerce e-commerce event tracking sent to PostHog for order lifecycle events (e.g., Order Completed, Order Refunded, Order Status Changed).
- Server-side tracking for product/cart-related events including Product Added (with deduplication) and support for various add-to-cart contexts (e.g., AJAX buttons, variable/bundled/optioned products).
- Frontend event tracking via PostHog JavaScript SDK for browsing and funnel events (e.g., Product Viewed, Product List Viewed, Products Searched, Cart Viewed, Checkout Started, Coupon Applied/Removed, Payment Info Entered), with stated support for block themes without jQuery.
- Marketing attribution capture and persistence using UTM parameters and ad click IDs (gclid, fbclid, ttclid, msclkid, li_fat_id), including first-touch/last-touch attribution persisted to orders and included in PostHog order events.
- Identity stitching between anonymous and logged-in users using PostHog identify flows (browser posthog.identify and server-side identify/anon distinct id merging) to enable end-to-end funnels.
- LTV/person enrichment in PostHog by updating person properties on purchase (e.g., total_orders, lifetime_value, avg_order_value, last_order_date) and setting acquisition fields once (e.g., acquisition_source/medium/campaign).
- Consent/GDPR mode support with optional opt-in/opt-out behavior (memory-only persistence when opted out) and JavaScript functions aphaOptIn()/aphaOptOut(), plus built-in support for CookieYes and Complianz consent platforms.
- WooCommerce compatibility features including HPOS compatibility and support for both classic and block checkout/cart flows, plus reverse proxy support for first-party tracking domains.
CONTENT BOUNDARY
AG Data for PostHog 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
AG Data for PostHog and REEID Translate FAQ.
What does AG Data for PostHog do according to the available plugin evidence?
AG Data for PostHog 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 AG Data for PostHog?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for AG Data for PostHog?
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 AG Data for PostHog in a multilingual WordPress workflow.
REEID documents AG Data for PostHog 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.