Great Anthony

<p>Tagbridge is a simple, independent way to add PostHog to WordPress: PostHog for WordPress, without touching code. Enter your PostHog project API key, choose your region, and Tagbridge loads PostHog on your site with the settings you pick.</p>
<p>Tagbridge is an independent project. It is not affiliated with, endorsed by, or sponsored by PostHog. “PostHog” is a trademark of its respective owner and is used here only to describe what this plugin connects to.</p>
<h4>What it does today</h4>
<ul>
<li>Connect to PostHog Cloud (US or EU) or your own self-hosted or reverse-proxy host.</li>
<li>Your project API key is checked with a live test call before it is saved, so you know right away if it is correct.</li>
<li>Loads PostHog (posthog-js) from the host you configure, so self-hosted and reverse-proxy setups work without code.</li>
<li>Plain-language toggles for what gets captured: pageviews, autocapture (clicks and form interactions), session recording, and person profile mode.</li>
<li>Privacy-first cookieless mode that keeps visitor state in memory, so no PostHog cookie is set.</li>
<li>Identity: tie logged-in WordPress users to one PostHog person across anonymous and logged-in sessions, using a stable hashed identifier (never the raw user ID). You choose whether to identify logged-in users and which properties to send (email, name, role).</li>
<li>Server-side events: send key events (user logged in, user registered) from your own WordPress server, so they still arrive when a visitor’s browser blocks tracking. Runs on your existing hosting, with a per-event on/off switch. A failed or slow PostHog request never affects your pages.</li>
<li>WooCommerce events (when WooCommerce is active): product viewed, added to cart, checkout started, and order completed with order value and currency. The same person is tracked from the browser session through to the completed order.</li>
<li>A clean settings screen that fits WordPress and stays out of your way.</li>
</ul>
<h4>On the roadmap</h4>
<p>Planned for future releases:</p>
<ul>
<li>A no-flicker feature-flag block and shortcode evaluated on the server.</li>
<li>Optional starter dashboards created in your PostHog project.</li>
<li>WordPress Consent API support.</li>
</ul>
<h3>External services</h3>
<p>This plugin connects to PostHog, the analytics service you configure. It is required for the plugin to do anything, because the plugin’s purpose is to send your site’s analytics to your PostHog project.</p>
<p>What is sent and when:</p>
<ul>
<li>When you save your settings in the admin, the plugin makes one request to the PostHog feature-flags endpoint (for example https://us.i.posthog.com/flags) with your project API key to confirm the key and host are valid. This request does not record any analytics event.</li>
<li>On your site’s front end, after you have connected and only when configured, the plugin loads PostHog (posthog-js) from the host you choose (PostHog US cloud, EU cloud, or your own host). PostHog then sends visitor analytics such as pageviews and, if enabled, clicks and form interactions and session recordings, to your PostHog project. The exact data depends on the toggles you choose.</li>
<li>When server-side events are enabled, your WordPress server sends those events (for example user logged in, or a completed WooCommerce order with its value and currency) directly to your configured PostHog host. This happens from your server, not the visitor’s browser.</li>
</ul>
<p>The host the data is sent to is the one you configure:</p>
<ul>
<li>US cloud: https://us.i.posthog.com</li>
<li>EU cloud: https://eu.i.posthog.com</li>
<li>Self-hosted or reverse proxy: the URL you enter</li>
</ul>
<p>PostHog terms of service: https://posthog.com/terms<br />
PostHog privacy policy: https://posthog.com/privacy</p>
<h3>Privacy</h3>
<p>No analytics are sent until you enter a PostHog project API key and connect. You control what is captured with the tracking toggles, and you can turn on cookieless mode so no PostHog cookie is set.</p>
<p>You are responsible for telling your visitors what you collect and for obtaining any consent your jurisdiction requires. Support for the WordPress Consent API is planned for a future release.</p>


Tagbridge – Deep Integration for PostHog

Independent PostHog integration for WordPress. Connect your project and send pageviews and events to PostHog. Not affiliated with PostHog.

Alex Godlewski

<p>AG Data for PostHog connects your WooCommerce store to <a href="https://posthog.com" rel="nofollow ugc">PostHog</a> — the open-source product analytics platform. Track the complete customer journey from first click to lifetime value, all within PostHog.</p>
<h4>Why AG Data?</h4>
<p>Most WooCommerce analytics plugins give you pageviews and basic events. AG Data gives you a <strong>full marketing attribution engine</strong> — first-touch/last-touch UTM tracking, ad click ID capture (Google, Meta, TikTok, Microsoft, LinkedIn), server-side first-party cookies that survive Safari ITP, and automatic LTV enrichment on every person profile.</p>
<h4>Key Features</h4>
<p><strong>Server-Side Event Tracking</strong></p>
<ul>
<li>Order Completed, Order Refunded, Order Status Changed</li>
<li>Deduplication prevents double-counting</li>
<li>Blocking API calls ensure delivery before marking as tracked</li>
<li>Works with all payment gateways and checkout flows</li>
</ul>
<p><strong>Frontend Event Tracking</strong></p>
<ul>
<li>Product Viewed, Product List Viewed, Products Searched</li>
<li>Product Added / Removed (classic and block-based carts)</li>
<li>Cart Viewed, Checkout Started</li>
<li>Product Clicked, Coupon Applied / Removed, Payment Info Entered</li>
<li>Works without jQuery — block themes fully supported</li>
</ul>
<p><strong>Marketing Attribution Engine</strong></p>
<ul>
<li>Captures UTM parameters and ad click IDs (gclid, fbclid, ttclid, msclkid, li_fat_id)</li>
<li>Server-side first-party cookies bypass Safari ITP 24-hour restriction</li>
<li>First-touch and last-touch attribution persisted to every order</li>
<li>Days-to-conversion and session count tracking</li>
<li>Falls back to WooCommerce 8.5+ native attribution when cookies are unavailable</li>
<li>Attribution data included in all PostHog order events</li>
</ul>
<p><strong>Identity Stitching</strong></p>
<ul>
<li>Reads PostHog JS SDK cookie server-side for seamless funnel connection</li>
<li>Browser <code>posthog.identify()</code> for logged-in users</li>
<li>Server-side <code>$identify</code> with <code>$anon_distinct_id</code> merges anonymous and known profiles</li>
<li>PostHog funnels work end-to-end: Landing Page <span aria-hidden="true" class="wp-exclude-emoji">→</span> Checkout Started <span aria-hidden="true" class="wp-exclude-emoji">→</span> Order Completed</li>
</ul>
<p><strong>LTV Person Enrichment</strong></p>
<ul>
<li><code>total_orders</code>, <code>lifetime_value</code>, <code>avg_order_value</code>, <code>last_order_date</code> updated on every purchase</li>
<li><code>first_order_date</code>, <code>acquisition_source</code>, <code>acquisition_medium</code>, <code>acquisition_campaign</code> set once via <code>$set_once</code></li>
<li>Build PostHog cohorts like “Customers with LTV > $500 acquired from Google Ads”</li>
</ul>
<p><strong>GDPR / Consent Management</strong></p>
<ul>
<li>Optional consent mode: starts PostHog opted-out with memory-only persistence</li>
<li>Exposes <code>aphaOptIn()</code> / <code>aphaOptOut()</code> JavaScript functions</li>
<li>Built-in support for CookieYes and Complianz consent management platforms</li>
</ul>
<p><strong>WooCommerce Compatibility</strong></p>
<ul>
<li>HPOS (High-Performance Order Storage) compatible</li>
<li>Cart and Checkout Blocks compatible</li>
<li>Classic and block checkout flows supported</li>
<li>Reverse proxy support for first-party tracking domains</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 5.8+</li>
<li>WooCommerce 7.0+</li>
<li>PHP 7.4+</li>
<li>A PostHog account (free tier available at posthog.com)</li>
</ul>
<h3>External services</h3>
<p>This plugin connects to PostHog, a third-party product analytics service, to send your store’s analytics and e-commerce event data. This connection is required for the plugin to work — its entire purpose is to record analytics in PostHog. No data is sent until you enter a PostHog Project API key in the plugin settings.</p>
<p>What PostHog is used for:</p>
<ul>
<li>Receiving server-side e-commerce events (Order Completed, Order Refunded, Order Status Changed).</li>
<li>Receiving frontend browsing events (Product Viewed, Cart Viewed, Checkout Started, and similar) via the PostHog JavaScript SDK, which is loaded on your site’s pages from your configured PostHog host.</li>
<li>Storing person profiles enriched with order/LTV data and marketing attribution data.</li>
</ul>
<p>What data is sent, and when:</p>
<ul>
<li>While a visitor browses your store, the PostHog JavaScript SDK captures pageviews and browsing events. This includes page URLs, referrer, UTM parameters, ad click IDs (gclid, fbclid, ttclid, msclkid, li_fat_id), and a PostHog-generated anonymous identifier.</li>
<li>When an order is placed, refunded, or changes status, the plugin sends order data from your server — order ID, totals, currency, line items, payment and shipping method, and billing/shipping country. For logged-in users, a WordPress-based identifier and the customer email may also be sent so anonymous and known profiles can be merged.</li>
<li>Requests are sent to the PostHog host you configure in the settings (PostHog US Cloud, PostHog EU Cloud, or your own self-hosted/proxy URL).</li>
</ul>
<p>Service provider: PostHog Inc.<br />
Terms of Service: https://posthog.com/terms<br />
Privacy Policy: https://posthog.com/privacy</p>


AG Data for PostHog

PostHog Analytics for WooCommerce. Server-side event tracking, marketing attribution engine, identity stitching, and LTV enrichment.

Tagbridge – Deep Integration for PostHog vs AG Data for PostHog