Template Integrations

After reading all technical documentation from this knowledge base, you still might have some questions. They might regard the very concrete use scenarios, platforms that you work with and so on. For example, you might already know how to add a custom traffic source to Voluum, but how does the setup look like on Facebook's or Google's side? You already know how to add an offer element to Voluum, but what about using offers from specific affiliate networks, such as Mobidea, Leadbit or MaxBounty? What options do you have and how to set up everything in those platforms?

If you do not know answers to those questions, then this section is for you.

You will find here documents that describe different template integrations with other platforms.

Integrations:

Traffic Sources:

Social platforms

Affiliate Networks:

Trackers:

Tag Management Systems:

Other

In this section:

A token is used to pass a dynamic information in a redirection link or a postback URL. Tokens are described by parameters. Each entity, such as traffic source or affiliate network, use specific tokens. Available Voluum tokens are always displayed when you are building a redirection link.

The request parameters of HyperText Transfer Protocol are additional pieces of information transmitted from one device to the other that you might see in the address bar of your browser. They are in the form of parameter_name={token} pairs, where {token} is replaced with a concrete value once the URL is activated, and are separated from the URL by a ?. There might be more than one parameter_name=value pair, where each of them are separated by an &.

Parameter name, Token