Receiving conversions
For networks and platforms on the receiving end, not sending events out. If you're an advertiser or agency sending conversions, the rest of the guides are written for you instead.
Getting an endpoint
There's no self-serve signup yet. Today, getting in touch is how it starts, we provision your endpoint and API key on our side and send them to you. This describes the intended shape of what you get, not a dashboard you can go create today.
Your landing zone
Every event an advertiser sends to your endpoint is validated against the ECAPI schema before it's stored, so what you see is always well-formed. That storage is your landing zone: a raw event log, basic aggregation, and export to CSV or by API, a place for the data to land even if you don't have a system of your own for it yet.
Real-time delivery: webhooks
ECAPI itself is one-directional, an advertiser posts an event, the destination returns a status code, nothing more. It doesn't define a way to notify a downstream system, so we built one: configure a URL, and Toplu sends an HTTP POST there the moment a validated event lands. Each request carries an X-Toplu-Signature header, an HMAC of the payload, so you can verify it actually came from Toplu before acting on it. Delivery follows the same retry and backoff behavior described in Handling retries, an outage on your end doesn't mean a lost event.
No engineering team? Pull instead
A webhook receiver is optional, not a requirement. If you've got nowhere to run one, the landing zone from above still works on its own: view events as they arrive, or export them, without standing up anything.
What this isn't
Not an identity-matching or attribution product. Toplu validates and hands you clean data, it doesn't claim to match it to your own users better than a dedicated identity platform would. See For networks for the full picture.
Need a hand?
Coding is hard sometimes, and that's okay. Visit our help center or reach out directly, we're here to help.