Get exclusive CAP network offers from top brands

View CAP Offers

Reply To: Is tracking working?

[bsa_pro_ad_space id=2]
#768692
Recrutwo
Member

Hi All,

32Red Affiliates stands by its first referrer policy. We believe those affiliates that make traffic aware of our brand and product initially have done the greatest amount of work, i.e. have conducted the marketing to drive people to their site and choose 32Red. This system has been in place for some time, is very successful and 32Red affiliates earn substantial rewards from the high levels of retention marketing and offline advertising that we do. Obviously, we realise that this method of tracking the first referral may not suit everyone and, as such, the feedback received on here is extremely valuable.

Let’s say, for instance, your site performs well in google for “Online Casino” – a customer searches, visits your site, sees an offer of a £100 bonus, clicks on the banner to visit 32red and a cookie is set. The visitor then realises that a bigger bonus may be available – googles “32Red Bonus” and finds a site with an outdated bonus of £200, clicks through and registers. Do you believe that the second referral should benefit?

In regard to our cookie tracking: after speaking with someone who understands the technology more than me, we do not believe it is possible to abuse the system. Cookies for 32Red can only be set from our own domain and cannot be set via external websites/pages. The only way a cookie could be set via an iframe would be if the iframe was hosted on 32red.com – something that we do not provide for affiliates. It may have been the case years ago that an older browser may have accepted a cookie with a different domain, but modern security features in browsers prevent this.

From w3.org:

Quote:
Cookies contain attributes that tell the browser what servers to send them to. The “domain” attribute tells the browser which host names the cookie should be returned to, and the “path” attribute indicates what URL paths within that domain are valid. For instance, a domain of “megacorp.com” and a path of “/users” tells the browser to return the cookie to hosts with names like “http://ftp.megacorp.com” and “http://www.megacorp.com“, and to do so only when requesting URLs that start with the path “/users”. An important security measure prevents the cookie’s domain from being set to top-level domains like “.com”. This prevents someone from creating a promiscuous cookie that will be returned to any server.

Again, thank you for your time and opinions on this matter – we welcome feedback on the affiliate program.
Regards
Aaron