ads

GET /v1/ads/site-tags/{tag_id}/gtm-container

The Google Tag Manager container to import, built from the same site tag.

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/site-tags/{tag_id}/gtm-container \
  -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 (docs/1006 §84). A GTM export (format 2) the customer imports in Admin → Import container (choose Merge): consent defaults on Consent Initialization, the Conversion Linker and Google tag, one Google Ads conversion tag per label (fired by the data-layer event zinn_<kind>), Microsoft UET and the Meta pixel (the Meta tags require ad_storage consent). The site pushes {event: "zinn_purchase", zinn: {value_minor, currency, transaction_id}}.

Parameters

NameTypeRequiredWhat it is
tag_id (path)stringYes—

Errors this endpoint can return

401 · 403 · 404