One of the most notorious misses on Google Analytics 4. Is the lack of AMP (Accelerated Mobile Pages) Pages tracking support. While this may not be an issue for many sites, there're some website types that really need this support (like media sites or magazines). That's why I decided to investigate the possibilities of <amp-analytics> Component and APIs in order to try to build an AMP…

When Google Announced Google Analytics 4, I started to work on this library, with the main aim to be used as a customTask. Now the current deadline is 1 year-ish for all free Universal Analytics users and 3 extra months ( thanks? ) for paid users. In my very humble opinion, this is very short notice for such a big work. In my experience, a big implementation will take at least 6 months…

If you're using Google Tag Manager for setting up Google Analytics 4 tracking you may have noticed the need of creating a separate tag for each event we want to track. While this gives a really nice and easy-to-understand photo of the current used events, it may add a ton of work for maintaining them, for example, if at some point we end up having hundreds of them.In Universal Analytics many implementations…

I must admit it, I miss the flexibility the customTasks give to Universal Analytics, and I really hope someone takes a step forward at some point by adding that feature to Google Analytics 4.In the meanwhile, I was in the need of doing parallel tracking, ie: sending the data to two different Measurement IDs and that would mean duplicating all the event…

At his point, many ( if not all ) have heard Google Analytics is moving to an "events" based tracking model with Google Analytics 4. But, what does it really imply? Do we have to worry about it?. To be honest, it's not a big ( from the implementation side ) deal since we have been already using "events" all the time, we used to call them hit types. If we look at it from…

Now that Universal Analytics deprecation has been officially announced, it's time to start writtingsome technical posts about how things works on Google Analytics 4. First one, is going to be about how Cross Domain Tracking works, ( not only for GA4 but also for any GTAG.JS based tool ). Back in time (about three years ago) I noticed a new "_gl" parameter being attached to some links by Google…

This past February, I attended to the SuperWeek Conference in Egerszalók / HU, where I decided to participate on the Punchcard Prize with a new tool that I had been using interally over the past years. The only difference is that I used to use it with some command line interface and for releasing it I build my first Window application ever ( beside an NFO Viewer for an European demogroup back in the years ).…

It took me almost a year ( once again ) to have a new version, but this time I did the things properly, I’ve restarted the tool totally from scratch, I re-did the dev environment, I re-coded the detections code, I changed the CSS Framework, I updated the JS backend. There have been hundreds of commits, hundreds of hours , and so much fun and learning in the process. If you ask me the main features beside the more accurate reporting are the new Preview…

This weekend I was doing a, long-due, room cleanup and I found buried in the bottom of a drawer an old hard I was using some years ago. Within it's content I found one folder named "WIP" ( Work In Progress ) and there I found some experiments, tools and proof of concepts I was working on 4-5 years ago and that got lost on the desk drawer when I upgraded my computer to a SSD drives.It seems that at some point I was playing around…

If I were asked about some missing feature on Google Analytics 4 ( a.k.a. APP+WEB, New Web Analytics ), I would say it would be the lack of the customTask functionality that my friend Simo has leveraged in the last years. Sadly at the moment there's nothing similar available ( I really hope to have something in the future ). In the past I collaborated…