debug_data_flow

Composes data from the conversions table + recent webhook logs + integration freshness so the agent can answer “why didn’t I see purchase events this weekend?”.

When to use

“No purchase events from Shopify in the last 7 days — what’s wrong?”
“Why is my Facebook spend missing for last Tuesday?”

For overall tracking health, use get_space_health. For a specific page’s pixel check, use inspect_site + verify_pixel_events.

Parameters

Parameter	Type	Required	Description
`event_name`	string	Yes	The event to trace.
`start_date`	string	Yes	`YYYY-MM-DD HH:MM:SS` in the space timezone.
`end_date`	string	Yes	`YYYY-MM-DD HH:MM:SS` in the space timezone.
`source`	string	No	Narrow to one integration / source slug.
`format`	string	No	`json` (default), `csv`, or `yaml`.

Output

{
  "event_name": "purchase",
  "range": {
    "start_utc": "2026-05-08T04:00:00Z",
    "end_utc":   "2026-05-15T03:59:59Z"
  },
  "conversion_count": 0,
  "recent_webhooks": [
    { "id": 78421, "source": "shopify", "status": "success", "created_at": "2026-05-09T10:12:00Z" }
  ]
}

recent_webhooks carries the last 10 webhook receipts on the source over the requested window — use them as triage signals. For full per-fire detail (including PII-redacted payloads), follow up with get_webhook_event. # hint: footer surfaces the most likely root cause first (“Webhooks fired but no conversions recorded — possible event mapping issue.”).

Get Started

Connecting Clients

Tools

Resources

Prompts

When to use

Parameters

Output

​When to use

​Parameters

​Output

When to use

Parameters

Output