Skip to main content
Navigation

Detail Tabs

Click any request in the list to open the detail panel with 5 tabs: Decoded, Query, POST, Headers, and Response. Each tab gives you a different perspective on the same request.

Decoded Tab

The default tab shows human-readable parameters grouped into collapsible sections.

  • Category headers — Parameters are organized by type (e.g., “Event Parameters”, “User Properties”, “Traffic Sources”, “Device Info”). Click a category header to expand or collapse it.
  • Key-value pairs — Each parameter shows its name and decoded value. Long values are truncated with a tooltip showing the full content.
  • Provider-specific grouping — Categories and parameter names are specific to each provider. For example, GA4 shows event_name, page_location, while Adobe Analytics shows pageName, events, eVar1.

The Decoded tab is the most useful for everyday debugging — it shows exactly what data each tracking call sends in a structured format.

Query Tab

Shows the raw URL query string parameters as key-value pairs.

  • Raw format — Parameters exactly as they appear in the URL, without provider-specific decoding
  • Useful for: Debugging URL construction issues, verifying parameter encoding, or when you need to see the exact raw data
  • Pretty-printed — Each parameter on its own line for readability

POST Tab

Displays POST body data for requests that use the POST method.

  • JSON pretty-print — If the body is JSON, it’s formatted with indentation and syntax highlighting
  • Form-encoded — If the body is application/x-www-form-urlencoded, parameters are shown as key-value pairs
  • Binary/empty — Shows a note when the POST body is empty or contains binary data
  • Useful for: Debugging server-side event endpoints (e.g., Facebook Conversions API, GA4 Measurement Protocol), verifying payload structure

Headers Tab

Shows request and response HTTP headers in two separate sections.

  • Request headers — What the browser sent, including User-Agent, cookies, referrer, content-type
  • Response headers — What the server replied with, including status code, cache headers, CORS headers
  • Useful for: Debugging CORS issues, checking cookie consent headers, verifying referrer policy, inspecting server response metadata

What to look for

  • User-Agent — Confirms which browser/device the request appears to come from
  • Cookie header — See which cookies are being sent with tracking requests
  • Referer — Verify the referrer value that accompanies the request
  • CORS headers — Check Access-Control-Allow-Origin for cross-origin tracking pixels

Response Tab

Shows the response body content, loaded on demand.

  • Lazy-loaded — The response body is only fetched when you click this tab, saving memory for large responses
  • Pretty-printed — JSON responses are formatted with indentation
  • Size indicator — Shows the response body size
  • Useful for: Investigating error responses, checking server-side acknowledgment data, debugging API response issues

Wrap Values

Toggle Wrap values in the toolbar to enable or disable line wrapping for long parameter values in the Decoded and Query tabs.

  • On — Long values wrap to multiple lines for readability
  • Off — Values are truncated with horizontal scroll

Use wrapping when you need to read full URLs, JSON strings, or other long parameter values without scrolling.

Auto-Expand

Toggle Auto-expand in the toolbar to automatically expand all collapsible categories in the Decoded tab when you select a request.

  • On — All categories are expanded immediately when a request is selected
  • Off — Only the first category is expanded; others remain collapsed until clicked

Auto-expand is useful when you want to see all parameters at once without manually expanding each section.

Default Tab

You can configure which tab opens by default when you click a request in Settings. Options are:

  • Decoded (default) — Best for most debugging workflows
  • Query — For raw URL debugging
  • POST — For server-side event debugging
  • Headers — For consent and CORS debugging
  • Response — For server response debugging

Tips & Best Practices

  • Start with Decoded — It gives the most structured and readable view of tracking data
  • Use POST tab for server-side debugging — Essential when debugging Facebook CAPI or GA4 Measurement Protocol implementations
  • Check Headers for consent issues — The Cookie and Referer headers reveal important consent-related information
  • Response tab for errors — If a request has a non-200 status, check the Response tab for error details
  • Auto-expand for audits — Enable auto-expand when auditing all parameters of a request

Was this page helpful?

Start typing to search docs...