Documentation

Build, route and explain every call

How to set up call tracking on buy3: buy numbers, add the buyers you sell to, build a routing plan and read exactly why each call went where it did. Written for publishers, networks, brokers and the buyers on the other end of the line.

Start here

QuickstartFrom a new workspace to your first routed call.Routing plansPriority, weight or highest bid, with failover.The call waterfallWhy a call went where it went, step by step.API referenceAuthentication, conventions and every endpoint.

How the platform fits together

A call lands on a tracking number, the number's campaign decides where it goes, and a buyer's target answers it. Real-time bidding can sit on either side of that. Whatever happens, the call writes its own record as it goes — and everything else in the product reads that record.

Callerspublishers and your own adsTracking numbersstatic, or pooled for DNICampaigngates, then the routing planBuyers' targetsphone, SIP or a bid endpointRTB in: publishers pingfor a bid before they sendRTB out: buyers' endpointsare pinged before the dialEvery call writes its own recordas the call happens, never reconstructed afterwardsCall log and waterfallevery gate, target and dialReportsrevenue, payout and marginWebhooks and pixelssigned, retried, replayableREST API and exportseverything the console sees
Left to right is the path of one call. The band underneath is what that call leaves behind.

Browse the guides

Getting started

Campaigns

Buyers and targets

Publishers

Numbers

RTB

Calls

Reporting

Integrations

Account

Reference

Building an integration?

The REST API reaches everything the console does, with scoped keys, a request log and signed webhooks. The reference has an example for every endpoint in curl, Node.js and Python.

Open the API reference