Skip to main content
POST
Event Tracking
Send user behavior events to build event-based audiences for targeting. The event data is used for audience segmentation and conversion tracking.

Request Parameters

Headers

string
required
App Key (found in adrop_service.json)
string
required
application/json

Body Parameters

string
required
User unique identifier
string
required
Event name (1–64 characters)
string
Platform. e.g., web, android, ios
Additional event-specific parameters are passed as top-level fields in the request body. For multi-item events (begin_checkout, purchase), pass an items array.

Response

string
"ok" on success, "!invalid" on validation error.

Supported Events

Common Events

Online Sales Events

Lead Generation Events


Examples

Simple Event

Event with Parameters

Multi-Item Event (Purchase)

Lead Generation Event


Notes

  • Events with unknown names or missing required parameters are silently ignored (HTTP 200 returned).
  • Multi-item events support up to 100 items per request.
  • String parameter values are limited to 1024 characters.
  • uid is hashed with SHA-256 before storage.

Event Targeting

Configure event-based audience targeting in the console

Conversion Tracking

Track conversions based on purchase events