Trails provide a comprehensive history of actions, offering valuable insights into customer activity and operational efficiency.
Navigation: Settings > Trails
Trails can be filtered using the Show Filters button.
What Information is Recorded in Trails?
Each entry in the Trails list provides a snapshot of an event, including:
Date: The date and time the event occurred.
Event Type: The type of event, such as "General Entry," "Class Check-in," or "Membership Purchase."
Check-in Method: Whether the event was a "Self Check-in" or processed by a "Front Desk Operator."
Customer Name: The name of the customer involved in the event.
Family Members (Juniors): If applicable, lists any junior family members associated with the event.
Operator: The name of the operator who processed the event (if applicable).
Viewing Detailed Trail Information
Clicking on any entry in the Trails list reveals more specific information, categorised as follows:
Details: This section provides specific data related to the event, which may include:
book_as: (Explanation of what this signifies - e.g., Booking type)location: The location where the event occurred (e.g., Wandsworth).location_id: The unique identifier for the location.checked_into: (Explanation - e.g., Specific class or area checked into)membership_id: The ID of the membership used (if applicable).session_credit_id: The ID of the session credit used (if applicable).
Customer Information: This section displays details about the customer involved:
Customer Name
Email
Age
Customer Code
Date of Registration
Who Can Access and Manage Trails?
Only permitted admin users have access to the Trails feature.
Admins can:
View Trails: Browse and search the complete history of events.
View Detailed Information: Click on individual entries to see comprehensive event details and customer information.
Delete Trails: Admins have the ability to delete trail entries. (Caution: Deleting trails is a permanent action and should be done with care.)
Why are Trails Important?
Trails are a valuable tool for:
Auditing: Tracking events for compliance and accountability.
Reporting: Generating reports on customer activity and operational performance.
Troubleshooting: Investigating issues and identifying the root cause of problems.
Customer Service: Providing better support by accessing historical customer data.
Data Analysis: Identifying trends and patterns in customer behavior.
Best Practices for Using Trails
Regular Review: Periodically review the Trails log to identify any unusual activity.
Data Security: Protect access to the Trails feature to ensure data integrity and confidentiality.
Data Retention: Establish a policy for how long trail data is retained.
Frequently Asked Questions (FAQs)
Q: Can I search for specific events in the Trails?
Yes, you can search by names, event, location, admin, date range and custom field
Q: Can I export the Trails data?
Not at present
Q: How often is the Trails data updated?
Trails are updated everytime an action takes place within Clava. Actions recorded include:
Self check-in failed
General entry check-in
Class check-in
Competency enabled
Competency disabled
Customer type created
Customer type updated
Customer type deleted
Customer type toggled
Customer type assignment updated
Customer type assignment removed
Customer type assignments bulk activated
Customer type assignments bulk deactivated