Simo AhavaVerified account

@SimoAhava

Husband | Father | Blogger | Keynote speaker | Partner, Co-founder | Google Developer Expert |

Espoo, Finland
Joined October 2013

Tweets

You blocked @SimoAhava

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @SimoAhava

  1. Pinned Tweet

    Code allergy should be a thing of the past: The Myth Of The Non-Technical Marketer

    Undo
  2. Retweeted

    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?

    Undo
  3. Chrome has said that the SameSite changes will be enforced on the week starting Feb 17, and initially only to a subset of users.

    Undo
  4. 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.

    Show this thread
    Undo
  5. 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.

    Show this thread
    Undo
  6. 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.

    Show this thread
    Undo
  7. Retweeted
    Jan 31

    2020 slides uploaded: Interoperability in Digital with take a Global Village welcoming pull requests on 's OpenDSR project

    Undo
  8. Humble request to event organizers everywhere: Please have a “Social Media” section in your event pages, make it abundantly clear what hashtag / mention you want attendees & interested parties to use, and do this well in advance so that discussion can commence before the event!

    Undo
  9. Retweeted

    Need to dissect your cookies 🔪🍪 in preparation for Chrome's updates? Check out our new, in-depth guide to testing and debugging cookies with 🧰 DevTools and more!

    Chrome DevTools open on the Network panel showing all the cookie attributes for a request
    Undo
  10. Retweeted

    Once again, with some early insights into Google Tag Manager -- this time focused on Server-Side Tagging.

    Undo
  11. My slides from 2020: The presentation details the past, present, and future of browser tracking protection/prevention mechanisms. The information is based on research published on .

    Undo
  12. Retweeted
    Jan 29

    [Blog Post] Step by Step: Setting up a App + Web Property in GA (an updated UI walkthrough)

    Undo
  13. Thank you and the entire crew for yet another lovely conference. Lots of wonderful talks with wonderful friends (old and new), and a lot of inspiration to take back home.

    Undo
  14. Retweeted
    Jan 29

    Well done Golden Punch card winner '20 Also well done to ALL winners and contestants today!

    Undo
  15. Retweeted
    Jan 29
    Undo
  16. Retweeted
    Jan 29

    And now something completely the same. With at (I should absolutely think about something fresh, but I was not able to resist).

    Undo
  17. As with almost everything , it has the power to construct and destruct, alleviate friction and create more of it, improve data quality and drown signal in noise. It’s wrought with dichotomies that are resolved through maturity and informed decisions. 6/6

    Show this thread
    Undo
  18. Since it’s server-side, you might be tempted to use it for circumventing browser block lists, tracking protections, consents, etc. Yes, you can do all this. But you don’t have to be a dick. Always err in the side of max. respect for user privacy. 5/6

    Show this thread
    Undo
  19. Amazing things cont’d: - (Hopefully) direct integrations to cloud APIs (write to BigQuery, trigger cloud functions) - Reduce the amount of crap loaded in the client, as you could theoretically send a single hit to the server and then parse it for different uses 4/6

    Show this thread
    Undo
  20. Some amazing things you can do with it: - Hit validation and fixing before the hit is sent to the endpoint - PII and privacy controls for the requests before dispatch - Send same request to multiple endpoints - Customize the HTTP response back to the client (e.g. Set-Cookie) 3/6

    Show this thread
    Undo
  21. You send HTTP requests to it from the browser, and it parses these requests (using a new “Client” format), typically dispatching them to their respective endpoints server-to-server (e.g. Measurement Protocol). 2/6

    Show this thread
    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·