ads
GET /v1/ads/connections/{connection_id}/product-analytics
The customer's product analytics source and the lead quality it measures (za-190).
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}/product-analytics \
-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 (za-190, docs/1006 §71). The connected product analytics project (PostHog, us or eu cloud) whose events tell the ads truth which clicks became sign-ups, activations, day-7 and day-30 retained people and upgrades. source is null until one is connected; the key is never returned (has_key). quality is per keyword and country, read from stored rows — never a network call in the request.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
connection_id (path) | string | Yes | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
source | AdsProductSource | null | Yes | — |
regions | string[] | Yes | — |
stages | string<signup, activated, retained7, retained30, upgraded>[] | Yes | — |
quality | object | Yes | — |
Errors this endpoint can return
401 · 403 · 404 · 429