On the back of defaulting header wrapping why not allow companies/users to set their own defaults for all options in workspace?we tend to always turn off anomoly detection and background bars, set funnels to visit and turn off flow truncation. Would be great to allow us to set these as new project d...
This seems like a very gaping and worrying hole in the security of the API I can’t believe that it’s possible for any user to modify admin settings via web services API. May need to cancel an entire project based around the API now...
I've got a lot dataelementchanged and pushState rules in place for our SPA with no noticeable impact, think if you're responsible and savvy you shouldn't have any issues.
Do you mean the callback functions in AppMeasurement from v1.8.0 onwards?Documentation on it is pretty light but it's straightforward to use. If you have a specific question ask away.Added the following pre- and post-tracking call hooks.s.registerPreTrackCallback s.registerPostTrackCallbackThese fun...
The only supported way to implemented DTM is by hard coding it to the page, any other way than this will mean Adobe will be unable to support your implementation.Becasue of the way you are implementing DTM any functions which rely on non ASYNC loading will be rendered unusable.
You have HTML in your tag and it can only contain pure JS, you need to remove all HTML before you can use your tag, otherwise you can change the type to an HTML tag however it's better for performance if you use pure JS.
I get this quite frequently too, the marketing cloud login system is just not fit for purpose in its current state. I have heard work is ongoing to banish this issue but heard no dates as to when.