
Originally Posted by
TheGooner
[/COLOR]Really?
An affiliate program using netrefer or income access software that pulls images (and deposits cookies) from remote servers different to the destination website would surely be the definition of "3rd party advertising cookies"?
Yes.
Now even more confusion.
When we talk about affiliate cookie it is always on the domain of the sportsbook. So for example IA Pinancle has affiliate cookie of domain pinnacle.com. When visitor comes through your link and later directly through typein, you would not get the credit otherwise. It is a 1st party cookie.
Netrefer at Unibet is a bit problem, I am not sure whether I am sure if it is like this, but I think: they use many Unibet.xxx domains like unibet.com or unibet.se etc. At least in some countries the tracking was through unibet.com, which looks like 3rd party cookie, but it is not. It was just done (I think) through iframes, where both affiliate click at unibet.se for example got affiliate cookie at unibet.com. Then at registration through unibet.se logically also some part of unibet.com via iframe was loaded. But I think they do not do it anymore and this is not the standard way how to do it. If anyone is checking affiliate cookies you should always check if the cookie is on the root domain of the book/casino. Otherwise complain. Cookie that is not on root domain is defacto analogy of session cookie that is however still limited by the duration of the cookie unlike real session cookie.
------
Now the second issue are the images etc (but not the affiliate cookies as described above). Yes they use second party cookies quite often, typically the ad serving domains are not on the domain of the casino or sportsbook. But those cookies impact us just indirectly and they should now affect the tracking. It can affect ad-targeting and make it worse, but this has huge impact for adcompanies, not to affiliates like us, who place at position A creative B.
If you talk to God, you are praying; If God talks to you, you have schizophrenia.