You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 author: [email protected] (February 08, 2012 15:44:42)
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: http://code.google.com/p/openrtb/issues/detail?id=42
The text was updated successfully, but these errors were encountered: