I had an extremely brief discussion the other day about custom code, Extensions, and data quality, with Urs Boller. You all know how much those three topics mean to me, and that I have some opinions on all three of them. I also have a lot of respect for Urs, so when he challenged my … Continue reading No Custom Code – is an Extension the answer?
I built an Extension some time ago that enables someone to set contextData for Analytics directly in the Launch UI. You can see the source code for that Extension on github, of course, but today, I want to write about some of the stuff that went into the Extension. This is also, in a way, … Continue reading Extensions and Adobe Analytics – get-tracker and augment-tracker
Those of you who have been to the Adobe Summit, or any other big event like it, may have been a victim of post-Summit blues - the feeling when you're back from a couple of ridiculously intense days of listening, meeting, talking, discussing, and fully committing to one single subject. It is part exhaustion, part … Continue reading Quo vadis, W4D?
Debugging and troubleshooting code is one of the less glamorous things we (and you) do, still sadly omnipresent. Today, I want to show you how to take away a little bit of the pain: I'll show you how you can tell Launch to deliver un-minified code. This is an extremely quick and easy tip, tbh, … Continue reading Quick tip – non-minified Launch code is easier to debug
Pedro Monjo's reaction to my last post was to simply quote this bit: "Well, obviously, we build an Extension!" My brain cannot stop thinking like that, and it's all because I think encapsulating or hiding complexity behind a UI will help greatly in the long run. I don't even want to tell you how many … Continue reading 7 things I learned about making Extensions
For some reason, I have lately been exposed to a lot of Angular Single-Page Applications. As you probably know, SPAs are the mortal enemy of the analyst, or at least the implementer, but as you also know, we must overcome our fears to grow. Or something like that. While this sounds empowering to some, and … Continue reading Basic Tracking – Angular SPA & angulartics2
If you haven't yet heard it: In Launch, by Adobe, the _satellite.track() method accepts two parameters: an Event name, plus payload data. We used to work around this in the past when calling DCRs in DTM, storing the data somewhere in the DOM. My favourite method was the one first shown to me by my … Continue reading Quick tip – Passing Data into Launch Rules
Adam Greco recently wrote three articles about how you can embed business requirements into Adobe Analytics Workspaces ("Adobe Analytics Requirements and SDR in Workspace" I, II, and III) in order to help data consumers understand. His method goes all the way from "this is why we added eVarXY" to "78% of requirements are currently tracked … Continue reading A Standard Data Model for Requirements