Skip to main content
All CollectionsCompliance automation
Tracking Device and Browser Events with Swif

Tracking Device and Browser Events with Swif

Updated yesterday

Swif’s Event Report page centralizes all significant device or browser events, such as USB connections, app usage, battery alerts, or security notifications. By deploying the relevant tracking policies to your devices, you can gather event data and then review it in one convenient dashboard.

1. Enabling Event Tracking

  1. Create or Edit a Policy

    • In the Swif console, go to Device ManagementPolicy.

    • Create a new policy or edit an existing one.

  2. Enable Tracking

    • Depending on the event type (USB usage, browser app usage, device reboots, etc.), ensure the matching tracking policy is switched on or included. (Note: Tracking policy is coming soon to Windows and Linux. You can find Mac's one as images below.)

  3. Assign Policy to Devices

    • Select which devices or device groups need these tracking settings.

  4. Save and Deploy

    • Once saved, Swif will begin collecting relevant events from those devices at their next check-in.

Note: Without a deployed tracking policy, no events will appear in the Event Report page for that category.


2. Viewing the Event Report

  1. Navigate to the Reports

    • In the left sidebar, select ReportsEvent Logs (naming may vary by your Swif version).

  2. Filter the Event List

    • Use the Event Type dropdown to see specific categories (e.g., USBConnect, AppUsage, BatteryLow, etc.).

    • Adjust Date Range to narrow the time window.

    • Enter keywords in the Search bar to locate specific events.

  3. Click an Event to see more details on the right-hand side of the screen.


3. Event List Details

Your event table may show rows like:

  • USBConnect (#xxxxx)

    • Timestamp (e.g., 14 Feb 2025 23:43)

    • Value (e.g., Port USB B2)

    • Device (e.g., MacBook Air, with a clickable link to device details)

  • AppUsage (#xxxxx)

    • Timestamp (e.g., 14 Feb 2025 23:43)

    • Value (e.g., Chrome, Duration: 24 mins)

    • Device (clickable device ID)

  • BatteryLow, SecurityAlert, UserAccessRevoked, etc.


4. Event Detail Panel

When you click an event in the table, a detail panel slides in with additional information:

  1. Event ID: Unique reference number for that event.

  2. Timestamp: Date/time the event was detected.

  3. Value: Additional details, such as USB port name, app usage duration, or a patch version.

  4. Device: Shows the device name and link (e.g., “Apple MacBook Air 14" 2022 #F022A323M2321”).

  5. Assigned To: If there’s a known user assigned to that device, their name is clickable, linking to the user’s profile or details.

  6. Policy: If the event is triggered by a specific policy (e.g., “External Device Connection (USB)”), it will show the policy name. Clicking it displays that policy’s configuration.

  7. Source: Indicates whether the data came from the Device Agent, Browser Extension, or another input method.


5. Generating Reports

Above the event table, you’ll see a Generate Report button:

  1. Click “Generate Report”

    • Exports the current list of events (respecting your chosen filters) into CSV, PDF, or other formats.

  2. Share with Stakeholders

    • Use the exported data to share with security teams, compliance officers, or management.


6. Common Use Cases

  • Monitoring External Drives: With USB tracking enabled, quickly spot unauthorized USB devices or see how often users connect external drives.

  • App Usage Insights: See which apps are heavily used, how long they run, and by which user or device.

  • Security / Compliance: Detect repeated failed password attempts or policy-based security alerts.

  • Troubleshooting: If a user’s device repeatedly reboots or disconnects, the event log can give clues about potential hardware or software issues.


7. Troubleshooting & Tips

  • No Events Showing?

    • Confirm that the correct tracking policy is deployed to the device group.

    • Check if the device is online and the Swif Agent is running.

    • Ensure the date range covers the timeframe of interest.

  • Policy or Device Link Missing?

    • If the device is unassigned or the event doesn’t map back to a policy, it may show “Unassigned” or a blank policy.

    • Ensure the device was enrolled with the correct user and policy assignment.

  • Time Zone Differences

    • Event timestamps might reflect the device’s local time or a standard reference. Verify time zone if needed.


8. Summary

Swif’s Event Report page is a powerful tool for tracking device and browser activities, from USB connections to app usage durations. By deploying the relevant tracking policies and reviewing the logs in this report, you can maintain a comprehensive view of what’s happening on your organization’s devices. If you have further questions, please contact Swif Support.

Did this answer your question?