I am in the process of migrating from the Adobe Media Analytics 2.x
Launch extension to the Adobe Media Analytics 3.x Launch extension.
Currently I am using the Adobe Media Analytics 2.x extension to track
Brightcove videos and SundaySky videos and I have two separate Launch
rules for the implementation code of each of the two different video
players. With the 2.x extension, I am able to set the playerName
property of the mediaConfig object that I pass into the
@evolytics_brian - I've considered just using buildDate, but since we
use the Major.Minor.Patch convention for our library name, capturing it
would just make things simpler from a reporting perspective. We are
currently capturing the Major.Minor.Patch AppMeasurement and ECID
versions in an Analytics dimension, but they don't always change from
library to library. Capturing an all-encompassing version number at the
library level would just make things cleaner.
It would be helpful if there was a Core data element that returned the
value of the Launch library "Name". This would make it easy to set the
value to an Analytics eVar for debugging purposes. We name our libraries
using the Major.Minor.Patch versioning convention and it would be
helpful to know which Launch library a website visitor was using.
Sometimes after a new library is published it seems like some visitors
may have the old library cached in their browser. If we could capture
the library ...
After migrating from DTM to Launch, the Target property token is no
longer getting automatically detected within the Target VEC. Within
Launch, we are using the latest version of the Adobe Target extension.
We have a Page Top rule configured to Load Target then Add at_property
to All Mboxes then Fire Global Mbox. We would expect with this setup,
that the Target property token would be present at the time that the
Target VEC tries to detect it. Has anyone else experienced this issue.
Is there som...