Event types

Endpoint and authentication

POST https://api.adgentek.ai/functions/v1/capi-conversions
Content-Type: application/json
x-api-key: YOUR_ADVERTISER_API_KEY

The key must be active, belong to the request’s organization, and include the capi permission.

Request

{
  "org_id": "YOUR_ORGANIZATION_UUID",
  "events": [
    {
      "event_name": "purchase",
      "event_id": "order_1234",
      "event_time": "2026-10-15T13:00:00Z",
      "click_id": "CLICK_ID_FROM_ADGENTEK",
      "value": 189.0,
      "currency": "USD",
      "attribution_window": "7d_click_1d_view",
      "session_id": "checkout_session_123",
      "custom_data": {
        "product_category": "electronics"
      }
    }
  ]
}

Field	Required	Description
`event_name`	Yes	Your event name, such as `purchase`, `lead`, or `sign_up`
`event_id`	No	Your stable identifier for diagnostics and reconciliation
`event_time`	No	ISO timestamp; defaults to receipt time
`click_id`	No	Value received as `adgtclid` on the landing URL; required for click attribution
`value`	No	Conversion value; defaults to `0`
`currency`	No	Currency code; defaults to `USD`
`attribution_window`	No	Use `7d_click_1d_view` for a seven-day click lookback
`session_id`	No	Your checkout or conversion session identifier
`user_key`	No	Your privacy-safe user key
`custom_data`	No	Additional non-sensitive event data

The endpoint accepts batches. Each event is processed independently, and the response reports processed events and indexed errors.

Event names

Event names are not restricted to a fixed enum. Use a small, stable taxonomy and keep the same meaning across campaigns. Common names are:

purchase
lead
sign_up
booking
app_install

Attribution

Adgentek appends adgtclid to the advertiser landing URL. Preserve that value through the conversion flow and send it in the API’s click_id field. Conversions with a matching click_id use last-click attribution. Send attribution_window: "7d_click_1d_view" for a seven-day click lookback. The current handler applies a one-day click cutoff when the field is omitted. Events without a matching click can be ingested but are not attributed to that click.

The current endpoint does not guarantee idempotent retries from event_id. Do not automatically retry an ambiguous response unless your integration first confirms that the event was not recorded.

Errors

Status	Meaning
`400`	Missing `org_id` or `events` array
`401`	Missing, invalid, or inactive API key
`403`	Key lacks `capi` permission or belongs to another organization
`500`	Ingestion failure

Get Started

Spark for Brands

Conversion Tracking

Measurement

Management API

Endpoint and authentication

Request

Event names

Attribution

Errors

​Endpoint and authentication

​Request

​Event names

​Attribution

​Errors

Endpoint and authentication

Request

Event names

Attribution

Errors