Voluum Documentation

Adding a Rule-Based Paths for Custom Variables

Voluum TRK Rule-Based Path Custom Variable

In the Adding a Rule-Based Path article you have learned how to create a path that contains one or more condition regarding traffic characteristics, such as country of origin or day of the week. These characteristics are fetched by Voluum and attributed to a visit. But apart from these characteristics, you have also information passed from your traffic source platform at your disposal. When correctly matched with Voluum custom variables in the traffic source element settings, they can also be the basis of traffic redirection rules created in a rule-based path. The following article will cover the topic of creating a rule-based path with values matched with custom variables.

Matching Traffic Source Parameters with Voluum Custom Variables

Your traffic source platform can pass various information in parameters. When configuring a traffic source element in Voluum, you need to match the traffic source token (placeholder) with one of the custom variables, from {var1} to {var10}. Once you do so, this {var} custom variable will store values passed in the token.

You can get a list of parameters from your traffic source documentation or use one of the Voluum traffic source templates to have all the parameters already matched.

Example:

Consider the following scenario: your traffic source supports passing information about which creative was used to generate a visit under the {creative_name} placeholder. During the setup process, you have matched it with {var1} custom variable. In this traffic source element form, under the Advanced parameters section, you should see the following configuration:

custom_variable1.png

Values passed in this token can serve as a condition in the Rule-based path configuration.

Adding a Rule-Based Path for Custom Variable

Let's assume that the {creative_name} token can pass one of two values: "banner1" and "banner2". You want to direct visitors to two different landers appropriate for the creative they clicked. In this setup, visitors that have clicked banner 1 (which passes the "banner1" value) will be directed to Lander1 and Offer1 and visitors that have clicked banner 2 (which passes the "banner2" value) will be directed to the Lander2 and Offer2. All remaining traffic will go to the Default Lander and the Default Offer. For this to work, we need to create two separate rule-based paths with a correct custom variable each, and set up a default path for a remaining traffic.

In order to do so, perform the following steps:

  1. In Voluum, go to the campaign / flow form. In Campaigns, in the Advanced view, go to the Destinations tab.

  2. Select the Path radio button in the Campaign destination section.

  3. Create a rule-based path for "banner1". This path diverts traffic that contains the "banner1" value, matched with the custom variable 1, to Lander1 and Offer1.

    1. In the Rule-based path section, click the Add rule button.

      rule1.png
    2. Provide a name for the rule in the Rule name text field.

    3. Click the Variables condition type.

    4. In the Variables:

      1. Click the Add condition button.

        add_custom_variable1.gif
      2. Because in our example you have matched the traffic source parameter with the {var1} custom variable, select the Add custom variable 1 option.

        add_custom_variable2.gif
      3. With the logical condition selected between Is or Is not, provide the value (not the token or parameter name) of your condition. So if you want to divert traffic to this path that comes with a "banner1" value passed in the {creative_name} token, select the Is logical condition and provide "banner1" value in the text field. You can provide more values, if needed, by ticking the List checkbox and providing those values in separate lines.

        add_custom_variable3.gif

        Caution

        Voluum Note: Keep in mind that only exact matches to the value you provided will cause traffic to be diverted to this path. Close matches, such as "cool_banner1" will not go to this path.

    5. Click the New path button under this rule.

    6. Provide a name for your path in the Path name text field.

    7. Select Lander1 from the list of your landers.

    8. Select Offer1 from the list of your offers.

      rule3.png
  4. Create a rule-based path for "banner2". This path diverts traffic that contains the "banner2" value matched with the custom variable 1 to Lander2 and Offer2.

    1. Click the Add rule button again.

      rule4.png
    2. Provide a name for the rule in the Rule name text field.

    3. Click the Variables condition type.

    4. In the Variables condition type, create a condition for custom variable 1 in the same manner as you have done so before, but this time, provide the "banner2" value as your custom variable.

      rule7.png
    5. Click the New path button under this rule.

    6. Provide a name for your path in the Path name text field.

    7. Select Lander2 from the list of your landers.

    8. Select Offer2 from the list of your offers.

      rule5.png
  5. Define a default path.

    1. Click the New path under the Default path section.

    2. Provide a name for your path in the Path name text field.

    3. Select a default lander from the list of your landers.

    4. Select a default offer from the list of your offers.

      rule6.png
  6. Click the Save button.

Here is what will happen: when traffic goes to Voluum, it will be checked against conditions set in those two rules. If traffic passes the "banner1" value in the token matched with custom variable 1, it will be directed to Lander1 and Offer1. If it passes the "banner2" value, it will go to Lander 2 and Offer 2. Traffic that does not meet any of these criteria (that does not pass any of those two values) will go to the Default Lander and the Default Offer.

Search results

    No results found