EyeFly CAPI Event Dashboard

Apr 16–22, 2026  ·  Leads event flow by dataset  ·  Generated Apr 22, 2026

🚨

Zero CAPI events detected across all 31 datasets this week

The Meta Graph API (/{dataset_id}/stats) returned {"data":[]} for all active, paused, and upcoming clients over the last 7 days and 30 days. The Leads event is not flowing through CAPI for any client. This means Meta has no conversion signal — bid optimization and attribution are blind.

Total Events (7d)
0
Leads + all event types
Datasets with Events
0 / 31
Active, paused, upcoming
Active Clients at Risk
23
No attribution signal
Window Checked
30d
Apr 16–22 + 30-day wide net
API Source
/{id}/stats
BM system user token
Filter:
Day-over-Day Event Volume (All Clients)
Client-Level Breakdown
Next Steps to Fix CAPI Coverage
  1. Verify GHL native CAPI action on one client (this week)
    Pick Monroe, LA (has BM token). Go to GHL → Automation → the lead-qualified trigger. Confirm the Meta Conversion API action is present and configured. Fire a test lead and check Events Manager Test Events tab for a Lead event within 5 min.
  2. Confirm action_source = business_messaging
    GHL's native CAPI node may default to web pixel. Business Messaging CAPI requires action_source: business_messaging + either page_scoped_user_id (PSID) or ctwa_clid. If GHL doesn't support this, fall back to N8N HTTP node.
  3. Run capi-health-monitor after first confirmed fire
    Install capi-health-monitor.skill and run it manually. It will write to brain.capi_health_snapshots and fire a Telegram alert. Schedule for Mondays 7:30 AM ET once the plumbing is confirmed.
  4. Fanout to all active clients once GHL pattern is confirmed
    Use capi-test-fire skill to fire a test LeadSubmitted event to each dataset. Then re-run this dashboard to confirm events appear.