ads

PUT /v1/ads/connections/{connection_id}/geo-holdouts/settings

Store the customer's geo hold-out thresholds (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.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 PUT https://api.zinndigital.com/v1/ads/connections/{connection_id}/geo-holdouts/settings \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

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.geo_holdout_settings. mode suggest (propose for approval, the default) · auto (start without asking, never for a country in the customer's markets) · off. reset: true puts every value back to Recommended. A value outside its bounds is 422 geoHoldoutInvalid. A test already proposed keeps the values it was proposed with.

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—

Request body

NameTypeRequiredWhat it is
modestring<auto, suggest, off>No—
raise_pctintegerNo—
daysintegerNo—
min_salesintegerNo—
resetbooleanNo—

Response

NameTypeRequiredWhat it is
dataAdsGeoHoldoutSettingsYesThe customer's geo hold-out thresholds (za-202); Recommended where never set.

Errors this endpoint can return

401 · 403 · 404 · 422 · 429