Ping URLs and the spec sheet

After you attach a source to a campaign, CallsFlow Plus gives you the integration details to send the publisher. They live on the campaign page, beside the source.

Call campaigns

For a call campaign each source has an RTB key, a short code you see in the Sources table. The integration panel shows:

• RTB ID: a single identifier. If the publisher is on another CallsFlow-based platform, this is the whole integration. Rotate it to issue a new one. The old one stops working within a minute.
• Ping URL (GET): the publisher's platform calls this for every call, passing the caller's number. State, zip and any extra tags such as SubId are also accepted, and extra parameters show up in your reporting.
• Confirm URL (optional): an optional extra address the publisher's platform can call to confirm a call.
• Call-end webhook (POST) and Call-end body: tells you when the call finishes and how long it lasted. The body must be filled in explicitly on the publisher's side.
• Try it: an example request you can run.
• Sample bid response: what a successful ping returns, including the number to dial and the price.

Replace YOUR_TOKEN with the publisher's token. The token can also go in an X-Service-Token header instead of the URL.

Each field has a Copy button. Rotate a source's RTB key from the same area with Rotate if it is exposed.

Lead campaigns

For a leads campaign, the panel has a Copy spec sheet button that puts the whole document on your clipboard. It lists:

• The Ping (POST JSON) URL, the Post URL (with how many seconds after the bid it is accepted), and the Direct post (no ping) URL if the campaign supports it.
• The questions (attributes) the publisher must send, marked required or optional, with the allowed answers.
• Sample ping, sample post and sample direct requests, and the possible responses.

Click Rotate token to issue a new one and the current one stops working shortly after, so send the publisher the new details straight away. See Ping, post and direct.

If a ping is refused

The publisher sees a plain reason, such as the publisher or source being paused, the campaign not running, the source not being attached, the rate cap being hit, an invalid caller number, the daily cap, or a duplicate caller. See Why a call didn't route.