Background/Problem Description:
Certain browsers have 3rd party cookie support disabled by default. Namely
Safari 5.1. This can cause major issues for DSPs and affects things such as
frequency capping (as there is no way to fully single out the user). Typically,
we have witnessed that for each auction request generated by these browsers
that a brand new SSP userid is generated each time.
Proposed Solution:
Browser facing SSPs should be evaluating whether or not 3rd party cookies are
enabled and should be passed this through on the auction request. There are
many ways of determining whether 3rd party cookie support is supported - namely
by watching for cookie persistence or by a two-pass redirect mechanism when no
domain cookies are detected (on SSP ends).
Original issue reported on code.google.com by pa...@sitescout.com on 8 Feb 2012 at 3:44
Original issue reported on code.google.com by
pa...@sitescout.com
on 8 Feb 2012 at 3:44