ads

GET /v1/ads/connections/{connection_id}/geo-holdouts

The account's geo hold-outs — incrementality tests by country (za-202).

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.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}/geo-holdouts \
  -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. Every geo hold-out of the connection (newest first, at most 200) and the customer's thresholds. Before a budget raise at or over the threshold, one country is held out of the campaign for days, resumed by its own Undo, and the account's real first-party sales are compared with their trend: lift (with the measured incrementality), noLift, or inconclusive with its reason (tooFewSales, underpowered, noSignal, endedEarly). Read from our own rows — never a network call (docs/1006 §80).

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—

Response

NameTypeRequiredWhat it is
dataAdsGeoHoldout[]Yes—
settingsAdsGeoHoldoutSettingsYesThe customer's geo hold-out thresholds (za-202); Recommended where never set.

Errors this endpoint can return

401 · 403 · 404 · 429