Description
Pressed Hog installs PostHog product analytics on your WordPress site — no code required. Works with PostHog Cloud (US or EU) and self-hosted PostHog instances.
Features
- Guided setup wizard on activation: pick your region, validate your API key live against your PostHog host, choose tracking and consent options, and send a test event to confirm everything works end to end.
- Injects the official posthog-js snippet with your project API key and host.
- Toggles for pageview capture, autocapture, session replay, and popover surveys.
- Optionally identify logged-in users, linking events to their WordPress account.
- Exclude roles (administrators, editors, …) from tracking so your own clicks stay out of your data.
- Consent handling with three modes: no gate, a built-in cookie banner, or integration with an external consent plugin via a cookie or JavaScript API.
- WooCommerce events:
product_added_to_cart,checkout_started, andorder_completed(with order totals and line items, deduplicated per order). - Server-side feature flags: a
[posthog_flag key="my-flag"]…[/posthog_flag]shortcode to gate content, pluspressed_hog_is_feature_enabled()andpressed_hog_get_feature_flag()template helpers. - Reverse proxy: serve PostHog through your own domain (e.g.
yoursite.com/phog/…) so analytics requests are first-party and delivered more reliably. - In-dashboard analytics: a Pressed Hog admin page with pageviews, unique visitors, a traffic chart, top pages, referrers, and devices — plus a WordPress dashboard widget and an optional link to a PostHog shared dashboard. Requires a personal API key with read-only Query scope.
- QR codes & trackable links: turn any URL of your own into a campaign-tagged link (UTM parameters plus a unique per-link id so PostHog can attribute each QR individually), generate its QR code right in the browser (nothing is sent to a third-party QR service), keep a saved list of your links, and export the whole list as a downloadable CSV spreadsheet. Download each QR as PNG or SVG.
Consent integration for developers
In “external” consent mode, tracking stays off until either the configured cookie equals the configured value, or your consent plugin calls:
window.pressedHog.grantConsent(); or `window.pressedHog.denyConsent();`
Hooks
pressed_hog_is_active— filter whether the snippet is output for the current request.pressed_hog_init_config— filter theposthog.init()config array.
PostHog is a registered trademark of PostHog, Inc. This plugin is an independent integration and is not affiliated with or endorsed by PostHog, Inc.
External services
This plugin connects your site to PostHog, a product analytics service. Nothing is sent anywhere until you enter a PostHog project API key. Depending on the features you enable, data goes to PostHog Cloud US (us.posthog.com, us.i.posthog.com, us-assets.i.posthog.com), PostHog Cloud EU (eu.posthog.com, eu.i.posthog.com, eu-assets.i.posthog.com), or the self-hosted PostHog instance you configure.
- Tracking library (visitors’ browsers). On every front-end page view by a tracked visitor, the browser loads the posthog-js library from PostHog’s asset host. It then sends the events you enabled: pageviews (URL, referrer, browser, device, screen size), autocaptured clicks and form submissions, session recordings, and survey responses, together with an anonymous ID and the visitor’s IP address. When a consent mode is enabled, nothing is captured and no PostHog cookie is stored until the visitor consents.
- User identification (optional). If “Identify logged-in users” is on, the logged-in user’s WordPress user ID, email address, and display name are sent to PostHog.
- WooCommerce events (optional). If enabled, add-to-cart, checkout-started, and order-completed events are sent, including product IDs, product names, quantities, order totals, and currency.
- Reverse proxy (optional). If enabled, visitors’ tracking requests pass through your server to PostHog, with the visitor’s IP address forwarded in the
X-Forwarded-Forheader. The posthog-js library files are still loaded from PostHog’s asset host. - Feature flags (server-side). When a page uses the
[posthog_flag]shortcode or the flag helper functions, your server sends your project API key and the visitor’s PostHog ID (or WordPress user ID for logged-in users) to PostHog’s/decideendpoint. Results are cached for 60 seconds. - Setup wizard. When you validate your key or send a test event, your server sends the project API key, and for the test event your user ID, site URL, and plugin version, to PostHog.
- In-dashboard analytics (optional). When an administrator opens the analytics page or dashboard widget, your server sends read-only queries to PostHog’s Query API using your personal API key and project ID. Results are cached for 5 minutes.
PostHog’s terms of service: https://posthog.com/terms
PostHog’s privacy policy: https://posthog.com/privacy
If you self-host PostHog, the data goes only to your own instance, and your own terms and privacy policy apply.
Screenshots
Installation
- Upload the plugin to
/wp-content/plugins/pressed-hog-analytics-for-posthog, or install it via the Plugins screen. - Activate it — you’ll be taken straight to the setup wizard.
- Follow the wizard: pick your PostHog region, paste your project API key (starts with
phc_), choose tracking and consent options, and send a test event.
You can re-run the wizard any time from the “Setup wizard” link on the Plugins screen, or manage everything on Settings Pressed Hog.
FAQ
-
Where do I find my project API key?
-
In PostHog, open Settings Project. The key starts with
phc_and is safe to expose publicly. -
Does this work with self-hosted PostHog?
-
Yes — choose “Self-hosted / custom” as the host and enter your instance URL.
-
Does the plugin send any data to PostHog on its own?
-
Only what you enable. The tracking snippet runs in visitors’ browsers; the only server-side request is feature flag evaluation (when you use the shortcode or helpers), sent to your configured PostHog host.
-
Does the reverse proxy work on any host?
-
It needs pretty permalinks enabled (Settings Permalinks). Every tracked event then passes through your server as a lightweight relay to PostHog — fine for most sites, but consider a CDN-level proxy for very high-traffic sites.
-
How do the QR codes track scans?
-
Each trackable link appends standard UTM parameters (source, medium, campaign) plus a unique
phg_qrid to your destination URL. When someone scans the code and lands on your site, posthog-js captures those parameters on the$pageviewevent, so you can break scans down by campaign — or by individual QR code — in PostHog. The QR image itself is generated in the visitor’s/your browser; the URL is never sent to an external QR service. -
Where are my links stored, and can I export them?
-
They’re saved in your WordPress database (the
pressed_hog_linksoption) and listed on the QR Codes page. Use “Download sheet (CSV)” to export every link — label, destination, full tracked URL, UTM values, tracking id, and created date — as a spreadsheet you can open in Excel or Google Sheets. -
Is my personal API key safe?
-
It is stored in its own non-autoloaded WordPress option. Public tracking requests load a separate settings option and do not retrieve the credential. It is only ever used server-side (never printed on the front end). Create it with the read-only Query scope so it can’t modify anything.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Pressed Hog – Analytics for PostHog” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Pressed Hog – Analytics for PostHog” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
0.3.2
- The optional PostHog shared dashboard is now linked from the analytics page instead of embedded in an iframe.
- The reverse proxy now relays only PostHog’s JSON API responses; library files load directly from PostHog’s asset host.
- Text domain changed to
pressed-hog-analytics-for-posthogto match the WordPress.org plugin slug. - All admin output is escaped at the point of output.
- Fixed a PHP deprecation notice on the setup wizard screen.
0.3.1
- Renamed to “Pressed Hog – Analytics for PostHog”; the admin menu is now labelled “Pressed Hog” and no longer sits at the top of the menu.
- The tracking snippet, settings script, and dashboard-widget styles now go through the WordPress script and style loaders instead of inline tags.
- With a consent mode on, posthog-js no longer stores cookies or localStorage until the visitor consents.
- The “connect PostHog” reminder now appears only on the Plugins screen.
- Uninstall now also removes WooCommerce order meta and cleans up every site on a multisite network.
- Documented the external services the plugin uses.
0.3.0
- New “QR Codes” page (under the PostHog menu): create trackable links from your own URLs with UTM tags and a unique tracking id, generate QR codes, save your links, and download the list as a CSV spreadsheet. QR codes are generated entirely in the browser and can be downloaded as PNG or SVG.
0.2.1
- Security hardening: restrict the reverse proxy to known PostHog paths and methods with a request-body size cap; validate the wizard’s key-check host (HTTPS only, via wp_safe_remote_post) to prevent internal-network probing; stop exposing the personal API key in the setup wizard’s page HTML and keep it out of the autoloaded options cache; reject numeric anonymous feature-flag identifiers.
0.2.0
- Reverse proxy for ad-blocker-resistant tracking through your own domain.
- In-dashboard analytics page, dashboard widget, and optional embedded shared dashboard.
0.1.0
- Initial release.