WBAMS can send page and event data to Google Analytics and to Mixpanel. They answer different questions — Google Analytics tells you about traffic, Mixpanel about what people did — and they are configured in different places.

Google Analytics

Google Analytics is an addon module. Activate it, then configure it.

  1. In Google Analytics, create a property for your site if you do not have one, and open Admin → Data streams.
  2. Select the web stream for your domain and copy its Measurement ID. It looks like G-XXXXXXXXXX.
  3. In WBAMS, open Settings → Addon Modules, find Google Analytics, and activate it.
  4. Open its configuration and set Analytics Version to Google Analytics 4.
  5. Paste the ID into Measurement ID.
  6. Leave Tracking Domain empty unless you track across several domains, in which case enter the domain in the form example.com.
  7. Save, then grant the addon to the administrator roles that should see it.
Universal Analytics is the old one.

The version selector still offers Universal Analytics and Classic Analytics for installations that have not migrated. A UA-XXXXXXXX-X ID belongs to Universal Analytics; a G- ID belongs to GA4. Pick the version that matches the ID you pasted or nothing will be recorded.

Confirm it is working

  1. Open your public site in a private window.
  2. In Google Analytics, open Reports → Realtime. You should appear within about thirty seconds.
  3. If nothing arrives, view the page source and search for the measurement ID. If it is absent, the addon is not active or has no access to that role; if it is present, the problem is at Google’s end — usually a filter or the wrong property.

The dashboard widget

Separately from tracking your public site, the admin dashboard can show Google Analytics reports in a widget of its own. It reads a GA4 property through a Google sign-in, and it is not the same thing as the tracking addon above — one sends data out, the other reads it back.

Two switches decide who sees it, and both have to be right.

  1. Open Settings → Theme Appearance and find the Role access card. Turn Enable Google Analytics (GA4) on for each administrator role that should have the widget. A role without it never gets the widget at all.
  2. Open the dashboard, connect the widget to a Google account, and choose the property and data stream. This is done once, for the installation, by an administrator who can change the widget’s settings.

The widget keeps a permission list of its own — which tabs it draws, whether the date range can be changed, whether graph options can be edited. A role that is given the tool starts with the viewing permissions and without the two that change the widget’s settings or hand permissions to other roles; those stay with administrators who can configure administrator roles. To refine a role, open the widget’s own permissions panel from its Graph Options menu.

Changes apply the next time the workspace is loaded.

An administrator who is already signed in sees the widget appear or disappear on the next dashboard load, not immediately.

Mixpanel

Mixpanel receives product events from WBAMS. It is configured with a project token, which is a public value and safe to place in the page.

  1. In Mixpanel, open the project you want to send to.
  2. Go to Settings → Project settings and copy the Project Token.
  3. In WBAMS, open the analytics settings and paste the token.
  4. Save, then trigger an event — signing in is enough — and watch Mixpanel’s live view.
The project token is not the API secret.

The token is meant to be public and identifies the project. The API secret is a credential that can read and delete your data. Never place an API secret in WBAMS configuration or anywhere it reaches a browser.

What is collected

Analytics runs in the visitor’s browser and sees what any web page sees: the page, the referrer, the device, and events the product raises. It is not a route into your billing data. Decide deliberately whether to run it on signed-in pages as well as public ones, tell your customers in your privacy notice, and honor consent where your jurisdiction requires it.

Analytics or reports?

Analytics answers questions about traffic and behavior; it will never agree exactly with your billing figures and is not meant to. For revenue, orders and customer counts use Reports and insights, which reads the operational database directly.