I am happy to present a guest post by my colleague Ben Wedenik, who, following a not so old, but very good tradition, writes about keeping implementations ridiculously simple. What does a lean and scalable Web SDK implementation look like? How to stay flexible while still having a powerful tag manager setup? I’m going to … Continue reading A Powerful Trio of Extensions for a scalable Platform Setup
Tag: javascript
Consent and Launch, part II – Opt-in
This post picks up where Consent and Launch gave up ended: what exactly happens when you're doing opt-in and a visitor has not given consent ever before? I had this down as somewhat mysterious and full of traps and pitfalls, but once I switched on the metaphorical light, I saw that it was surprisingly easy … Continue reading Consent and Launch, part II – Opt-in
Launch Libraries, “Upstream”, and Fallbacks
First things first: I will move to a monthly release cycle. The last year or so has been a total write-off for all of us. I am feeling it, sometimes more, sometimes less, but I am. I have seen what happens when you simply keep going, and it's not nice, so I am cutting back. … Continue reading Launch Libraries, “Upstream”, and Fallbacks
Why Context Data is cool when you have multiple Report Suites
A very, very long time ago, when the world was in a much simpler shape, when there was only simple, one-cell life forms in some murky ponds, and the air had high levels of CO2, NH3, and CH4, when temperatures were much higher than today, and rain would fall for millions of years on end, … Continue reading Why Context Data is cool when you have multiple Report Suites
Why I do not use setVar
In his posting on AEP Web SDK Debugging, which is excellent, my colleague Julien Piccini wrote about Data Elements, Promises, and how you can use _satellite.setVar() to store return values. As always when I see someone use setVar, my first reaction is "I should really finish this post about why I don't use setVar at … Continue reading Why I do not use setVar
Consent and Launch
I've pondered, written, deleted, re-written, forgotten, re-written, merged, and then deleted this article a bunch of times before. What you're reading today is like the 50th iteration. The kudos go entirely to my colleagues in product management and engineering, who (in my opinion) are doing a blast of a job with Launch and the Extension … Continue reading Consent and Launch
Adobe Experience Platform Web SDK
Last year, in April, I opined that a big change was coming for all of us who work with Analytics, Target, or Audience Manager. That change has been in the making for some time. I remember how Bret and Ben dropped some subtle hints some time ago in London. They were clearly exited, and, as … Continue reading Adobe Experience Platform Web SDK
Quick tip: Passing Data into a Data Element
We interrupt our regular schedule for a very quick tip today, one that I learned about just last week: you can pass data into the getVar() method, and use that data inside your Custom Code Data Element! I learned about that from fellow #measure slack contributor Francis Li, and, somewhat embarrassing, should've seen it a … Continue reading Quick tip: Passing Data into a Data Element
Lean Analytics with the Adobe Client Data Layer
This is a guest post by my colleague Ben Wedenik, one of the people who wrote the Adobe Client Data Layer Extension for Launch. When my colleagues and I started to develop the “Adobe Client Data Layer” Launch Extension, we wanted to make the concept and technology of an Event Driven Data Layer (EDDL) available … Continue reading Lean Analytics with the Adobe Client Data Layer
Why not use sendBeacon?
One reaction to last weeks article on the ACDL was from @AnalyticsNinja, and it was about the 500ms wait time I mentioned: 500ms setTimeout() in click handlers.... Isn't navigator.sendBeacon sufficient? — Analytics Sith (@AnalyticsNinja) October 23, 2020 So very right he is, and the only excuse I have is that ... no, I don't have … Continue reading Why not use sendBeacon?
