With regards to an Analytics implementation, it's not clear to me at the
moment how to format the XDM such that an event simply increments a Page
View. In AppMeasurement we had s.t() vs s.tl() to explicitly set or not
set the hit as a Page View, but there don't seem to be analogous
functions in alloy.js.Launch has web.webpagedetails.pageViews as a
suggested XDM event type when triggering a 'Send Event' action for the
AEP Web SDK - I'd assume an event with this type would automatically
flag the h...
Supporting the renaming of _satellite would be the easier part. The more
difficult part would be avoiding conflicts in persistence layers (e.g.,
localStorage, sessionStorage, cookies) and conflicts in in-memory
objects (e.g., the same extension in two properties loading the same
library twice).I believe our direct team could prevent conflicts in our
code accordingly, but placing a burden on extension developers to ensure
no conflicts if their extension is used twice on the same page would be
Ah yes, sorry I didn't think to mention that. That flag isn't selected
by default but I do agree, having a message in the console indicating
the flag is on would be helpful. I'll be sure to mention it to the team.
Sounds like a great opportunity for someone to write a "perfect"
extension in launch for the integration. Launch is being built as an
open platform where customers and third-party consultants will be able
to build their own extension. This will allow for our experts within the
community to build integrations with just about any pixel/tag out there.
We will no longer be limited by having a single team being responsible
for every integration and extension.
You can reuse variables but not in the way you are thinking. Setup Data
Elements within DTM to do this. You can have a Data Element named
"ProductID". Then within analytics you set eVar1 (or whatever variable)
to %ProductID% and then you can use that Data Element for any other var
or tool or tag that you are using DTM to deploy.Data Elements -- See
this link for more info on Data Elements.