---
title: "Live Event Debugger - Serpwise Documentation"
description: "Watch conversion events flow through the gateway in real-time. Debug integration issues, verify event data, and monitor delivery during setup."
url: "https://serpwise.ai/docs/tracking-debugger/"
source: "https://serpwise.ai/docs/tracking-debugger/"
---
[Back to Serpwise](/)

Serpwise Documentation

Connect · Configure · Execute

Search documentation

`/`

No documentation found.

↑↓ Navigate Enter to open

Browse documentation

The **Live Event Debugger** provides a real-time stream of conversion events as they are processed by the gateway. Use it during integration setup to verify events are firing, inspect data field coverage, and diagnose delivery failures without waiting for events to appear in the Event Log.

Access the debugger from the **Live Debugger** tab in your domain’s Tracking dashboard.

## How It Works

The debugger uses Server-Sent Events (SSE) to stream events from the gateway to your browser in real-time. When you open the debugger tab, it connects to the gateway and starts receiving events immediately. Recent events (last 100) are loaded on connect so you don’t start with an empty view.

Events appear in the stream within milliseconds of being processed - including forwarded, failed, deduplicated, and consent-denied events.

## Event Stream

Each event in the stream shows:

| Field          | Description                                                 |
|----------------|-------------------------------------------------------------|
| **Time**       | When the event was processed                                |
| **Event Name** | The conversion event type (e.g., Purchase, Lead, AddToCart) |
| **Platform**   | Which integration the event was sent to                     |
| **Status**     | Delivery result (see status table below)                    |
| **Duration**   | How long the platform API call took (in milliseconds)       |

### Status Indicators

| Status             | Color  | Meaning                                                         |
|--------------------|--------|-----------------------------------------------------------------|
| **Forwarded**      | Green  | Event was successfully accepted by the platform API             |
| **Failed**         | Red    | Event failed to send (credential error, API rejection, timeout) |
| **Deduplicated**   | Yellow | Event was identified as a duplicate and skipped                 |
| **Consent Denied** | Orange | User consent was required but not granted                       |
| **Dropped**        | Grey   | Event was dropped by a transformation rule                      |

### Expanded Details

Click any event row to expand it and see:

- **User Data Fields** - Shows which identity signals are present (email, phone, firstName, lastName, IP, userAgent, fbp, fbc, ttp, scid, gclAw) as badges. Present fields show as filled badges, missing fields as outlined. **No actual PII values are shown** - only field presence.
- **Custom Data** - The event’s custom data (value, currency, orderId) in JSON format.
- **Error** - If the event failed, the error message from the platform API.
- **Source URL** - The page that triggered the event.
- **Event ID** - Unique identifier for platform-side deduplication.

## Controls

- **Pause / Resume** - Pause the stream to inspect events without new ones pushing them down. Resume to continue receiving.
- **Clear** - Remove all events from the current view (does not affect the gateway or event log).
- **Platform filter** - Show only events for a specific platform (Meta, TikTok, etc.).
- **Status filter** - Show only events with a specific status (Forwarded, Failed, etc.).

## Recommended Workflow

1. **Open the Live Debugger** before testing a new integration
2. **Trigger a test conversion** - visit a page that matches a conversion rule, or send an event via the [Ingest API](/docs/tracking-api)
3. **Verify the event appears** with status “Forwarded” and correct event name
4. **Expand the event** to check that user data fields (email, cookies) are present
5. **If failed** - read the error message. Common issues:
   
   - `credential fetch failed` - check your integration credentials
   - Platform API errors (400, 401) - invalid token or pixel ID
   - `consent not granted` - user hasn’t accepted the required consent category
6. **Check the Event Log** tab for the persisted record with full platform response

## Connection

The debugger automatically reconnects if the connection is interrupted. A green dot indicates an active connection; a pulsing red dot indicates reconnecting.