Install the plugin
Select the ZIP file under Plugins → Add New → Upload Plugin and then install and activate it.
BlogTraffic for WordPress
Your blog writes.
Your blog writes.
The plugin counts.
Set up BlogTraffic directly in WordPress, with central settings, HTTPS tracking and an optional sidebar counter.
WordPress 6.0 or laterPHP 7.4 or laterVersion 1.1.2
In three steps
From installation to statistics.
You need a BlogTraffic account with a valid user ID and an accessible tracking domain.
Enter your user ID
Under Settings → BlogTraffic enter the numeric user ID, choose the correct tracking domain and enable tracking. New installations initially start without counting.
Check the count
Clear the page cache and open a public page while signed out of WordPress. Then check the figures in the BlogTraffic dashboard for confirmation.
Connection test: The WordPress test requests a neutral pixel from the server. It checks reachability, but confirms neither account activation nor a counted browser visit.
One integration. Clear settings.
- Tracking can run independently of the visible sidebar widget.
- Signed-in users are excluded by default. Admin pages, feeds and previews are not counted.
- Do Not Track and Global Privacy Control are respected.
- The connection test and domain selection are available directly in settings.
Remove additional manual BlogTraffic snippets so that only one integration is active per page. Signed-in users must be excluded from full-page caching.
Keep using your existing widget.
Back up the existing plugin files before replacing them. Deactivate the old plugin, install the new package and activate it. Both generations must not be active at the same time.
Existing user IDs and widget settings are preserved. The sidebar ID stays the same; edit the title under Settings → BlogTraffic from now on.
Existing installations initially use blogtraffic.de over HTTPS. blogtrack.de can be selected once its tracker is configured.
Replacing individual files
In older flat installations, blogtraffic.php and the new assets folder are directly under wp-content/plugins/. In a plugin-directory installation, replace both inside that directory. The existing language packages include the required files; the current interface follows the WordPress language.
What the plugin collects.
The plugin loads a local JavaScript file and sends at most one pixel request per HTML page load. It sends the public user ID, the page identifier main and a random value to prevent image caching.
The plugin sets no cookies or local identifiers. It sends no page titles, visited URL parameters, screen data or referrers. The tracking server technically receives the IP address and HTTP headers; processing there depends on its server configuration. Existing cookies for the tracking domain may also be sent.
Hits are not unique people. In the standard cookieless mode, hits and impressions are equal; repeated page loads are counted again.
No counting takes place without JavaScript, with blocked pixels or when Do Not Track or Global Privacy Control is active.
Connect your existing consent solution
With “Wait for consent” enabled, counting starts only after a signal from the existing consent solution. The plugin does not provide its own consent dialog.
document.dispatchEvent(new Event('blogtraffic:consent'));
// Revoke consent:
document.dispatchEvent(new Event('blogtraffic:revoke'));If consent has already been given before the plugin loads, set window.BlogTrafficConsent = true beforehand. Do Not Track and Global Privacy Control still take precedence.