This article describes tag routing filters. Tag routing filters evaluate the reporting tag values on a call against criteria you define to determine how to route the call. You can add tag routing filters to a target or ring tree target to control whether Ringba routes calls with certain tag values to the target.
You can also create a tag filter on a pixel that must be satisfied for the pixel to fire and on a Router node in a call flow to define whether a call can follow a route.
This feature is available to Admin users.
This article contains the following sections:
Tag Routing Filters
Tag routing filters are a better way to manage dynamic call flows. With filters, you use tags to define certain conditions that allow or block targets from receiving calls. You can, for example, set a target up to accept only calls from a specific state or only those that come from any state in a list of states you provide. Since you define tag routing filters for each target, you can define different filters for different targets on the same campaign.
When a tag filter is in place, the system sends a call only if the target satisfies ALL conditions in the filter. Each condition can be TRUE or FALSE. If there is only one condition, it must evaluate to TRUE for the target to be eligible for the call. When there are multiple conditions, all the conditions must evaluate to TRUE for the target to be available for the incoming call.
When you configure your conditions, you choose from a list of operators that define how the system compares the tag and the value. This is the list of operators:
- Begins With: The first characters in the tag value must match the characters you enter.
- Contains: The tag value must contain the string of characters you enter.
- Equals Multiple Values: The tag value must match one of the values in the list you provide. Find more information below about uploading a TXT file of values.
- Equals Single Value: The tag value must match the value you enter.
- Exists: The tag must contain a value.
- Greater Than: The tag value must be a numeric value greater than the value you enter.
- Less Than: The tag value must be a numeric value less than the value you enter.
- Does Not Begin With: The first characters in the tag value must not match the characters you enter.
- Does Not Contain: The tag value must not contain the string of characters you enter.
- Does Not Equal Multiple Values: The tag value must not match any of the values in the list you provide. Find more information below about uploading a TXT file of values.
- Does Not Equal Single Value: The tag value must not match the value you enter.
- Does Not Exist: The tag must not contain a value.
When you choose Equals Multiple Values or Does Not Equal Multiple Values, you upload a TXT file with the values you want the filter to use. The values in the TXT file should be separated by commas or by line breaks (one value per line). The file you upload should be no larger than 38MB.
Note: When you upload a TXT file of tag values, Ringba compares its contents against the contents of any previous TXT files you have uploaded. If the content is identical, you see the following message and Ringba uses the existing file.
Tip: See Bulk Tags for information on managing your files of multiple tag values.
Single Filter
For a single filter rule, you can determine whether a value satisfies the filter by putting the phrase “The call will connect if…” in front of it. Consider the following example:
To apply the phrase from above, you say: “The call will connect if State equals California.” So, if a call with from the state of California comes in, this condition evaluates to TRUE and the target is eligible to receive it.
- If a call comes from California, then the condition is TRUE and the call can connect.
- If a call comes from Texas, then the condition is FALSE and the call cannot connect to that target. Instead, the system forwards it to another one following the priority that you have set up.
Multiple Filters
You can add multiple filters to the same target, giving you more flexibility to control the conditions for who is eligible for calls. You can also organize filters into blocks. For multiple filters, the system looks at each block independently and then combines the results. If there are multiple filters inside a block, the system treats each filter independently and then combines the results inside the block.
When you create multiple filters, you configure multiple conditions and then combine them with AND or OR. Conditions configured like this must still evaluate to TRUE for the target to be eligible to receive the call:
- If you use AND, all the conditions must be TRUE for the result to be TRUE.
- If you use OR, at least one condition must be TRUE for the result to be TRUE.
Tip: If you create conditions using an operator that starts with does not (such as does not begin with and does not contain), you should always join those conditions with AND instead of OR to avoid unexpected behaviors.
Example Cases
The following example filter demonstrates a configuration with multiple filters.
In this case, there are two blocks: A and B. A contains one condition and B has two conditions in a block. The blocks have an AND operator between them, so they must both evaluate to true for the call to connect. To use our strategy from earlier in this article, the call will connect if:
A) the state is equal to California AND B) the publisher is equal to Publisher Alpha OR Publisher Beta.
Which means condition A must always be true to connect the call AND either one of the two conditions in B must also be true.
The following examples demonstrate how the system would evaluate the tag routing filters for calls with certain tags.
Example: Call from California AND Publisher Alpha
Block A
The state is equal to California - TRUE
Block B
The Publisher is equal to “Publisher Alpha” - TRUE
OR
The Publisher is equal to “Publisher Beta” - FALSESo, they evaluate to: TRUE AND [TRUE OR FALSE]
According to the tables above: TRUE AND TRUE = TRUE
The call will connect!
Example: Call from Texas AND Publisher Beta
Block A
The state is equal to California - FALSE
Block B
The Publisher is equal to “Publisher Alpha” - FALSE
OR
The Publisher is equal to “Publisher Beta” - TRUESo, they evaluate to: FALSE AND [FALSE OR TRUE]
According to the table: FALSE AND TRUE = FALSE
The call will NOT connect!
Tag Routing Filters FAQ
How does the Zipcode tag filter work?
When you select the tag for your tag filter, you can select Zipcode from the categories on the left side of the window.
When you choose Zipcode, you:
- Select sources where Ringba can expect to find the caller's ZIP Code
- Toggle the switch to indicate whether the caller's ZIP Code must be in your list or must not be in your list
- Upload a list of ZIP Codes you want to use to compare the caller's ZIP Code
If you select more than one potential source for the ZIP Code and toggle the Zipcode not in switch OFF, then a call that arrives with multiple different ZIP Codes from the different sources satisfies the filter if the value from any source is in your list.
On the other hand, if you select more than one potential source and toggle the Zipcode not in switch ON, the target becomes ineligible if any ZIP Code value from any source is present in your list.
How can I use ICP/Profile to collect ZIP Codes?
Instant Caller Profile (ICP) is a feature that incurs an additional fee and must be enabled in your account. Contact your Account Manager to enable ICP for your account.
Once you have ICP enabled, you can use the Profile Node in your call flows to collect the caller's ZIP Code. See Different Ways to Collect ZIP Codes for more details.
Important: If you enable ICP after you have already created your targets, you need to check the targets' routing filters to ensure the ICP/Profile box is selected. This box does not appear until you enable ICP, so it may be deselected in targets you created before you enabled ICP.
How can I use data from tools like IDE or RTB in my tag routing filters?
Ringba features like inbound data enrichment (IDE) and real-time bidding (RTB) attach data to calls as reporting tags. You can use those tags in your tag routing filters by declaring them as URL parameters. See URL Parameters for step-by-step instructions on declaring URL parameters.
What should I do if I need help with tag routing filters?
If you have any questions or need additional help, please reach out to our support team via chat or email at support@ringba.com.