If you are looking for a good technical solution to set up your traffic from Facebook, Google, or other popular sources, then this article can be of great use to you. I will be showing you a real working case on the tracker, which is successfully used by affiliates from eastern Europe, to launch verticals, such as: Gambling, Dating, Sweepstakes, and any others with which you need a special setting for moderators.
This tracker has a set of scripts that can be connected to your remote sites and has various settings, including dynamic content substitution, depending on the characteristics of the incoming traffic.
In addition, it makes it possible to write your own script, macro, or filter, and integrate it into the tracker if you are technically savvy and want to implement an author's solution on a ready engine.
I will be using the Keitaro tracker, which can be bought for very little money and installed on your VPS, running CentOS 7 or 8.
Self-hosted installation may seem like an awkward solution to you as we near the end of 2020, but it is the best solution for the safety of your links and landing pages that you will load in the tracker. The reason being all data will be stored exclusively on your server and not somewhere in the cloud, and you will not have root access. You can download pre-landing pages and landing pages locally, and then use them to dynamically rewrite your remote sites, where all traffic will land.
So, how does it work?
After installing the tracker on the server, go to the admin panel, which looks a little old-fashioned and not as bright as modern tracking solutions but has great functionality. Use at least a pro license (for 40 dollars) to have the opportunity to use integration scripts.
Next, we need to buy a domain and send it to the tracker so that our future integrations work through SSL.
To add a domain in the tracker, add an A record from the IP server where the installation was performed. And then on the Domains page, add it.
For experts:
If you know how CloudFlare works, then it is better to direct the domain first to this service, and from there add an A record. This way, you can mask the true IP of your server with the tracker on it, and, in case of problems, just change the domain, without having to reinstall the tracker to a new server.
Next, we create a campaign and generate a new integration script in it through the previously added domain.
Choose the KClient JS integration in base64 format.
You need to put this code on your remote site in the tag <head>.
After you install the code, every click on the site will be processed by a script and all data will be transferred to the tracker, and to the campaign where the integration script was taken.
A distinctive feature of this script is that it is unique every time and the moderation bots still haven't tagged it.
As I already said above, the code sends a request with the click data to the tracker and waits for a response, then it can perform any action set in the campaign.
The key action of the script is the ability to rewrite the content of your remote page (switch on page from the tracker), without redirecting and changing the domain.
Therefore, all that remains for you to do is to launch an advertising campaign to your remote site, then wait for the targeted traffic and set up the conditions in a stream, under which it will recognize targeted traffic and send it to the cash flow. The content of this stream will be sent to your original site without changing the domain or redirecting.
It looks like this:
You need to put this code on your remote site in the tag <head>.
After you install the code, every click on the site will be processed by a script and all data will be transferred to the tracker, and to the campaign where the integration script was taken.
A distinctive feature of this script is that it is unique every time and the moderation bots still haven't tagged it.
As I already said above, the code sends a request with the click data to the tracker and waits for a response, then it can perform any action set in the campaign.
The key action of the script is the ability to rewrite the content of your remote page (switch on page from the tracker), without redirecting and changing the domain.
Therefore, all that remains for you to do is to launch an advertising campaign to your remote site, then wait for the targeted traffic and set up the conditions in a stream, under which it will recognize targeted traffic and send it to the cash flow. The content of this stream will be sent to your original site without changing the domain or redirecting.
It looks like this:
In the first stream, we set an action - Do nothing.
As soon as we are ready to receive targeted traffic, we turn off this stream and all clicks from the remote site will be checked according to the conditions of the second stream. (Of course, non-targeted clicks and bots will not have a creative_id or ad_campaign_id value).
Therefore, they will remain in the second stream, and all targeted traffic will go to the third, where your local landing page will be, which will be sent to your remote site.
The built-in bots base is rather weak and not very suitable for working with sources such as Tik-Tok, Google Ads, Facebook, and others. Therefore, you can filter by click parameters, as in the screenshot above.
Or use the available integrations: Imklo, Hide click (services similar to Cloak it, Magic Checker or Fraud Filter).
Or even write your own filter and integrate it into the tracker.
Additionally, you can add a built-in Bot filter with your own IP lists or UserAgents/signatures.
This scheme is simple to implement and the quality of traffic processing only depends on you.
I hope this article helps you generate a lot of traffic to popular verticals in the affiliate marketing market.
For more information, or to ask a question, send a message to our support team, who is available during working hours.
This tracker has a set of scripts that can be connected to your remote sites and has various settings, including dynamic content substitution, depending on the characteristics of the incoming traffic.
In addition, it makes it possible to write your own script, macro, or filter, and integrate it into the tracker if you are technically savvy and want to implement an author's solution on a ready engine.
I will be using the Keitaro tracker, which can be bought for very little money and installed on your VPS, running CentOS 7 or 8.
Self-hosted installation may seem like an awkward solution to you as we near the end of 2020, but it is the best solution for the safety of your links and landing pages that you will load in the tracker. The reason being all data will be stored exclusively on your server and not somewhere in the cloud, and you will not have root access. You can download pre-landing pages and landing pages locally, and then use them to dynamically rewrite your remote sites, where all traffic will land.
So, how does it work?
After installing the tracker on the server, go to the admin panel, which looks a little old-fashioned and not as bright as modern tracking solutions but has great functionality. Use at least a pro license (for 40 dollars) to have the opportunity to use integration scripts.
Next, we need to buy a domain and send it to the tracker so that our future integrations work through SSL.
To add a domain in the tracker, add an A record from the IP server where the installation was performed. And then on the Domains page, add it.
For experts:
If you know how CloudFlare works, then it is better to direct the domain first to this service, and from there add an A record. This way, you can mask the true IP of your server with the tracker on it, and, in case of problems, just change the domain, without having to reinstall the tracker to a new server.
Next, we create a campaign and generate a new integration script in it through the previously added domain.
Choose the KClient JS integration in base64 format.
You need to put this code on your remote site in the tag <head>.
After you install the code, every click on the site will be processed by a script and all data will be transferred to the tracker, and to the campaign where the integration script was taken.
A distinctive feature of this script is that it is unique every time and the moderation bots still haven't tagged it.
As I already said above, the code sends a request with the click data to the tracker and waits for a response, then it can perform any action set in the campaign.
The key action of the script is the ability to rewrite the content of your remote page (switch on page from the tracker), without redirecting and changing the domain.
Therefore, all that remains for you to do is to launch an advertising campaign to your remote site, then wait for the targeted traffic and set up the conditions in a stream, under which it will recognize targeted traffic and send it to the cash flow. The content of this stream will be sent to your original site without changing the domain or redirecting.
It looks like this:
You need to put this code on your remote site in the tag <head>.
After you install the code, every click on the site will be processed by a script and all data will be transferred to the tracker, and to the campaign where the integration script was taken.
A distinctive feature of this script is that it is unique every time and the moderation bots still haven't tagged it.
As I already said above, the code sends a request with the click data to the tracker and waits for a response, then it can perform any action set in the campaign.
The key action of the script is the ability to rewrite the content of your remote page (switch on page from the tracker), without redirecting and changing the domain.
Therefore, all that remains for you to do is to launch an advertising campaign to your remote site, then wait for the targeted traffic and set up the conditions in a stream, under which it will recognize targeted traffic and send it to the cash flow. The content of this stream will be sent to your original site without changing the domain or redirecting.
It looks like this:
In the first stream, we set an action - Do nothing.
As soon as we are ready to receive targeted traffic, we turn off this stream and all clicks from the remote site will be checked according to the conditions of the second stream. (Of course, non-targeted clicks and bots will not have a creative_id or ad_campaign_id value).
Therefore, they will remain in the second stream, and all targeted traffic will go to the third, where your local landing page will be, which will be sent to your remote site.
The built-in bots base is rather weak and not very suitable for working with sources such as Tik-Tok, Google Ads, Facebook, and others. Therefore, you can filter by click parameters, as in the screenshot above.
Or use the available integrations: Imklo, Hide click (services similar to Cloak it, Magic Checker or Fraud Filter).
Or even write your own filter and integrate it into the tracker.
Additionally, you can add a built-in Bot filter with your own IP lists or UserAgents/signatures.
This scheme is simple to implement and the quality of traffic processing only depends on you.
I hope this article helps you generate a lot of traffic to popular verticals in the affiliate marketing market.
For more information, or to ask a question, send a message to our support team, who is available during working hours.
