Live Debug Console

Monitor and inspect live inbound events to troubleshoot Trigger and integration behaviour.

The Live Debug Console is a real-time event feed for your Fast Track CRM environment. It lets you view, filter, and inspect incoming Real-Time Events as they arrive on the platform — making it an essential tool for integration validation, testing, and day-to-day troubleshooting.

Using the Live Debug Console

Navigate to Settings > Integration Hub and select the Live Debug Console tab. Click Start in the top-right corner to begin streaming events in real time.
​
​
Once the console is running, any Real-Time Events sent from your site will appear immediately in the feed below. Each row shows the Event Type, User ID, Origin, and Timestamp for every event received.
​
​

Filtering the event stream

Use the coloured filter buttons at the top of the console to show or hide specific event types. Available filters include:
  1. Registration
  2. User Update / User Update V2
  3. Login
  4. Payment
  5. Lottery
  6. Bonus
  7. Game Round
  8. User Block
  9. User Consents
  10. Casino
  11. User Balances Update
Click a button to toggle that event type on or off. This is especially useful when you want to focus on a specific flow without trawling through unrelated traffic.
You can also use the Filter by User ID field to narrow the feed to events from a specific player.

Inspecting a payload

To inspect the full payload of an event, click on any row in the feed. The raw JSON will appear in a panel on the right-hand side, showing all fields and values received — useful for confirming expected data is present and correctly formatted.
You can pause the stream at any time by clicking Pause, allowing you to inspect events without the feed continuing to scroll.

Prerequisites

Your Operator API must be configured before using the Live Debug Console. If the console starts but no events appear, this is the first thing to check.

Common use cases 🖥️

Validating your integration
Use the console to confirm that Real-Time Events are being delivered into your environment — particularly useful in staging or UAT. If you start the console and see nothing, it's a strong signal that the stream connection is down or events aren't being consumed.
Live monitoring during testing
Start the console before triggering test events so you can watch them arrive in real time. This is the standard way to confirm "we sent X" → "Fast Track received X".
Payload inspection
Pause the console, select an event, and inspect its JSON payload to verify the expected fields and values are present. This is particularly helpful when debugging invalid event errors.
Debugging downstream behaviour
If an event appears in the console but an Activity or Trigger doesn't fire, the issue is likely downstream — check validation rules, event mapping, or Activity configuration rather than the ingestion layer.
Focused troubleshooting with filters
Use event-type filters to isolate a specific flow — for example, showing only Login events while debugging a login-triggered Activity — so you're not distracted by unrelated traffic.
Platform and connectivity health checks
If events stop appearing unexpectedly, the console itself is a useful health indicator. Message queue connection problems, API configuration errors, or queue issues will all prevent events from arriving.