Written guide
Written course script · documented draft · Live figures and tracking verification pending
Overview
Analytic Center connects website activity with sales, customer conversations and operational work. We'll choose the right report, set its time window, inspect the records behind a result and use Live View to understand visitors currently on the site.
1. Choose a dashboard and date window
Open Analytic Center from App Root. Select the relevant dashboard in the available tabs or More Dashboards. The current catalogue includes Live View, Website, Blog, Workflow, Storefront, Tickets, Leads, Automation, User Account and Email analytics.
Open the date picker. Select a Quick Select preset, or enter Start Date and End Date under Custom Range, then choose Apply Custom Range. Confirm the displayed window after the panel closes. The custom handler checks that both dates exist; choose a start no later than the end rather than relying on it to correct an inverted range.
Choose Refresh and wait for the loading state to finish. If a request fails, use the visible retry action. A failed dashboard is not a valid zero report.
First set the question's time window. A total without its period is easy to misread, especially when a dashboard also includes a current-state figure.
Date preferences are stored locally. On a later visit, an older saved window can be moved forward to end today while retaining its length. For a repeatable historical report, re-enter and confirm the exact dates each time rather than assuming last week's selection is unchanged.
Store Analytics opens the Storefront dashboard; CRM Analytics opens Leads. Embedded analytics may hide the dashboard picker while retaining date and refresh controls. Open Analytic Center when you need the full dashboard selection.
This October 2 capture has Storefront selected. The date picker is shared; choosing dates does not change which dashboard you are reading.
This historical capture shows a label defect: September 1–October 2 inputs appeared as August 31–October 1 in the Chicago-time browser. The empty report is not proof of a successful sale, correct order-boundary inclusion or website tracking. Keep your intended input dates rather than copying the old incorrect label.
2. Inspect website traffic by site, domain or host
Choose Website Analytics. Read the traffic figures with their labels and units, then inspect the trend, top pages and traffic-source distribution.
Open the website filters and choose the intended site, domain or host. The dashboard reloads the chosen period with that filter. Confirm its active label. With no filter, a filterable entry in By Site also opens that site's scope. Remove the active filter to return to the organization-wide view.
The option list is loaded separately from the report. If options fail, retry them rather than concluding no sites were recorded. A site that does not have qualifying tracked visits can also legitimately have no data for the selected period.
Follow these steps
- Open the controlled public site in an independent browser session.
- Visit two identifiable pages using the site's normal navigation.
- Return to Website Analytics and refresh the period containing that visit.
- Select the exact site and inspect its top-page or traffic entries.
- Compare the recorded identity and URLs, allowing for the collection and refresh delay.
Tracking must be active on the tested site. Do not turn this into a claim that opening any arbitrary website automatically appears in Appmint.
3. Use Live View and inspect a visitor's journey
Choose Live View. Its own window selector offers 5 min, 15 min, 30 min and 1 hr; these are recent-visitor windows, separate from the historical dashboard date picker. This view polls about every 15 seconds and offers refresh controls.
Use the visitor table and map as complementary views. Match a controlled visitor by the available identity, site and current URL. Inspect the recorded page, entry page, device/browser, source and activity information. Location data is recorded context, not proof of precise physical whereabouts.
Select View journey on the intended visitor. Follow its recorded sequence rather than combining rows from unrelated devices. View insights is available for known visitors with the required email identity; anonymous traffic does not automatically have a customer history. View raw JSON shows the stored visitor record for troubleshooting.
This is the visitor's recorded context. The journey helps us respond to the page they are using, while the identity tells us whether we can connect it to known customer activity.
Do not describe recent activity as proof the person is staring at that page right now. Check the recorded time and state.
4. Invite a visitor to chat
On the controlled visitor row, choose Engage. Read the target, type a short relevant message and choose Send. The form accepts up to 500 characters. It sends a chat invitation; the widget's Reply button opens chat or registration for an unauthenticated visitor.
Inspect the independent visitor browser. Confirm the invitation appears and that Reply opens the intended chat flow. A staff success notice is not the complete visitor-side result.
Where Start chat is offered, use the intended visitor's action and verify the conversation identity in the chat interface. Do not move from a visitor row to an unrelated inbox thread for the recording.
The individual invitation uses an API request and does not require the staff live-chat socket merely to submit that invitation. An organization-wide Engage broadcast uses the live-chat connection; connect Chat first and use only a controlled audience during a demonstration. Its reach is broader than the selected visitor. Configure the website widget and receiving agent/AI route before expecting a useful conversation.
Live View invitations are distinct from the richer media broadcast controls in the full Chat application. The Chat course covers those, including AI assistance and takeover.
5. Read Storefront, Leads and Ticket reports
Keep a known date window and change dashboards deliberately. Briefly name the question before opening its report.
Storefront Analytics
Inspect Revenue, Top Products, Orders by Status, Revenue by Source, Customer Spend and Returns. Revenue uses the paid/fulfilled order scope shown in the report, while Orders by Status describes orders placed in the period. They need not have matching counts. Use Orders, Products, Customers or Returns to inspect their source records.
On Top Products, use its CSV export when needed and inspect the downloaded rows. Exporting that panel is not an export of every dashboard or a financial ledger. Campaign-source reporting depends on source information recorded at checkout; an absent source is not proof there was no marketing influence.
Leads Analytics
Inspect New Leads per Day, By Status, By Source, Value by Status and Campaigns. A potential lead value is not received revenue. The period's leads may now have statuses reached after they were created. Open Leads and inspect a representative record to understand its current state and source.
Ticket Analytics
Inspect ticket totals and the priority, category and assignee breakdowns. Use the ticket destination to inspect the underlying case. Do not infer a customer's satisfaction from resolution time alone or present a missing metric as measured data.
These links open the corresponding modules; do not assume each chart bar is an implemented filtered drill-down. Show the actual module search/filter needed to find the example record.
6. Compare workflow work and automation execution
Choose Workflow Analytics. Inspect Completed per Day, By Status, By Workflow and By Assignee. Read Open Work Right Now separately: it includes current open work regardless of creation date. It is not the same population as tasks created in the selected period.
Open Workflow boards to inspect an actual task and its stage. A chart is an overview; the board gives the actionable record.
Switch to Automation Analytics. Read Active Automations as the currently switched-on definitions. Runs, Succeeded, Failed and Avg Run Time describe executions; the success/error percentages refer to finished runs. Running or paused runs are called out separately. Runtime includes waits and delays, not just time spent computing.
Inspect Runs per Day, By Automation, By Trigger and Failures. The failures panel gives the latest recorded error for an automation with failed runs. Choose Fix in Automation, open the matching automation and inspect its run details before changing or retrying it.
Workflow tells us where the team's work stands. Automation tells us how automated executions performed. A definition being active does not mean its last execution succeeded.
Do not retry an automation from this analytics lesson. Some actions send messages or create records; recovery belongs to the run-specific procedure in the Automation course.
7. Inspect content, customer accounts and email activity
Blog Analytics covers recorded content performance. Select its period and compare content entries with the actual posts. Publication counts and visitor engagement are different signals; a published article does not guarantee recorded views.
User Account Analytics includes New Customers per Day, Subscriptions by Plan, Revenue by Order Type and What Signed-in Customers Did. Subscription information includes current active state, while paid orders and tracked site events have their respective scopes. Use Customers, Subscriptions or Customer activity to inspect the exact records. This is customer-account reporting, not automatically a complete staff attendance report.
Email Analytics shows Sent, Delivered, Opened and Failed, followed by Sent per Day and Most Sent by subject. Open figures depend on recorded read receipts. Clicks, replies and unsubscribes are not tracked as those metrics in this dashboard; do not describe their absence as zero.
Choose Communications to inspect a message's delivery state. A queued message, a delivered message and a recorded open are different events. Use a controlled recipient and its actual message before narrating a delivery example.
8. Make the report reproducible
Record the organization, dashboard, exact dates, site filter if used, refresh time and source-record identities for any finding. When comparing two reports, first align their periods and definitions. Current-state totals may legitimately differ from period-based counts.
If a figure seems wrong, inspect a small known set of underlying records. Check statuses, currencies where relevant, event dates, filtering and whether the event is tracked. Report the concrete mismatch rather than editing source records just to make a chart look right.
Analytic Center provides predefined reports. To build your own aggregation and layout, use the Dashboard Builder course. Do not promise a custom query editor in these predefined panels.
Limitations and checks
Choose the report for the question, confirm its scope and use the source records to act on the result. Live View gives immediate visitor context; historical reports help you understand patterns over a chosen period.
Source reviewed: AnalyticsHome, DateRangePicker, dashboard-config, the dashboard components, LiveViewDashboard, live-visits-table and EngageForm. Pending live proof: tracked visitor identity, all report definitions against controlled records, scope changes, CSV output, invitation receipt and permission boundaries. This draft reports source behavior, not a new end-to-end analytics test.
Limitations and checks
The two inspected captures demonstrate the date selection and resulting Storefront report in a historical rehearsal. Current Website filtering, controlled visit detection, visitor invitation, nonzero metric reconciliation, Workflow and Automation reports, content/user/email dashboards and repeatable historical comparisons still need fresh action/result evidence. No synthetic figures or generic landing screenshot are counted as those outcomes.