tenancy

POST /v1/me/acquisition-touch

Record where the signed-in customer came from (the app's landing capture).

All tenancy endpoints

All developer docs →

Authentication

Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.

Where your organisation id goes

This endpoint takes org_id as a field in the JSON body.

Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.

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/me/acquisition-touch \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "touch": <object> }'

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

The dashboard captures utm_*, ref, zd_vid (the product sites' visit id), the referring host and the landing page BEFORE the sign-in hop, and sends them here on the first signed-in page load. This is the only way an app sign-up can be attributed: self-registration provisions the organization inside authentication, which never sees the landing URL (docs/750). Unknown keys are dropped, values are capped, and the landing page is host and path only. Recorded only against an organization the caller OWNS — a member of someone else's account did not bring it to us — and never under impersonation. The first touch is written once and never overwritten; the last touch is overwritten each time. A capture with nothing attributable (no campaign, affiliate code, visit id or foreign referrer) records nothing and answers recorded: false, reason: empty.

Request body

NameTypeRequiredWhat it is
org_idstringNoThe org to record against; optional when the caller owns exactly one.
touchobjectYesCaptured on landing. Kept keys: utm_source, utm_medium, utm_campaign, utm_term, utm_content, gclid, fbclid, ttclid, msclkid, ref, zd_vid, referrer_host, landing_page. Others are…

Response

NameTypeRequiredWhat it is
recordedbooleanYes—
reasonstring<, empty, impersonation>Yes—
org_idstringNo—

Errors this endpoint can return

401 · 403 · 422