Thanks for the informative session on the web SDK! It’s great to see experts like Mitch and Joe explaining things so clearly. I use Plerdy for free on my site because it helps me understand visitor interactions easily, which makes web optimization a breeze. 👍 Looking forward to more such insights!
Joe, if your team owns the web sdk extension, maybe make a better way to update xdm vars on the fly? Something that wouldn't require the awkward and confusing merging of dataelements? Maybe also allow custom javascript portion in actions and expose the content in it? Simple things. Nothing more than what we had in appmeasurement extension. Oh and also versions! No versioning for the websdk extension and its callback? That callback is as important as doplugins in the AA extension. Seeing the history of its changes is crucial. I'm shocked it's not the part of the initial release. And yes, thanks for at least giving us the callback. That helps hotfixing poor web sdk implementations.
Thanks for the informative session on the web SDK! It’s great to see experts like Mitch and Joe explaining things so clearly. I use Plerdy for free on my site because it helps me understand visitor interactions easily, which makes web optimization a breeze. 👍 Looking forward to more such insights!
This is Excellent stuff! Great job in explaining all the intricacies!
Joe, if your team owns the web sdk extension, maybe make a better way to update xdm vars on the fly? Something that wouldn't require the awkward and confusing merging of dataelements?
Maybe also allow custom javascript portion in actions and expose the content in it? Simple things. Nothing more than what we had in appmeasurement extension.
Oh and also versions! No versioning for the websdk extension and its callback? That callback is as important as doplugins in the AA extension. Seeing the history of its changes is crucial. I'm shocked it's not the part of the initial release.
And yes, thanks for at least giving us the callback. That helps hotfixing poor web sdk implementations.