
外掛標籤
開發者團隊
② 後台搜尋「Tagbridge – Deep Integration for PostHog」→ 直接安裝(推薦)
原文外掛簡介
Tagbridge is a modular integration platform for WordPress, starting with a deep, independent integration for PostHog. Enable only the integrations you use, configure privacy and consent rules once across your whole site, and send clean browser and server-side events without touching code.
Tagbridge is an independent project. It is not affiliated with, endorsed by, or sponsored by PostHog or any other listed service. Third-party product names and logos belong to their respective owners and are used solely to identify the services Tagbridge integrates with.
What it does today
Modular Integrations Hub: Enable or disable integrations at any time with zero runtime cost when disabled. Each integration has its own isolated settings screen, plus a Coming soon catalog with local in-WordPress launch notifications (Notify me).
Global Privacy & Settings: Built-in WordPress Consent API integration (Off, Require consent, or Cookieless until consent), Do Not Track (DNT) header support, and WordPress role exclusions applied across both browser scripts and server-side events.
PostHog Connection & Key Check: Connect to PostHog Cloud (US or EU) or your own self-hosted or reverse-proxy host. Your project API key is checked with a live read-only test call before it is saved.
Client-side Tracking: Loads PostHog (posthog-js) from the host you configure with toggles for pageviews, autocapture (clicks and form interactions), session recording, person profile mode, and privacy-first cookieless mode.
Identity Stitching: 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), with per-property controls (email, name, role).
Server-side Events: Capture key events (user_logged_in, user_registered) directly from WordPress so they still arrive when browsers block tracking, with non-blocking shutdown delivery and per-event switches.
WooCommerce Events (when active): HPOS-safe tracking for classic and Block Checkout (product_viewed, product_added_to_cart, checkout_started, order_completed with value and currency), idempotent order completion (never double-counted on repeated status changes), and customer-safe privacy snapshots when admins complete orders.
On the roadmap
Planned for future releases:
Upcoming Integrations: Webhooks, Google Analytics 4, Meta Pixel & Conversions API, Klaviyo, Microsoft Clarity, Plausible Analytics, Intercom, and Slack & Discord Alerts.
PostHog Deepening: Setup diagnostics with a labeled test-event check, a no-flicker server-evaluated feature-flag Gutenberg block and shortcode, and starter dashboards provisioned in your PostHog project.
External services
This plugin connects to PostHog, the analytics service you configure. It is required for the PostHog integration to do anything, because its purpose is to send your site’s analytics to your PostHog project.
What is sent and when:
When you save PostHog 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.
On your site’s front end, after you have connected and when permitted by your consent/privacy settings, 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.
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.
The host the data is sent to is the one you configure:
US cloud: https://us.i.posthog.com
EU cloud: https://eu.i.posthog.com
Self-hosted or reverse proxy: the URL you enter
PostHog terms of service: https://posthog.com/terms
PostHog privacy policy: https://posthog.com/privacy
Privacy
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.
Global controls under Privacy & Settings apply across all integrations:
WordPress Consent API: Choose Off, Require consent (blocks scripts and server events until consent is granted, and listens for live consent changes), or Cookieless until consent (runs anonymously in memory without person identification until consent is granted).
Do Not Track: Optionally suppress browser and server-side tracking when a visitor sends a DNT: 1 header.
Exclude user roles: Skip tracking across browser and server events for selected WordPress roles (such as administrators).
Local launch alerts: Selecting Notify me on a Coming soon integration stores only the integration slug locally in your WordPress tagbridge option; zero external calls are made.
