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
Wait? What? How can this be part 4? Where are parts 1 through 3? I am very liberally counting things, disregarding slight differences in titles, and tools, so the previous parts are: With DTM you don’t need Plugins! – Part 1 With DTM you don’t need Plugins! – Part 2 With DTM you don’t need … Continue reading With Launch, you don’t need doPlugins! – Part 4
Back towards the end of April, a test manager at one of my clients listened to me talk about the test framework I had built over the last couple of years. He was supportive and eager to run tests. He also very casually asked me why I hadn't considered "Behaviour-driven development", BDD, instead of TDD. … Continue reading BDD > TDD – Site Infrastructure Test v4