Services (v2) – Reporting Guide (Migrate from old widgets)

Overview

We’ve introduced Services (v2) Reporting, a dedicated module within the Reporting Dashboard for all service-based insights. This replaces the earlier service-related widgets that were part of the Calendars/Meetings module.

The new module (identified by purple icons ) provides a more structured and scalable way to track appointments, revenue, staff performance, and more.

What’s New in Services (v2)

The Services (v2) module includes a wide range of widgets, such as:

• Appointment count by service
• Appointment count by service category
• Total revenue from service booking
• Revenue by service
• Revenue by service category
• Average order value (services)
• Top grossing staff (services)
• Top performing service locations
• Cancelled service revenue
• Coupon redemptions (services)
• Revenue from coupons (services)
• Top coupon codes (services)

These widgets are designed to give you deeper visibility into service performance and revenue trends.

What Changed from the Previous Setup

Previously, service-based reporting was available through two widgets under the Calendars/Meetings module:

• Appointment Count by Service
• Appointment Count by Service Category

These older widgets (shown with standard calendar icons) are being moved to Services (v2) and will no longer function in their current form after the update.

Old:

New:

Action Required (If You Used Old Widgets)

If you previously added the older service widgets to your dashboard, you will need to update them.

Steps to Update

1. 1Go to your Reporting Dashboard
2. 2Locate and delete the following widgets:
3. 3Click Add Widget
4. 4Navigate to the Services (v2) module (purple icon section)
5. 5Add the relevant new widgets based on your reporting needs
6. 6Save your dashboard

Important Notes

• The old widgets will stop displaying data after the release
• Your underlying data is not affected
• You must use the new Services (v2) widgets to continue viewing service-related reports

Before you begin

“Services (v2) – Reporting Guide (Migrate from old widgets)” is part of the Reporting → Reporting Dashboard area in Adaptive AI. Use the central reporting view and saved reporting settings. Reports are only useful when their date range, time zone, filters, source records, and attribution rules match the question being asked. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Define the business question and the exact metric, record type, status, owner, campaign, or channel needed to answer it.
• Set the account time zone, reporting date range, comparison period, and filters before interpreting totals or trends.
• Confirm the underlying contacts, appointments, opportunities, messages, payments, or events are being recorded consistently.
• Identify attribution windows, bot filtering, exclusions, and status definitions that can change what the report counts.
• Choose a small set of known source records that can be compared directly with the report output.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Run the report with the intended filters and compare several results with their underlying source records.
2. 2Change one filter at a time and confirm the totals respond in a way that matches the documented definition.
3. 3Check the same reporting period after export and verify columns, time zones, statuses, and totals remain consistent.
4. 4Confirm users with the intended role can access the report without seeing data outside their responsibility.
5. 5Record the report definition and date so later comparisons use the same rules rather than a visually similar configuration.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Clear hidden filters and verify the date range, time zone, owner, pipeline, status, and channel when expected records are missing.
• Allow for processing delay when the underlying event occurred recently, then compare event and report timestamps.
• Check whether bot filtering, attribution rules, deleted records, test activity, or duplicate contacts explain a count difference.
• Compare a single known record end to end before treating an aggregate mismatch as a reporting defect.
• Confirm the selected report version or migrated widget uses the same metric definition as the report being replaced.

Best practices

• Use a small set of documented decision-making metrics instead of dashboards filled with unrelated numbers.
• Name saved reports for the audience, metric, period, and filter scope so similar reports are not confused.
• Separate test activity from production reporting and establish consistent rules for won, lost, canceled, spam, and duplicate records.
• Review source-data quality before optimizing a campaign or team based on the dashboard.
• Annotate major launches, tracking changes, and outages so unusual trends can be interpreted later.