Is anybody having this beta feature enabled in its instance in combination with strict mode? If so we can maybe share issues, questions, etc... through this discussion.
Next to that, is there anyone that has the latest info on what information we are not able to capture when using only third party cookies? As per my latest understanding it's still only Safari by default blocking all third party cookies, right?
What we have noticed so far:
Non-SSL domain:
- Standard Eloqua banner setting third party cookie instead of first party one
- Strict mode only working if first party cookie in place, third party cookie being ignored ? I was under the assumption that if no first party cookie available Eloqua would always revert to the third party one (if present)
- Opt-in / out via Javascript generates different type of (first party) cookie (OPTIN=1 vs. OPTOUT=s9999999999=1), which is being ignored, doesn't have any effect on tracking
SSL domain:
- ELOQUA first party cookie is set as http and has a dummy value (GUID=%7b00000000-0000-0000-0000-000000000000%7d)
- Standard Eloqua banner setting third party cookie instead of first party one
- Strict mode only takes into account the third party cookie, if there's a first party one it is being ignored (so opposite behavior of the non-ssl domain)
- Opt-in / out via Javascript doesn't work, getting below error:
- Mixed Content: The page at 'https://xxx.yyy.zzz' was loaded over HTTPS, but requested an insecure script 'http://app.inform.janssenpro.eu/visitor/v200/svrGP.aspx?pps=41&siteid=19885…ed73&elqCampaignId=&ms=957&firstPartyCookieDomain=app.xxx.yyy.zzz'. This request has been blocked; the content must be served over HTTPS.