PSA: The upcoming #SameSite enforcement in Google Chrome v80 (Feb 4) *can* impact your first-party analytics trackers.
If you load content from a cross-site host in an iframe, any JS cookies being accessed within that iframe would need SameSite=None;Secure settings.
#measure
-
-
This applies to a common scenario where the site loads a third-party booking flow or shopping cart in an iframe, and tries to do cross-domain tracking with e.g. the
@GoogleAnalytics _ga cookie. Without SameSite=None;Secure that cookie can’t be accessed and tracking won’t work.1 reply 0 proslijeđenih tweetova 2 korisnika označavaju da im se sviđaPrikaži ovu nit
Solution is to petition your analytics vendors to make the SameSite and Secure flags configurable when the tracking cookie is created. I’ve given feedback to Google about this. For Safari, you’ll need the Storage Access API. https://web.dev/samesite-cookies-explained/ … https://developer.mozilla.org/en-US/docs/Web/API/Storage_Access_API/Using …
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.