Diagnostics

When events aren't arriving as expected, walk through these checkpoints in order.

AdsPing side

Pixel detail page shows the time of the most recent event received per pipeline.
Events tab lists every event ingested in the last 7 days with status (success / failed / pending).
A failing pipeline turns yellow ("Degraded") after 3 consecutive errors and red ("Auth failed") when the API returns 401/403.
Click the pipeline edit pencil → it shows the last error message when health is non-green.

Events Manager → your pixel → Diagnostics tab. Shows all warnings/errors flagged on the last 7 days of events. Common issues: low match quality, missing user_data fields, duplicate events without dedup.
Test Events tab for real-time per-event inspection. Set a test code in AdsPing to route there.
Overview tab shows hourly volume. A drop to zero means events stopped flowing.

Web Events page → Diagnostics tab. Lists 7-day warnings: match quality, missing parameters, dedup rate.
Event Activity tab shows each event with source (Web / Server / Both) and Match Score.
Test Events tab is real-time once a test code is set.

Tools → Conversions → click your action → Diagnostics tab. Shows recent uploads, success rate, error breakdown.
Common error UNAUTHENTICATED = developer token missing Basic Access (use gtag fallback while waiting for approval).
Common error INVALID_ARGUMENT: gclid is required = event fired without a captured Google click ID. pb.js captures gclid from URLs automatically — only happens when a visitor lands via a non-Google referrer.

Reports → Realtime → Overview shows live event stream (60-min window).
Reports → Realtime → DebugView requires debug_mode: true in the payload. AdsPing currently doesn't toggle this; use Realtime instead.
Admin → DebugView for older properties.

"No events in Test Events tab" — check that the Test Event Code is set on the AdsPing pipeline AND matches the platform's current code (codes regenerate when you switch tabs sometimes).
"Events arrive but match quality is low" — your forms might not have name="email" or name="phone" attributes. pb.js relies on standard attribute names to harvest Advanced Matching values. Add them to your form fields.
"Pipeline shows Auth failed" — token expired or rotated. Click the pipeline pencil → reconnect the destination from the platform card.
"Events count higher than expected" — you have both pb.js and the platform pixel running, AND the dedup isn't working. Check that event_id appears in both browser fbq calls and AdsPing payloads (they should be identical).

Still stuck? Email [email protected] with your pixel ID, the platform you're debugging, and a description of what you're seeing vs. what you expect.