Recently I have found some time to finally get going (thx to Simo Ahava’s TeamSimmer) with Google’s late, but intriguing arrival to the Server-Side Tag Management Zoo (SSTMZLOL). Tealium, Signal (no, not the messenger) and probably some others have had their cages there for almost a decade now. Adobe put its own elephant into that zoo last year: Launch server-side properties which leverage the Adobe Experience Platform Web SDK. So no more social distancing there. The battle is on.
Thanks to the Adobe Analytics API, you can finally get your Analytics setup back under control and put an end to user (and admin) frustration because of seemingly endless lists of components with similar names, duplicates etc.
A good data engineer can write the queries needed for the steps below herself with the Adobe Analytics API 2.0, e.g. via Julien Piccini’s Python Wrapper. …
Let’s start with one of the many examples. Somebody from Analytics writes an email to IT:
This email is great because it contains pretty much all the issues I have experienced with Content Security Policies in the last year.
I estimate that I alone spent at least a full week (42 hours) last year on Content Security Policy issues. Add to that:
Some months ago, I presented my new pet tool, the Adobe Analytics Bulk Component Editor for Google Sheets. In this video/article, I present an update: There is now a “Component Usage” Tab which shows you not only all Components, i.e. Calculated Metrics, Success Events, Segments, Dimensions or Date Ranges. It also shows you:
Then, with standard Google Sheets functionality, you can identify the unused Segments and Calculated Metrics and delete or…
In the third part of “Life with Adobe Launch”, I look at the entry bar for developing a Custom Launch Extension in terms of skills and structure. Tag Management specialists tend to have some development skills, but rarely work in the same environments nor with the tools that full-stack developers do. Developing a Launch Extension changes that: You have to learn how to work with the tools of today’s professional developers. Thus, the entry bar may be high. It was for me. But I don’t regret it and learned so many useful things along the way.
In Part II, we…
Part I covered the rocky history of Adobe Tag Management Systems (TMS). It also showed that Launch still has many of the scaling issues of its predecessor Dynamic Tag Management (DTM). Fortunately, Launch offers a way out: Custom Extensions. So if you have multiple sites and want them to adhere to a common tracking standard, such an Extension is a must. Otherwise: innovation freeze and data quality disaster.
Your organization has multiple websites and you want to change one thing globally in all of them. The only options that Launch offers without a Custom Extension (like DTM) are:
As amazing as Adobe is in Analytics, as inglorious is Adobe’s history with Tag Management Systems. Launch is the 3rd TMS in 6 years*. After the failed “Adobe Tag Manager”, Adobe “DTM” did the fancy, unimportant things well, but choked at what is most important, especially for large enterprises: scale. Launch still has many of the same problems, but offers solutions now.
In August 2019, I took on a new client. It was not a completely new stint because I had worked for them already in the past (2013–15) as a consultant with Unic. Back then, that client was one…
In part 1, I looked back at my first steps in self-employment. In this part, I compare today with my initial plans and summarize why things went well — and the one thing that is at the root of all my failures. Also, some thoughts on why it is hard to find out “the truth” on the Googles and Adobes out there.
After “reality had happened” in 2018, I postponed my naive formula of “70% work + 15% learning + 15% other construction sites”. It is still on ice. Every time I thought I could maybe reduce because some larger…
The humble Julien Piccini, author of several Python wrappers that e.g. make working with the Adobe Analytics API 2.0 a lot easier, (e.g. to build tools like my “Adobe Analytics Component Editor for Google Sheets”), recently wrote a post about “Mental Health in Analytics”. This post brought up some important issues I think about a lot as well. For a while now, I also wanted to write about my journey into self-employment aka independence aka self-built hamster wheel, since my one-man company dim28 is now over two years old.
Add or remove components from multiple Virtual Report Suites at once, changing (curated or default) names and descriptions of components, getting rid of components or workspaces that are used by nobody, replace components across all Workspaces — all in a simple Google Sheet and with a click of a button.
Note: The “Adobe Analytics Component Editor for Google Sheets” is now called “Adobe Analytics Component Manager for Google Sheets” (as you can now do much more than just bulk editing).