BigCommerce store events
When a configured activity occurs in your BigCommerce store, the webhook sends the event to Auditor. The event is processed, stored in the audit log, and made available on the dashboard.
BigCommerce App Store
Auditor watches your store in real time and writes down what happened, who did it, and what the value was before and after. Search it, filter it, export it.
webhook capture · no theme edits · read-only scopes
What Auditor captures
Auditor collects BigCommerce events, staff activity and application logs to give you a clearer view of what happened in your store.
When a configured activity occurs in your BigCommerce store, the webhook sends the event to Auditor. The event is processed, stored in the audit log, and made available on the dashboard.
When you need to know who performed an activity, Auditor can scrape the BigCommerce Staff Action Log and store the matching staff activity for further investigation.
Open an event from the dashboard and view more details. Auditor uses relevant event information, such as the resource ID and timestamp, to find the corresponding staff activity.
Monitor application activity and system-level logs separately, making it easier to review errors, processing issues, and other operational events.
The path of one event
Every store event is captured and logged, with staff details available when you need to trace who made the change.
Install the app and complete token verification to securely connect your BigCommerce store with the audit system.
When an activity occurs in your BigCommerce store, the configured webhook sends the event details to the audit system.
The received event is processed and stored with important details such as the event type, resource ID, store, and timestamp.
Your dashboard displays the recorded store activity. Search and filter events by date, user, or event type to find the change you need.
Select an event and choose “More Details” to investigate the change and find additional information about who performed it.
The system uses the event's resource ID and timestamp to match it with BigCommerce Staff Action Log activity and display the corresponding staff details.
Investigation
Review activity in your dashboard, then investigate individual events when you need to understand what happened and who performed the change.
Read the user manualAuditor starts recording the moment it's installed. It can't recover what happened before that.