Voluum Documentation

Adding Click URLs on a Landing Page Used in Different Funnels

Voluum TRK TRK Campaign Funnel Click URL

This article explains how to add click URLs to the landing page that might be used in different campaign funnels. When this happens, the domain name changes, thus this piece of information should be passed to the landing page dynamically.

Landing pages with a Voluum click URL do not require any additional scripting for tracking clicks or offer redirections.


Voluum Note: Double-check if you have used the {trackingdomain} token in the lander's setup in Voluum. This and the code that you are about to add ensure that the domain used in the click URL / multi-offer click URL matches exactly to the domain used for the campaign URL. It allows you to dynamically pass this information. For more information, go to the Creating a Lander Element with Tokens article.Creating a Lander Element with Tokens

II. Paste a Script to Your Landing Page

In this step you need to do modify the landing page, so that all the data is automatically taken and used to build the click URLs on the landing page.

Within the <head> section of your landing page, add the following script:

function getURLParameter(name) {
var query = window.location.search.substring(1);  
var vars = query.split("&");  
for (var i=0;i<vars.length;i++) {  
var pair = vars[i].split("=");  
if(pair[0] === name){return pair[1];}  
return "";


getURLParameter(): This is a function that looks for a given parameter name in the landing page URL and returns its value.

Parameters in the URL are added as follows:


thus the getURLParameter(parameter2) returns the value2 and getURLParameter(parameter3) returns the value3

It means that when you have added the parameter with the {trackingdomain} token to the landing page URL: 


the script will dynamically return exactly the same domain as for the campaign URL.

Having defined the function, you can now use it in your CTA links / buttons.

III. Add the Click URL(s) to Your Landing Page

There are two types of the CTA links / buttons that determine how many call-to-action links you might add to the landing page:

  • Single Click-to-Action (CTA) → click URL: The default click URL is only used for landing pages containing a single CTA link / button, http://your_Voluum_domain.com/click . This click URL should be placed into the <body> section of a landing page’s HTML.

    As explained before you need to paste it in a way that the domain name is automatically retrieved from the landing page's URL and added to the click URL. Take a look at the code sample below:

    <script>document.write('<a href="http://'+ getURLParameter('domain') + '/click">Click here to win!</a>')</script> 
  • Multiple Click-to-Action (CTA) → multi-offer click URL: You should use the multi-offer click URL only if you have a few static offers that you want to promote on your landing page and each offer has its own CTA link / button that redirects to it upon a click. If you have multiple offers that you want to rotate after upon the CTA link / button, use the click URL and then add multiple offers while creating a campaign in Voluum.

    For example, if your landing page contains three different (CTA) links to separate offers, you need three separate multi-offer click URLs for each CTA:





    The multi-offer click URLs should then be placed into the <body> section of a landing page’s HTML.

    The multiple CTA links / buttons should be added in a way that the domain name will be passed from the domain parameter in the landing page's URL to the click URL:

    <script>document.write('<a href="http://'+ getURLParameter('domain') + '/click/1">Click here to win!</a>')</script>
    <script>document.write('<a href="http://'+ getURLParameter('domain') + '/click/2">Click here to win!</a>')</script>
    <script>document.write('<a href="http://'+ getURLParameter('domain') + '/click/3">Click here to win!</a>')</script> 

Once you have added the URLs to the landing page, you are ready to set up the landing page in the campaign funnels.

Search results

    No results found