# What is referer overriding?
The referrer identifies the webpage that the previous request comes from. If you need more explanations on this concept, you can referer to the guide about hiding the referer.
When you override the referer, you make the page believe that the visit comes from a specific domain.
# Why does it matters on Autosurf systems?
By default, a visit will be direct (no referer), which can be considered as a low value traffic for specific needs when it represents a major part of the traffic.
With the override referers feature, you can put any domain as referers and your links will think that the visit comes from them, even if no link is really present on the referer page.
# How to manage the override referers feature?
- Go to your my sites page
- Click on the configuration button of one of your links and click on advanced options and info
- Find the
Change the refererrow and enable it
- You will see a table with a row below to add a new referer. You can also select pre-made referers from the suggestion list
You will see that 100% of the visits will come from Otohits domain or will be direct visits. To update this value, you'll need to set the percentage of visits to use with the custom domains you added previously
As the example below, I set 25% for Facebook and 75% for Twitter. After then, click the
- The text should now say:
Visits with custom referer: 100%
# Points to consider when using the override referer feature
- Referers are always hidden in case of failure, so the Otohits domain should not appear if there is an issue on the override
- You are free to put any domain you like. Make sure they start with
- Behavior can change depending on your links and the referer used
HTTPlink will work
HTTPlink will work but can be detected as a fraud
HTTPSreferer is not always transmitted when using
- Even if Otohits will ignore these rules and always send the referers you added, we strongly suggest you follow them.
If you need more information on these principles, you can read the following W3C article: https://www.w3.org/Protocols/rfc2616/rfc2616-sec15.html#sec15.1.3 (opens new window)