Connect WordPress to your own HTTPS Umami server. A dashboard widget displays hourly visits for the last 24 hours, visitor estimates, page views, average visit duration and bounce rate.
Browse pages, browsers, languages, operating systems, devices and visitor countries. A configurable share URL opens the full Umami report in a new tab.
Features:
- Automatic page views and configurable link/button/contact/download events.
- Optional scroll milestones and form submission attempts; successful Contact Form 7 submissions.
- Official Umami real-user performance collection: LCP, INP, CLS, FCP and TTFB.
- WooCommerce product, cart, checkout and paid order confirmation events; HPOS compatibility.
- Server-side report requests, encrypted API keys, capability and nonce checks.
- English source strings with bundled Portuguese (Portugal) translations for PHP and JavaScript.
- No analytics data or credentials are sent to WebDig. Data goes to the Umami server you configure.
Requirements: a self-hosted Umami server version 3.2 or later; HTTPS connectivity from WordPress and visitor browsers. Dashboard access needs an API key or a valid Bearer token. Use a separate Umami account that can only access the relevant website.
External service and privacy
The plugin loads the official tracker from your configured server's /script.js endpoint. The tracker sends page views, event data, browser/device information and, when enabled, performance measurements to that server. It uses the visitor IP for Umami processing and geographic estimates. Refer to your Umami server's privacy policy and configuration. Umami documentation:
https://docs.umami.is/docs/ . No central WebDig analytics service is required.
Automatic tracking excludes form values, customer names, customer emails and addresses. URLs exclude query strings and fragments, including order keys; this also excludes UTM attribution from URLs. User-supplied custom event data remains the site owner's responsibility.
Purchase deduplication stores an order marker in the visitor's localStorage. The plugin does not integrate a consent banner or wait for consent. Its analytics settings do not determine your website's legal obligations.
Purchase tracking scope
Purchases are tracked in the browser when the order is paid and the customer returns to a valid order confirmation URL. The order key is verified and is not sent to Umami. Delayed bank-transfer/Multibanco payments are not tracked through a payment webhook. Reloads are deduplicated in the same browser, but cross-device or cleared-storage duplicates remain possible. Refunds do not amend the original Umami event. Analytics revenue is not an accounting record.
Legacy AJAX cart events and WooCommerce Blocks events are supported. Non-AJAX product form submissions are recorded as add_to_cart_attempt, not confirmed cart additions. Custom cart extensions can require their own integration.
Portuguese (Portugal) documentation is included in readme-pt_PT.txt. / A documentação em português de Portugal está incluída em readme-pt_PT.txt.
- Upload the ZIP in Plugins > Add New > Upload Plugin and activate it.
- Create a website in your Umami instance and copy its Website ID.
- Open WebDig.DEV Analytics in the WordPress admin menu.
- Enter your server base URL, Website ID and report API key. Enable tracking.
- Optionally enter the Umami share URL and select the tracking features you need.
- Remove other Umami snippets/plugins and clear site/CDN caches.
- Open Dashboard > Home to view the statistics widget. If hidden, enable it in Screen Options.
- Test tracking in a private browser window. Administrators are excluded from tracking by default.
Plugin activation, tracking and widget visibility are separate. Activate the plugin on the Plugins page, then enable tracking in its settings to start collecting visits. Showing or hiding the dashboard widget does not start or stop tracking. Statistics are displayed in the WordPress administration area and Umami, not on public site pages. The API key is required for dashboard reports, but not for collecting visits.
Settings remain when deactivating or updating the plugin. Uninstalling deletes this site's plugin settings and local report caches. It does not delete data on your Umami server. Multisite installs must be configured separately per site; network-wide provisioning is not included.