Integration metrics & monitoring
The integration metrics view provides performance data for every connected integration β sync volumes, success rates, and authentication validity. Use it alongside the integration health dashboard for trend analysis and capacity planning.
Audience: Organization administrators and integration managers who monitor connected third-party systems.
On this page
- Before you begin
- Access integration metrics
- Available metrics
- Use metrics to identify issues
- Handle metric anomalies
- Reconciliation
- Export metrics data
- Tips
- Troubleshooting
Before you begin
Permission: You need organization administrator access to view integration metrics.
- Your organization must have at least one active integration configured. If no integrations are active, the metrics view will show no data.
- Integration metrics are available for integrations that report sync activity to Zenoti, including accounting providers, tips payout, inventory suppliers, and payment processors.
Note: Stripe payment processing supports card saving and account health checks. Stripe does not support terminal or card reader connections β payment terminal setup for Stripe uses a separate terminal configuration workflow. For processing payments at the point of sale, see Invoices and Billing.
Access integration metrics
The integration metrics page is accessible from the integration health dashboard.
- Open the integration health dashboard for your organization.
- On any integration card, select View metrics to open the metrics view for that integration.
- The metrics view shows performance data for the selected integration within the configured date range.
Note: The direct navigation path to the integration metrics page is not yet established in the current product version. Use the View metrics entry point from the integration health dashboard.
Available metrics
Sync volume metrics
The following metrics describe the volume and outcome of sync activity for the selected integration and date range.
| Metric | Description |
|---|---|
| Total records processed | Records synced in the selected period. |
| Success rate | Percentage of records synced successfully. |
| Failed records | Count and rate of failed sync attempts. |
| Average sync duration | How long each sync cycle takes. |
| Pending queue size | Records waiting to be processed. |
Connection health metrics
The following metrics describe the current connection state and credential validity for the integration.
| Metric | Description |
|---|---|
| Uptime | Percentage of time the integration was connected and active. |
| Last successful sync | Timestamp of the most recent successful sync. |
| Authentication status | Whether the integration credentials are valid and current. |
| API rate limit usage | Percentage of the provider's API rate limit consumed. |
Use metrics to identify issues
Review the following patterns to diagnose common integration problems:
- High error rate β a sudden increase in failed records usually indicates a change in the external system (account archived, key revoked, schema change). Review error details in the sync log.
- Long sync duration β increasing sync times suggest backlogs or external-system slowness. Break long date ranges into smaller batches.
- API rate limit approaching β reduce sync frequency or batch size. Accounting providers such as Xero and QuickBooks Online enforce daily API call limits.
- Authentication expiry β monitor token validity and re-authorize before expiry to avoid sync disruptions.
Tip: Filter metrics by a specific integration type (for example, accounting or tips payout) to isolate which connected system is contributing to anomalies. Comparing the same metric across two consecutive weeks helps distinguish a one-time spike from a sustained degradation.
Handle metric anomalies
The following table describes common anomalies, their likely causes, and how to resolve them.
| Anomaly | Likely cause | Resolution |
|---|---|---|
| Success rate drops below historical baseline | External-system change, credential rotation, or mapping drift | Open the sync log for the affected integration; follow the integration-specific troubleshooting article. |
| Pending queue grows | Pause active, or provider slow to accept | Confirm no pause is active; reduce batch size if the provider is throttling. |
| Uptime drops below 99% | Repeated outages or network flap | Review provider status; confirm local network path. |
| API rate limit above 80% sustained | Over-frequent sync schedule | Lower sync frequency; use Integration pause scheduling during peaks. |
| Authentication status shows Invalid | Token expired, revoked, or rotated on the provider side | Re-authorize the integration from its setup page. |
Worked example: An accounting integration shows a success rate of 62% on Tuesday, down from 98% the prior week. The failed-records count is 340. Filtering by Invoice Type in the sync log reveals that all failures are for refund records. The accounting provider's chart-of-accounts mapping for refunds was changed by a team member on Monday. Restoring the original mapping and triggering a manual sync resolves the backlog within the sync cycle.
Reconciliation
For each integration, compare aggregate metrics in this view against the provider's own reporting. Each integration's detailed reconciliation steps are in its workflow article; the metrics view is the starting point.
| Source | View | Match key | Cadence |
|---|---|---|---|
| Zenoti | Integration metrics view > selected integration, date range | Records processed per period | Weekly |
| External system | Provider-specific activity or usage report | Records processed per period | Weekly |
Large discrepancies between Zenoti's counts and the provider's counts typically indicate records that errored out before reaching the provider, or records created directly on the provider side that bypassed Zenoti.
Export metrics data
- In the metrics view, set the date range.
- Select Export to download a CSV of the metrics for the period.
- Use the export for reporting, capacity planning, or to share with your integration partner.
Tips
- Review integration metrics weekly as part of your operations cadence.
- Set internal reminders to re-authorize OAuth connections (for example, Xero: 60 days; QuickBooks Online: periodic) before they expire.
- Use the metrics export to spot trends and plan for capacity β for example, rising sync volumes for an accounting provider may indicate you need to adjust your sync schedule or batch size.
- When investigating a drop in success rate, filter the sync log by the date the anomaly began rather than reviewing the entire history. This narrows the scope to changes made around that time.
- Use Integration pause scheduling to prevent sync jobs from running during high-traffic periods, which can reduce API rate limit consumption.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| Metrics view shows no data for an integration | No sync activity in the selected date range, or the integration was not active during that period | Expand the date range; confirm the integration is enabled and has run at least one sync cycle. |
| Export file is empty | No records match the selected filters | Clear all filters and re-export; confirm the date range includes periods with sync activity. |
| Authentication status shows Invalid immediately after re-authorizing | Credentials entered during re-authorization are incorrect, or the provider revoked the token again | Verify the credentials with the provider; check whether the provider requires a specific account role to issue tokens. |
| Success rate is 100% but record counts are lower than expected | Some record types are excluded from the sync configuration, or records were filtered out before processing | Review the sync configuration for the integration to confirm which record types are included; check for any active filters. |