How To Make Money With Affiliate Marketing and The Car Dealer Chatbot

---

---

---

Mask Your Affiliate Link With Your Domain Name

If you would like to mask your Chatbots.Systems Affiliate URL with your own domain web link, see the below for different options. Please consult your webmaster and backup any config files before making any changes. It is recommended that you save all your original settings in case they are needed.

The Affiliate ID of 1 will be used for the examples below. The ID is the number at the very end of "Your Unique Referral Link”. Be sure this number matches your ID number at the end of “Your Unique Referral Link” on your Affiliate Page.

APACHE - redirecting all traffic from https://www.yourwebsite.com/chatbots to https://clients.chatbots.systems/aff.php?aff=1

<VirtualHost>
	DocumentRoot "/www/example1"
	ServerName www.example.com
	Redirect "/chatbots" "https://clients.chatbots.systems/aff.php?aff=1"
<VirtualHost>

NGINX - redirecting all traffic from https://www.yourwebsite.com/chatbots to https://clients.chatbots.systems/aff.php?aff=1

server {
	listen               xxx.xxx.xxx.xxx ssl;
	server_name          www.example.com;
		
	location /chatbots {
     	return 301 https://clients.chatbots.systems/aff.php?aff=1;
  	}
}

Use HTACESS only if you are using it already or if you have to

In general, you should only use .htaccess files when you don't have access to the main server configuration file. There is, for example, a common misconception that user authentication should always be done in .htaccess files, and, in more recent years, another misconception that mod_rewrite directives must go in .htaccess files. This is simply not the case. You can put user authentication configurations in the main server configuration, and this is, in fact, the preferred way to do things. Likewise, mod_rewrite directives work better, in many respects, in the main server configuration.

.htaccess files should be used in a case where the content providers need to make configuration changes to the server on a per-directory basis, but do not have root access on the server system. In the event that the server administrator is not willing to make frequent configuration changes, it might be desirable to permit individual users to make these changes in .htaccess files for themselves. This is particularly true, for example, in cases where ISPs are hosting multiple user sites on a single machine, and want their users to be able to alter their configuration.

However, in general, use of .htaccess files should be avoided when possible. Any configuration that you would consider putting in a .htaccess file, can just as effectively be made in a section in your main server configuration file.

Source: http://httpd.apache.org/docs/current/howto/htaccess.html

# -- By default, Redirect maps the path node to a new path node, so anything after the first path gets appended to the target URL.
RedirectMatch 301 ^/chatbots https://clients.chatbots.systems/aff.php?aff=1

#-- Or if you'd rather use mod_rewrite instead of mod_alias:
RewriteEngine On
RewriteRule ^/chatbots https://clients.chatbots.systems/aff.php?aff=1 [R=301,L,NC]

Example: https://cdn.chatbots.systems/chatbots

The above link clearly shows and resolves to https://cdn.chatbots.systems/chatbots but the visitor clearly redirects to https://clients.chatbots.systems/aff.php?aff=1.

Each time you click on your Affiliate Link, the number that represents the "Clicks" located inside the blue square will go up by 1. This number is also seen in Step 3 in the image above.

---

---