Hub reporting and automation

Review one site's activity

Sign into the company that owns the site, or use an active exact-site delegation. You can only see records within your member and client scope.

1. Open Reporting.
2. Under Filters, choose Range and Store. For a specific period, choose Custom dates and fill in the start and end dates.
3. Narrow the results using Event, Outcome, Severity, Stream, Flow, or Search as needed.
4. Select Apply filters.
5. Review the summary and connected-store detail before deciding what needs investigation.

Example: select one shop, a seven-day range, and Failed under Outcome to investigate recent failures. An empty result means no matching available records; it does not prove the site has no problems.

Create and test an alert

Use an owner, staff, or member account permitted to manage automation. Have the intended email recipient or webhook URL ready.

1. Open Automation and add a destination.
2. Give it a recognizable Destination name, choose Email or Webhook, and fill in the matching address.
3. Choose the permitted client scope and select Add destination.
4. Under Create a rule, enter a Rule name and choose a Trigger.
5. Set the site or client scope, threshold, and any relevant event conditions.
6. Choose the Destination and select Create rule.
7. Use Send test on the rule, then check the recipient and Delivery history.

Expected result: the rule is saved with the intended scope, and the test has a visible delivery result. A successful test proves the delivery path, not that a real event has already matched the rule.

Example: name a rule Shop checkout failures, select Checkout failures reach a threshold, scope it to the shop, and send notifications to the store's support mailbox. Choose the threshold to fit the activity you want reviewed.

If a report or alert is missing

Check the company, selected site, date range, and active filters. Delegation exposes the granted site, not the owner's other sites.

For an alert, check the rule's scope and conditions, destination address, and delivery result. Investigate failed delivery before repeatedly sending tests. Keep webhook credentials and raw sensitive logs out of support messages.