GET /v1/ads/connections/{connection_id}/tracking

Authentication

Send an API key as a bearer token. The key must carry the ads.view permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X GET https://api.zinndigital.com/v1/ads/connections/{connection_id}/tracking \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Gated on ads.view. Real outcomes from the customer's own source (the events API below, a connected store, plugin or CRM) against what the network credited over the settled days (thresholds.days, the newest thresholds.processing_days excluded). latest.status gap (more than thresholds.gap_pct apart, either direction) or unreadable (the network's count could not be read — never a pass) sets hold: the autopilot judges, cuts and pauses nothing on the network's counts until a check says ok again. latest.diagnoses are the fix assistant's findings as codes + figures (the dashboard words them). latest.recovered / credited_after are the before/after of the missed- conversion recovery. fix_offer is the paid "Fix it for me" add-on priced from the catalogue, or null when it is not offered.

Parameters

Response

Errors this endpoint can return

401 · 403 · 404 · 422 · 429