The AutoLoginer hack is responsible for simulating clicks on autologin links. It does not touch leads in live traffic and works only with leads forwarded manually or via the rebox hack.
Hack settings interface
- Checkbox Enable emulation of clicking on autologin links controls the global activation of the hack. You can leave the checkbox unchecked and configure the hack at the specific offer level.
- Work in selected countries only. The list limits the countries the hack will work with. Used only when the hack is globally enabled.
- Work for selected offers only. The list limits the offers the hack will work with. Used only when the hack is globally enabled.
- Work with selected companies only. The list limits the companies the hack will work with. Used only when the hack is globally enabled.
- Checkbox Request IP via proxy before sending lead. Automates requesting the IP address that the proxy is currently using. The proxy address is reset via the link before this request and before sending the lead (if the proxy supports such operation and the corresponding setting exists).
- Proxy servers database. A list of your proxy servers and their details. Add a new proxy using the "Add proxy" button. The add form contains the following fields:
- Proxy Country. If your proxy works with multiple countries, select Worldwide.
- Host. Proxy address in the form
proto://host:port. Formats for different protocols and available macros are shown below. -
Authorization. Proxy authorization data: for login and password use the format
login:pass, for login only —login, if authorization is not used — leave the field empty. - IP reset link. Used to reset the proxy server IP address, for example to obtain a new random IP or to set the proxy to the required geo.
- Log file. You can create a file where the hack requests will be logged. Just specify the desired path, for example
/var/www/autologin.txt. We recommend using it — very useful for debugging. - API link of the transition emulation service. Allows using third-party services for emulation. Useful if JS support is required. More details will be given below.
Proxy format
Specify the host strictly according to your proxy protocol. Pay special attention to proxies with domains. An incorrect format will not work.
- HTTP with IP address:
12.34.56.78:910 - HTTP with domain:
proxy-host.com:910 - HTTPS with IP address:
https://12.34.56.78:910 - HTTPS with domain:
https://proxy-host.com:910 - SOCKS4 with IP address:
socks4://12.34.56.78:910 - SOCKS4 with domain:
socks4a://proxy-host.com:910 - SOCKS5 with IP address:
socks5://12.34.56.78:910 - SOCKS5 with domain:
socks5h://proxy-host.com:910
Macros
The following macros are supported in the proxy, login and IP reset link:
{geo}- two-letter ISO country code of the lead in lowercase.{geoup}- two-letter ISO country code of the lead in uppercase.{ip}- the original IP address of the lead.{lang}- two-letter ISO language code of the lead in lowercase.{langup}- two-letter ISO language code of the lead in uppercase.
Offer parameters
Activation and configuration of the hack at the offer level are done via the following parameters:
autologiner- enable automation on the offer.autologinerZZ- enable automation for the company with identifier ZZ.auto-proxy- proxy address for automation in the standard format.auto-pauth- proxy access credentials in the standard format.auto-ipurl- URL to reset the proxy IP address.
Some parameters support geo-specific values. Simply add -xx to the end of the name, where xx is the two-letter ISO country code.
autologiner-xx- enable automation on the offer.auto-proxy-xx- proxy address for automation in the standard format.auto-pauth-xx- proxy access credentials in the standard format.auto-ipurl-xx- URL to reset the proxy IP address.
You can use offer-level settings simultaneously with the global settings.
Important! The hack uses global settings for all offers by default. If you specify proxy settings via offer parameters, be sure to provide all auto-* parameters — global parameters will be ignored in that case.
API integration with an emulation service
The hack uses emulation without JS support. If you need JS support and full emulation of the transition, you can connect via API to a third-party service.
In the API link of the emulation service field, specify the service URL and provide the required parameters.
Available macros:
{url}- autologin link{ua}- User-Agent{geo}- country{lang}- browser language{ip}- IP address{referer}- referrer{proxy}- proxy address{pauth}- proxy authorization data{name}- customer name{last}- customer sirname{email}- customer email{pass}- customer password
To send a POST request or JSON format, append |POST| or |JSON| respectively after the URL, then provide the necessary data in urlencode format.
Example GET request:
http://fuck.it/?token=foo&url={url}&geo={geo}
Example POST request:
http://fuck.it/?token=foo|POST|url={url}&geo={geo}
Example request in JSON format:
http://fuck.it/?token=foo|JSON|url={url}&geo={geo}
Minimum requirements
For successful operation you must have a proxy pool covering all required countries. You can assign a separate proxy per geo or use a proxy whose geo is specified in the address, login, password or IP reset URL. It is recommended to use residential or mobile proxies that change the IP address via a reset URL.
Optimal hack setup: create proxies, specify the list of geos and companies to emulate, enable the hack.
Very important! The hack cannot be used without proxies!