Firefox Will Soon Block Third-Party Cookies
 

Make sure each CCBill sponsor has IP Tracking switched on, if the cookie lasts over 3 days then IP Tracking is switched off. :2 cents:

http://yro.slashdot.org/story/13/02/..._medium=f eed

"Stanford researcher Jonathan Mayer has contributed a Firefox patch that will block third-party cookies by default. It's now on track to land in version 22. Kudos to Mozilla for protecting their users and being so open to community submissions. The initial response from the online advertising industry is unsurprisingly hostile and blustering, calling the move 'a nuclear first strike.'"


CCBill

"When the expiration value is greater than 3, no extra data will be logged to CCBill's database, so the cookie will be the only means of tracking a referred sale. If the surfer does not accept the cookie, the system will not be able to track them."

Check each cookie here

http://www.rexswain.com/httpview.html

Once it's produced a load of data, search for "expires"

So we want everything at the 3 default now?

If I understand correctly, a third party cookie is where an inline object such as javascript, an image, or an iframe is fetched from an external site, and sets a cookie.

ccbill would NOT be affected because their tracking cookie is set when you click on a link to their domain.

I was wondering about this myself, I was hoping someone was going to come in and write what you have. Hopefully you're right :thumbsup

If CCBill cookies will be blocked, then yes, or perhaps CCBill would increase their maximum IP Tracking. :2 cents:

"If a cookie is associated with a file requested from the same domain as the page you are viewing, it’s a first-party cookie. A cookie associated with a file requested from a different domain is a third-party cookie. That’s it."

"Notice that the same cookie can be a first-party cookie one moment and a third-party cookie the next. For instance, when you visit twitter.com your browser sets several cookies associated wth the *.twitter.com domain name. In the context of your stay on Twitter these are first-party cookies. If you then visit huffingtonpost.com, Huffington Post requests files from twitter.com and those requests include the same *.twitter.com cookies, which are now third-party cookies."

http://www.ravelrumba.com/blog/third-party-cookies/

According to CCBill if third party tracking data is not allowed and IP tracking is switched off, then there's another mechanism of tracking with lasts for 24 hours. :2 cents:

http://ccbill.com/cs/wiki/tiki-index...+for+a+sale%3F

"We track consumers primarily through a Cookie, in this case a Cookie is an Internet tracking device that is saved in a browser then tracked before and after a consumer sale. This Cookie can track anywhere from 3 (default) to 255 days depending on Sponsor Program settings. If the consumer does not accept third party cookie tracking data we have a redundancy in place that will track the sale for that consumer for 24 hours."

I'd say the redundancy mentioned is the IP. The only other way I can think of tracking without IPs and cookies would be passive browser fingerprinting, or something shifty like abuse of etags.

this.

I've always got 3rd party cookies blocked and anything I test tracks fine.

What is the big deal with cookies anyway? Customize users experience and tracking marketing spend are completely legitimate. I have never heard of someone getting their computer messed up over cookies or anything like that, why is everyone trying to get rid of them?

technically it wont matter to ccbill links.

It started when antivirus companies ran out of ideas for the first time. They had done all they could with virus detection and user interface improvements, so they created the tracking cookie boogie man. It was something new.

Seems to me that IMers are going to have to get back to the basics............................................ ..........

Double-opt-in email lists come to mind.

:2 cents:

What the fuck is a tracking cookie boogie man? Do you mean everlast cookies? Those are fucking serious, I tried to use one in real life (which as far as I know, they are not used) and accidentally set one on myself I could not get rid of. Fucked my site up for me. I think I still have the cookie but I had to change all my code to ignore the cookie!!!! Very hard to get rid of. :mad: But more people will use these fuckers when they can't use regular cookies anymore.

For those who don't know, everlast cookies are a grouping of "cookies" which some are not really cookies but they store multiple methods of the cookie data and/or will reload the cookie in all your browsers! So cache image will have code in it, regular cookie has code, flash cookie, silverlight data, and all sorts of programming shit you never deal with has little memory clusters where you can store and execute code to hold the cookie data or to execute to retrieve the cookie again if any one part is deleted. So you need to delete every single instance at once and then open your browser and you will be OK. Currently I think there are around 25 storage areas that have been discovered for the average system.

You didn't do it right.

:2 cents:

it gets harder and harder to be an affiliate these days

What makes you say that? :1orglaugh