Twitter | Pretraživanje | |
Simo Ahava
Husband | Father | Blogger | Keynote speaker | Partner, Co-founder | Google Developer Expert |
8.612
Tweetovi
491
Pratim
17.104
Osobe koje vas prate
Tweetovi
Simo Ahava 1 h
Odgovor korisniku/ci @angelagrammatas @smhmic i 2 ostali
ITP doesn’t block anything - it just prevents the cookie being set. But if GA can’t set the cookie, it probably aborts the hit. With a cookieless solution, *always* need to set “storage” field to “none”.
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 1 h
Odgovor korisniku/ci @angelagrammatas @smhmic i 2 ostali
I mean, there’s no issues with ITP or anything else if you’re just sending stuff via postMessage to the iframe page and then picking up those parameters and sending them to GA.
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 1 h
Odgovor korisniku/ci @angelagrammatas @smhmic i 2 ostali
Many ways to skin the cat. You could just as well send the hits from the iframe, as then you wouldn’t have to rewrite document location / path etc. A cookieless solution is best all things considered. Downside is that if user visits iframe page directly they’ll be a new user.
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava proslijedio/la je tweet
Google Webmasters 13 h
We had an issue with the GTM verification method in Search Console, but it should be solved by now. You might need to re-verify. More details on how to verify at
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 17 h
Odgovor korisniku/ci @smhmic @thezedwards @danaditomaso
That would work of course as would other manual workarounds, too :) G should update the SDKs to support cookieSameSite and cookieSecure fields in the tracker!
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 22 h
Odgovor korisniku/ci @kyotonio
Also, I think that Edge just warns about that if the site sends a network request to a classified domain, even if no storage is accessed?
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 23 h
Odgovor korisniku/ci @kyotonio
I think occasionally the GA endpoint drops a cookie on (maybe with the DoubleClick redirect?), which would be blocked as GA is in the “Tracker” lists.
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 3. velj
Odgovor korisniku/ci @thyng @googleanalytics
David, this is almost five years old :)
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava proslijedio/la je tweet
ℨ𝔞𝔠𝔥 𝔈𝔡𝔴𝔞𝔯𝔡𝔰 1. velj
Google only puts SameSIte updates & release dates here (), and this Friday evening they quietly pushed the release date to February 17th and then pretended like they weren't saying February 4th for months. // maybe a changelog here? more transparent edits?
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 1. velj
Odgovor korisniku/ci @scott_h_herman
Wikipedia got my back!
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 1. velj
Odgovor korisniku/ci @thezedwards @danaditomaso
Haha yeah, well, maybe Google will announce they meant Feb 17, 2021 all along.
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 1. velj
Odgovor korisniku/ci @thezedwards @danaditomaso
Yeah, it’s really fragile. Safari requires / will require Storage Access API, Chromium browsers SameSite changes, nothing on Brave... A stateless solution with window.postMessage polling on every page would prob. be best. Will write a new guide!
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 1. velj
Chrome has said that the SameSite changes will be enforced on the week starting Feb 17, and initially only to a subset of users.
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 1. velj
Odgovor korisniku/ci @rnebhwani
No official announcements because it wasn’t an official announcement. Video will come later if the speakers agree it’s ok to release.
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 31. sij
Odgovor korisniku/ci @scott_h_herman
I’d like to respond with something clever but I feel like it can and will be used against me in all future dinners with you and your team
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 31. sij
Odgovor korisniku/ci @danaditomaso
It would! Without being able to set the cookie in the iframe to SameSite=None the cookie would not get set. It might work on the first page but if the user navigates in the iframe a new client ID would be generated.
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 31. sij
Odgovor korisniku/ci @BrianClifton
:D it was good seeing you briefly - too bad we didn’t get a chance to chat proper! Next time, then.
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 31. sij
Odgovor korisniku/ci @SimoAhava
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.
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 31. sij
Odgovor korisniku/ci @googleanalytics
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 _ga cookie. Without SameSite=None;Secure that cookie can’t be accessed and tracking won’t work.
Reply Retweet Označi sa "sviđa mi se"
Simo Ahava 31. sij
PSA: The upcoming 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.
Reply Retweet Označi sa "sviđa mi se"