Ringba identifies a call as a duplicate if it comes from a caller ID that previously called into the campaign in the last 365 days. If a call meets this criterion, Ringba applies an isDuplicate=yes tag, which appears in Reporting and which you can use like any tag in your tag routing filters or when firing pixels.
However, the way you configure some settings can affect how Ringba defines a duplicate call and how it treats those calls. Certain settings can cause Ringba to act on calls as duplicates even if they don't have an isDuplicate=yes tag.
The following sections explain how settings on the campaign, target, or buyer can affect how Ringba defines a duplicate call.
Defining Duplicate Calls by Campaign
In a campaign, you can configure the Report Duplicate Calls On field.
You can choose any of these values:
- Connect: Ringba adds the isDuplicate=yes tag if a previous call from the caller ID connected to a target in the last 365 days.
- Incoming: Ringba adds the isDuplicate=yes tag if a previous call from the caller ID entered Ringba, even if it never connected to a target, in the last 365 days.
- Call Length Greater Than: Ringba adds the isDuplicate=yes tag if a previous call from the caller ID connected to a target in the last 365 days and remained connected longer than the number of seconds you enter in the field.
Blocking Spam Calls
Also in a campaign, you can use the Filter Repeat Callers field in the Spam Filter section to block repeat calls from a caller ID for a number of seconds.
Ringba considers all incoming calls, regardless of whether they connected or converted, when applying this setting, and enforces it for the number of seconds you configure. Calls blocked by this setting do not get the isDuplicate=yes tag.
See Outsmarting Spam Calls for more information about blocking spam calls in Ringba.
Restricting Duplicate Calls for a Target or Buyer
When you restrict duplicate calls for a target/buyer, you have the option to choose a Duration. You can set the Duration for any length of time, including Always. If you set the Duration to any value longer than 365, you expand the definition of "duplicate call."
If you set a longer Duration for a target/buyer, and a duplicate call comes in after day 365, Ringba does not add the isDuplicate=yes tag to the call, but it does prevent the call from going to the target/buyer.
Note: Ringba blocks duplicate calls according to your configurations. However, if the caller ID tries to call more than 20 times, on the 21st try, Ringba allows the call to go though. For example, say you set the target to restrict duplicate calls for 15 days and a caller ID called the first time on June 10. Per your settings, the caller ID should be blocked until June 25, but if they called 20 times already and call for the 21st time on June 20, the call goes though.
Restricting Duplicate Calls for Publishers
When you're configuring a campaign, you can override the campaign settings for a publisher and use the Duplicate Payouts controls to restrict publisher payments for duplicate calls.
As with the target/buyer setting, you can choose a duration for the restriction longer than 365 days.
If you set a longer restriction time for a publisher, and a duplicate call comes in after day 365, Ringba does not add the isDuplicate=yes tag to the call, but the payout can be denied for the reason that it was a duplicate.
Note: In the campaign's General Info section, you can toggle on the Payout Once Per Caller switch. If you toggle on this switch, Ringba pays out only once per caller ID, even if different publishers generated the duplicate calls.
Identifying Duplicate Calls FAQ
What should I do if I need help?
If you have any questions or need additional help, please reach out to our support team via chat or email at support@ringba.com.