Identify a visitor
Changed onRecords who a visitor is (by email, phone or your own id, all hashed at rest) together with the ad click id that brought them, so that a conversion reported later by email alone can still be credited to the click. Where the click id is gone, the identity itself is used for Enhanced Conversions for Leads.
Also accepted with the campaigns:write scope, and with a website key (grow_pub_…), which is the credential the site tag carries. A personal token still works for server-to-server callers.
Errors
- 400 VALIDATION_ERROR: the body failed validation; details.issues[] names each field.
Request
- Base URL: https://api.growomat.com
- URL: https://api.growomat.com/api/v1/identify
- Auth: one of:
- HTTP bearer
- HTTP bearer
Headers
The Space to work in, for example spc_8f3aK2. Omit it to use your personal Space. List your Spaces returns the ids. A Space that does not exist returns 404 SPACE_NOT_FOUND; one you are not a member of returns 403 NOT_A_MEMBER.
Request body
Response
OK. The result is in data. List responses also carry meta with nextCursor and total.
Changes
- info
added the new optional request property
- info
added the new optional request property
- info
added the new optional request property
- info
added the new optional request property
- info
added the new optional request property
- info
added the new
fbclidenum value to the request property - info
added the new
li_fat_idenum value to the request property - info
added the new
opprefenum value to the request property - info
added the new
rdt_cidenum value to the request property
- info