ads
POST /v1/ads/connections/{connection_id}/conversion-setup/queue
Queue one approve-first change — import the chosen GA4 key events, or create the upload action.
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}/conversion-setup/queue \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ "step": <string<ga4_import, upload_action>> }'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-logged (ads.conversion_setup_queued). Nothing is sent to the network: the change waits in the connection's change queue for a person to approve it. ga4_import sets the chosen key events ENABLED, primary when the method is ga4 and secondary when it is server (so a sale is never counted twice). upload_action creates the UPLOAD_CLICKS action (Google) or offline goal (Microsoft) the server-side upload reports into. Asking again returns the change already waiting.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
connection_id (path) | string | Yes | — |
Request body
| Name | Type | Required | What it is |
|---|---|---|---|
step | string<ga4_import, upload_action> | Yes | — |
kind | string<purchase, lead> | No | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
connection_id | string | Yes | — |
step | string | Yes | — |
change_id | string | Yes | — |
Errors this endpoint can return
401 · 403 · 404 · 422 · 429