Basicrum - Real User Monitoring

You need a Basicrum collector endpoint and its matching Brum Site ID. Join the free hosted public beta or self-host the single-server community edition.

No. Basicrum provides consent-controlled loading and editable text for the WordPress Privacy Policy Guide, but it does not determine your legal basis, display a consent popup, or configure your privacy notice.

The recommended mode keeps monitoring off until your consent tool reports an allow decision on each page. Automatic connection supports WP Consent API, Borlabs Cookie 3.2+, and CookieYes 3.x. If Basicrum cannot choose one safely, monitoring remains off. For another tool, choose Manual callbacks and use one of the copy-ready integrations in the settings page. Basicrum does not store its own consent choice. Always test both allow and deny decisions.

By default, page and resource URLs may include complete query strings. Enable Strip Query Strings to replace them with ?qs-redacted before sending beacons. URL paths are still collected.

When monitoring runs, Boomerang sets a first-party RT cookie at path /. It contains a random session identifier that links page views, uses a 30-minute session window, and has a rolling seven-day expiry. It uses SameSite=Strict and is marked Secure on HTTPS sites. The opt-out callback removes RT and any legacy BA cookie.

Yes. Basicrum detects shop, product, product_category, cart, checkout, checkout_payment, checkout_success, and account. Standard WordPress values include home, post, page, custom_post, category_archive, tag_archive, taxonomy_archive, author_archive, date_archive, archive, search, and 404.

Test in a private window because administrator tracking is disabled by default. Confirm that monitoring is enabled, the Beacon URL and Brum Site ID are valid, and the consent connection reports an active decision. Check the browser network panel for a request to your Beacon URL. After changing or disabling Basicrum, purge page and CDN caches so they do not serve old HTML.

HTTP beacon URLs are upgraded to HTTPS by default. For local testing only, select Developer Settings > HTTP Strictness > Allow HTTP beacon URLs. Do not enable this on a production site.

Disabling monitoring or deactivating the plugin stops new script injection, but cached pages may continue serving old markup until caches expire or are purged. Deactivation keeps your settings. Uninstall removes Basicrum settings from the current site; it does not delete data already stored by a remote collector. On multisite, configure and remove settings for each site separately.