How does Ringba decide which values to use if I configure revenue recovery at the campaign, buyer, target, and RTT levels?
You can configure revenue recovery in several different places: at the campaign, buyer, target, and ring tree target (RTT) levels. When all of these entities have settings configured, Ringba must choose which settings to honor. Ringba uses the following hierarchy to prioritize the settings:
- Campaign settings are the least specific and therefore the default. Ringba follows the campaign settings only if they are not overruled by settings on the buyer or target.
- Buyer settings are more specific than campaign settings. If they exist, Ringba uses these settings for all targets and RTTs associated with the buyer.
- Target and RTT settings are the most specific. Ringba always favors target and RTT settings if they exist.
This means even if you have toggled OFF the Revenue Recovery switch on your campaign, calls will still be rerouted if any buyer, target, or RTT associated with that campaign has the Revenue Recovery switch turned on and will accept the calls.
Does revenue recovery work with ring trees?
Yes, revenue recovery works with ring trees the same way as it works with regular targets. If the ring tree target connects and then the call is rerouted, the entire ring tree will be excluded from the next reroute attempts.
Does revenue recovery work with RTB campaigns?
Yes, revenue recovery works with RTB campaigns.
Does revenue recovery work with passthrough?
Yes, revenue recovery works with RTB Passthrough campaigns.
Previously, RTB campaigns did not have the ability to reroute a call. Once a publisher pinged an RTB campaign, the system would verify all eligible targets and return with a single bid to the publisher. If the call did not connect or was dropped, the call would be lost.
Now, with revenue recovery, the system considers the Pass Through Settings on the campaign to ensure a call is rerouted only if the next eligible target meet the Min Bid Margin After Adjustments and Min Call Duration for Payout criteria.
Note: If the Min Bid Margin After Adjustments field is empty, it defaults to zero.
If a call connects to a target for a few seconds before rerouting, do those seconds count toward the Convert On Call Length?
No. Ringba keeps track of the call length separately for each target. Ringba does not start counting the call length for the second target until the call connects to that target. You can see separate call logs for each in your reporting.
If you have your campaign set to Convert On Call Length, Ringba counts the call length only for the final target when deciding whether the call converted.
If the call does not connect during a rerouting attempt, does the call drop?
Yes. The revenue recovery feature tries all eligible targets, and if none connects to the call, the call drops. This happens even if the reroute attempts value has not been reached because a call must connect to count as a reroute attempt: if no target connects, there is no one to reroute to.
How does the publisher see the calls in the reporting in their publisher account?
Publisher users see the calls broken down with their own data. So, for each call, a new inbound call ID is generated on their end.
Does Ringba generate separate payouts for rerouted calls?
No, even if your campaign is set to allow duplicate payouts, one rerouted call can generate a maximum of one payout. In reporting, the payout appears on the original leg of the call. Bear in mind that your publisher can see all rerouted calls as new calls while logged in as a Publisher User. However, only the first one will be awarded payout.
Does Ringba charge a rerouted call for TCPA Shield?
If a call with TCPA Shield gets rerouted, Ringba does not charge again for the same call. The TCPA Shield charge occurs only for the original call, not for the reroute attempts.
Does Ringba charge a rerouted call for ICP?
If a call has instant caller profile (ICP) and it gets rerouted, we are not charging again for the scrub. The ICP charge occurs only for the original call, not for the reroute attempts.
When is revenue recovery not used?
The reroute only happens when the target explicitly hangs up. If the caller hangs up or if the call disconnects in any other way, such as an unknown or system hang-up, Ringba will not attempt to reroute the call.
How do predictive routing campaigns and targets work with revenue recovery?
In a predictive routing campaign, Ringba completes the calculation once and use the resulting calculation for the rerouted call.
Can I filter calls that were rerouted through revenue recovery?
Yes. This information is available in a column to show on the Reporting and Insights screens, and you can filter on this column. You can filter by calls that got rerouted elsewhere as well as the calls that were generated by the reroute. From there, you can build queries at will to monitor performance for the feature specifically.