conversions

Report conversion events

Changed on

The general way to tell Growomat that something happened: a sign-up, a trial, a qualified lead, a payment or an upgrade. Send events from your own stack (one, an array, or { events }), or pass a provider payload with source set to stripe, hubspot, salesforce, ga4 or webhook and let the server normalise it.

A funnel event name creates its conversion action on first use; adjustment rows are routed to the adjustments path. Also accepted with the campaigns:write scope.

With a website key (grow_pub_…) the operation runs in a constrained form: the source is set by the server, adjustments are refused (ADJUSTMENTS_NOT_ALLOWED), a declared source is refused (SOURCE_NOT_ALLOWED), conversion actions are never created, and at most 10 events are accepted per request. Sales reported this way are stored as unverified claims and are neither uploaded to an ad platform nor counted in any report until a server-side source confirms the same orderId.

Errors

  • 400 VALIDATION_ERROR: the body failed validation; details.issues[] names each field.
post/api/v1/conversions/events

Request

  • Base URL: https://api.growomat.com
  • URL: https://api.growomat.com/api/v1/conversions/events
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer

Headers

X-Space-Idstring

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

OR
OR

Response

OK. The result is in data. List responses also carry meta with nextCursor and total.

dataunknown required

Changes

  • f02611b531aaRevision changes
    • breaking

      removed subschema #2 subschema #3 from the request body oneOf list

    • 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 subschema #2 subschema #3 to the request body oneOf list