ads

POST /v1/ads/connections/{connection_id}/tracking/retry

Send the uploads Google never gave a verdict on again (a person's retry).

All ads endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

Send an API key as a bearer token. The key must carry the ads.manage 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 POST https://api.zinndigital.com/v1/ads/connections/{connection_id}/tracking/retry \
  -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.manage; audit action ads.tracking_retry. Google accepted these uploads and no verdict was read within 3 days, so nothing more is sent automatically (AdsTracking.given_up). Each goes back to pending ONCE and the tracking check starts, which sends them the normal way (good standing is checked at the send; a refusal waits the normal back-off). Idempotent: a second call finds none given up and re-queues nothing (requeued: 0, started: false). A refunded upload, or one past the network's upload window, is never sent again; a refund of a re-queued one is still a retraction (Google may have recorded the original).

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—

Response

NameTypeRequiredWhat it is
connection_idstringYes—
requeuedintegerYesUploads put back to pending by this call.
startedbooleanYesThe tracking check workflow started.
given_upintegerYesUploads still given up after this call.

Errors this endpoint can return

401 · 403 · 404 · 422 · 429