Takt Analytics for WordPress

📚 Documentation — taktlytics.com/docs/wrappers/wordpress

The official WordPress plugin for Takt, privacy-first web analytics. It injects the Takt browser snippet into your site and — when WooCommerce is active — reports completed orders as server-to-server purchase events with revenue.

Takt itself is a managed service hosted in Europe; the plugin connects your site to it. Only the measurement script can be served from your own domain (the asset mode below).

• Snippet injection into wp_head (inline, CDN, asset served from your own origin, or ES-module SDK).
• Autocapture for outbound links, file downloads, tagged events (data-takt-event) and 404s.
• WooCommerce purchases sent server-to-server, so revenue is tracked even when an order completes off-session (IPN, admin, cron).
• No bundled HTTP stack — server-to-server requests go through WordPress' own wp_remote_post.
• Dependency-isolated — all Composer dependencies are namespaced under Takt\WP\Vendor\, so the plugin never clashes with another plugin's PSR-7/HTTP libraries.

Requirements

• WordPress 6.0+
• PHP 8.1+
• WooCommerce (optional, for purchase tracking)
• A Takt account: a site domain, and — for purchase tracking — an API key

Installation

1. Download takt-analytics.zip from the latest release.
2. In WP Admin → Plugins → Add New → Upload Plugin, upload the ZIP and activate it.
3. Open Settings → Takt Analytics and set your domain. That alone is enough for the browser snippet: it posts to https://taktlytics.com/api/event by default. To also report WooCommerce purchases, fill in the ingest origin (https://taktlytics.com) and your API key.

Or via WP-CLI:

wp plugin install takt-analytics.zip --activate

The release ZIP is self-contained: it bundles takt-core-php and its PSR-7 dependencies (scoped), so no composer install is needed on the server.

Configuration

Settings → Takt Analytics — 19 settings, all stored in the single takt_settings option. Defaults below are what a fresh, never-saved install uses.

Ingest origin vs. collect URL

Two different things share the word "endpoint" across Takt, so the plugin is explicit about which one it wants:

• The browser snippet posts to a full collect URL. It is not configurable here and defaults to https://taktlytics.com/api/event. Setting a Script origin makes the tracker derive {script origin}/api/event instead, which is how a first-party proxy is used.
• The Ingest origin setting is server-to-server only, and is an origin: /api/event is appended to it on every send.

Pasting the full collect URL into the Ingest origin field is the obvious mistake, so it is accepted: a trailing /api/event is folded back to its origin when the settings are saved and read. Both forms therefore post to exactly one /api/event, and origins already stored keep working unchanged.

API key via wp-config.php

For environments where secrets must not live in the database, define the key as a constant. It takes precedence over the stored value and the admin field becomes read-only:

define('TAKT_API_KEY', 'your-key');

URL scrubbing via wp-config.php

scrubUrl is a raw JavaScript function injected verbatim into the page, so it is dev-controlled only — it lives in a constant, never in the database or the admin UI, and only takes effect in sdk mode:

define('TAKT_SCRUB_URL', '(u) => u.split("#")[0]');

Privacy

WooCommerce purchase events are sent from your server to the configured Takt ingest origin and include the customer's IP address and user agent for attribution. They are forwarded, never logged by the plugin. The browser tracker honours Do Not Track (unless Ignore Do-Not-Track is on) and a takt_ignore localStorage opt-out.

Development

composer install
composer check        # php-cs-fixer + phpstan + phpunit
composer test         # unit tests only

Building the release ZIP

bin/build.sh          # → dist/takt-analytics.zip

This installs production dependencies, scopes them under Takt\WP\Vendor\ with PHP-Scoper, regenerates the autoloader, smoke-tests it and packages the ZIP.

End-to-end tests

The E2E suite spins up a real WordPress + WooCommerce via wp-env, runs Playwright against it and asserts the snippet, the pageview beacon and a WooCommerce purchase event (captured by a mock ingest server):

npm install
npx playwright install chromium
npm run env:start
npx wp-env run cli wp eval-file wp-content/plugins/takt-wordpress/e2e/setup-wp.php
npm run e2e

License

MIT