Developer documentation

Integrate Trakio with confidence.

Production contracts for tracking links, S2S conversion reporting, Flutter and Android SDK ingestion, attribution, and partner postbacks.

Start integrating API health

Quickstart

A predictable attribution handoff

Connect the click, identity, and conversion without changing the identifiers Trakio issues.

Create a tracking link

Choose an approved campaign and preserve the generated Trakio Click ID through the user journey.

Use the correct credentials

Keep production API and SDK credentials isolated. Never expose an S2S key inside a client application.

Send or record events

Report install, registration, KYC, purchase, and custom events with stable identifiers and idempotency.

S2S conversion endpoint

Report an advertiser event

Send a valid Click ID or approved deterministic external identifier. Use a unique event ID for idempotency.

POST https://api.trakiommp.com/v1/conversions
Authorization: Bearer YOUR_PRODUCTION_KEY
Content-Type: application/json

{
  "event": "registration",
  "click_id": "clk_xxxxxxxxx",
  "event_id": "registration_user_123",
  "external_user_id": "user_123"
}

Canonical events

install

First SDK-reported installation for the app installation identity.

registration

Successful account creation after the advertiser completes registration.

kyc_completed

Advertiser-confirmed KYC completion.

purchase

Completed payable purchase with currency and amount where applicable.

Tracking contract

Trakio creates the Click ID. Partners may pass pcid and pid; advertisers must preserve trk_click_id unchanged.