WBAMS reports

Insights include daily performance, income forecasts, annual income, new customers, ticket feedback scores, and other operational reports. A selected report must preserve its report parameter and render the intended report rather than redirecting to the generic index.

Measurement model

  • Revenue: invoiced, collected, recurring, overdue, refunded, credited, and forecast.
  • Customers: new, active, retained, expanded, downgraded, and canceled.
  • Operations: automation completion, exceptions, queue delay, and manual interventions.
  • Support: volume, first response, resolution, reopen rate, and feedback score.

Google Analytics and Search Console

Configure Google through WBAMS Sign-In Integrations, use the same Google account that owns the Analytics and verified Search Console properties, grant only required scopes, and return the authorization code when prompted. The login artwork must be served from a valid local or official asset URL.

Privacy

Document what is collected, obtain consent where required, avoid placing customer financial or support content in analytics events, and review data-retention settings for every provider.

The admin area asks each administrator whether WBAMS may use anonymized tracking to improve the product. Since 1.9.8 the answer is recorded for that administrator:

  • Declining is written down, so the card does not come back on another browser, another computer or after cookies are cleared. Agreeing is kept the same way.
  • The ✖ means "not now": it keeps the card away for thirty days without recording an answer.
  • An installation that switches this tracking off in settings.php is not asked at all.

The 1.9.8 migration, upgrade198.sql, lets the stored answer be empty, and moves administrators who held the old default to "no answer yet": they are asked once more, and whatever they choose is kept. Administrators who had agreed are not asked again.