How does Ringba prioritize multiple tags? – Ringba

The Ringba application offers several locations where you write syntax that can include tag tokens. The tag tokens are placeholders for tag values you want the application to include in the request. These locations include:

You might receive the same tag values from different publishers in differently named tags. For example, one publisher may send the ZIP code in a parameter called ZIPCODE while another uses a parameter called zip_code. You can include the tag value, regardless of the tag name, by adding all the possible tag tokens in the order you want the application to consider them.

The order of the tags indicates their priority. By default, the system sends the first tag’s value. Only if the tag is empty does the system consider the next tag value. You use a pipe (|) to delimit the tags and square brackets ([]) to contain the values. The syntax looks like this:

[category:tag|category:tag]

Consider this example:

[user:zipcode|gather:zipcode]

The example contains the following parts:

Left and right square brackets show where the value begins and ends
user and gather are the categories that indicate where the tag value is coming from
The colons separate the category from the tag names
In both cases, the tag is named zipcode

Ringba interprets this example to use the gather:zipcode value only if user:zipcode value is not available.

You can select as many potential tag values as you want and Ringba uses them in the order in which you present them. If multiple tags have a value, only the earliest one will be sent, not all.

Related articles