Docs
Toplu is a single API for server-to-server conversion events. Your backend sends one event when a conversion happens, Toplu delivers it to every destination you use.
Receiving conversions instead of sending them? These guides are written for advertisers. See For networks for the product, or Receiving conversions for the technical guide.
How it works
Send
Your server sends one event to Toplu the moment a conversion happens.
Normalize
Toplu validates the event and maps it to whatever each destination actually expects.
Deliver
Delivered to every destination you use: hand-built connectors for the big platforms, automatic for every network that speaks ECAPI.
Guides
Quickstart
The three steps, start to finish
Sending your first event
What a request actually contains
Working with destinations
ECAPI-native vs. hand-built connectors
Schema mapping
What a connector actually does
Handling retries
Automatic, per destination
Testing your integration
Test keys vs. live keys
Going to production
The checklist before you switch
Migrating from a custom pipeline
Replacing hand-rolled per-destination code
Questions, or want to shape what these should cover? Get in touch.
Need a hand?
Coding is hard sometimes, and that's okay. Visit our help center or reach out directly, we're here to help.
