Hello, everyone! Today, I decided to write a guide on cloaking with JS clients. To put it bluntly, this is the code that integrates into
<head></head> of the white page you created in a builder. In this case, for FB, the builder acts as a trusted platform. Aside from that, white pages are easy to create in the builder.
What will it look like for the customer?
The customer clicks a link: ahuenno.mystrikingly.com and is redirected to the white page. The JS script is triggered in the “head” line and transmits the received click to the Keitaro, where bots are sifted according to your campaign settings. If a user/bot has not passed verification, they remain on the page without base href content substitution, which by default would be replaced in Keitaro as with local cloaking. That is, the user/bot stays on the same page which is just great for FB. But if a user (your potential customer) has passed the review, then the content is substituted and the user will see the black page with the same builder URL.
As illustrated on the screenshot, a “Do nothing” action is applied to bots and a user who was rejected during verification in our intercepting and closing flows. That is, bots aren’t redirected from the white page builder.
How to install it?
Since there are numerous builders, it makes no sense to make screenshots of the JS code installation guide. Just look for a special graph in the webpage settings of your builder and insert it. So, no further comments.
How to choose a JS client?
Now that’s interesting. The pricing is quite intriguing. Here’s a list:
What did I do?
I’m not sure if I’m disclosing some insights, but at the proper time and with no extra costs it helped me to eliminate system circumvention which happened a lot. I didn’t enjoy spending $50 each time, so I decided to fetch a circuit.
So, I created an account on GitHub, paid for the monthly tariff (debited automatically), and obtained an API key. What’s it for? Guys, it’s easier than you think! Mobirize is integrated with GitHub so it allows you to download websites to its repository! That is, to obtain a ready-made cloaked link, you must:
- Open the Mobirize on the PC and build the white page. Next, insert the JS code which you’ve prepared earlier in Keitaro in the “head” line.
- Download the white page directly from Mobirize to GitHub.
- That’s it! As a result, you’ll obtain a ready-made trusted link that will look like this: ahuenno.github.io/papka1. As a rule, they do not ban such links.
Note: you’ll require third-party plugins to insert the JS code into the “head” on the home page (without the plugin, it won’t work). However, you can’t do that in the default version of Mobirize. Download an earlier release such as 5.3 and plugins here: https://witsec.nl (you’ll require a code editor).
Guys, I won’t provide a step-by-step guide on Mobirize, particularly for GitHub, because all you have to do is pay for the API key and collect it. However, you now have something to think about.
What about Pixel?
If you work with first-billing, then you won’t need it (the JS client won’t work anyway, otherwise, you’ll have to upload a bunch of landing pages in Keitaro with different redirection settings to “Thank You” pages in the builder. Learn more below). Provided you set up lead conversion, it will pick the required audience to little effect.
But if you use your budget for long-term promotion, then you should set up a short pixel on the “Thank You” page. But here’s a catch: after the customer fills out the form on the black page on the builder’s domain such as ahuenno.github.io/papka1, they will be redirected to the “Thank You” page, which is commonly left in the black page folder in the Keitaro by default, that is, the user will be redirected to the vashdomenkeitaro.ru/lander/prostatit/thank.html website. Since a potential customer is shown a “Thank You” page on one of Keitaro’s domains, a short pixel will give away the website’s referrer. FB won’t like the fact that the pixel on the “Thank You” page does not work with the builder’s subdomain (ahuenno.github.io/papka1 ).
There is a simple solution to that: after you have created a white page together with a “Thank You” page, you must open the landing page code in Keitaro – the handler file that redirects to the “Thank You” page – and insert the URL of the “Thank You” page, which is located on the builder’s domain (ahuenno.github.io/papka1/thank.html) rather than the local “Thank You” page directory. Ideally, the user must be redirected to the “Thank You” page from the white page’s form as well.
For a step-by-step guide, visit Keitaro Blog. If you want to save money, you’re welcome to try the approach I described above.
Regards, Vladimir! Welcome to my Telegram channel: https://t.me/pbvladimircard