Adding Contester tag directly

Usually websites rely on multiple tag containers that execute in a chain, one including the other. Example of that is using a Google Tag Manager to include an affiliate network tag container, that in turn includes affiliate network specific partner scripts onto advertiser website.

It is also a common practice to down-prioritize the load of affiliate network scripts to minimize impact on website loading time. And historically there was no need for a quick execution of affiliate scripts.

That creates a certain challenge in using Contester solution on advertiser websites.

On a cold page load (first time user opens a particular website, they don't have any of website scripts cached on their browser) it can take anytime from 2 seconds to 20 seconds before our scripts start executing.

This can impact effectiveness of our solution because users who fail to see our widget upon page load may navigate away and never see the content or a live stream.

A solution to this is embedding our scripts directly in advertiser website, or as early in the script loading timeline as possible. This minimizes amount of time it takes for our widget to display to users.

We have a different script for each different affiliate network (or even a script flavor without any affiliate network associated to it). So the first step is discussing the matter with us and determining which exact script needs to be added.

Once that's clear, we'll give an HTML embed script that can be added to a website, GTM or any other script container to assure faster scripts loading. Script will contain your individual advertiser ID that integrates through a specific affiliate network.

After embedding our script directly it is possible, that our script will load twice. Once directly and once through affiliate network tag manager. This is completely safe, as we are handling this case and assuring that our script actually executes only once, no matter how many times it is being embedded.