averageradical

<p>Non-technical summary: Track incoming referrer and write it to any hidden form field with the identifier “referrer” (this can be created in Contact Form 7, for example; see below). Also if the WordPress site redirects from HTTP to HTTPS, this plugin also overrides the redirect to add the referrer to the https URL.</p>
<p>Technical details: This plugin runs client-side JavaScript in every page in HEAD and if there isn’t a session cookie with the name “referrer”, then it writes a session cookie with the name “referrer” and the value of either document.referrer, or if that’s empty, the URL-encoded value of window.location.href. There is another client-side JavaScript in every page before  which writes the value of the “referrer” cookie to any INPUT with the ID “referrer”, if it exists.</p>
<p>When integrating with Contact Form 7, add a hidden input field such as the following:</p>
<pre><code>[hidden referrer id:referrer]
</code></pre>
<p>And then add to the Mail’s Message Body:</p>
<pre><code>Referrer: [referrer]
</code></pre>
<p>If you’re just integrating this with HTML, just add this to any form:</p>
<pre><code><input type="hidden" id="referrer" name="referrer" />
</code></pre>


track-incoming-referrer

Track incoming referrer and write it to any hidden form field with the identifier "referrer".

Didier Sampaolo

<p>This plugin uses a blacklist to filter your incoming traffic and block “spam referrer” attacks.</p>
<p>This blacklist has been compiled using the author’s website and a few others : during the plugin’s<br />
<em>beta-testing phase</em>, a few webmasters sent their reports to the author in order to find a suitable list of<br />
domains actually using false referrers to spam (at least) some websites statistics.</p>
<h4>Terms of use</h4>
<p>There aren’t any terms, conditions or restrictions to the use of this plugin and/or the Blacklist : feel free to reuse<br />
our work ! If you want to use the SpamReferrerBlock Blacklist for other purposes than this plugin, we simply ask that<br />
you consider linking to this page, to the plugin homepage, or to our blog. That’s all 🙂</p>
<h4>The Webservice</h4>
<p>This plugin uses a Webservice. Please be advised :</p>
<ul>
<li>You <strong>will</strong> retrieve information from our server. The “Blacklist” consists of a plain JSON file.</li>
<li>No need to register or provide personal information.</li>
<li>Free of charge, forever.</li>
<li>Caution – We technically <strong>can</strong> access some information while you request the file : your server’s IP address and<br />
server name, and so on. But we (honestly) <strong>DO NOT</strong> use <strong>ANY</strong> information that can be sent to our server during the downloading process, in any way.</li>
</ul>
<h4>Updates</h4>
<p>The blacklist will be updated as often as possible, we expect to release weekly updates.<br />
You can choose to automatically download the blacklist once a day.<br />
You can choose to filter all connexions or only the first of every session.<br />
Webmasters are encouraged to submit spammy URLs to help us improve the blacklist (see FAQ).</p>
<h4>Why this plugin ?</h4>
<p>I wrote a post about spam referrer attacks and how to avoid them on my blog : http://www.didcode.com/code/stop-spam-referrer.html (fr).<br />
Some webmasters asked me (on Twitter) to write this plugin. They were also targeted by “spam referrer attacks” and sent me the originating domains.<br />
I compiled a list and put it in a JSON file, which is called by the plugin.</p>
<p><a href="http://www.didcode.com/spam-referrer-block" rel="nofollow ugc">Plugin home page</a> (fr)</p>


SpamReferrerBlock

This plugin prevents spam referrer attacks by filtering your incoming traffic.

track-incoming-referrer vs SpamReferrerBlock