This is actually as setting to assign the s variable globally within the
AA ext which has been enable. The concern is rather when the data
elements are evoked within Launch that yield different results for 4
types of Page Load events.
For AppMeasurement managing the library I think it's a good idea to send
the version within a prop to know when the versions change in the event
there's some reporting anomalies. I discovered setting a data element to
the value of the s.version only works if the beacon is sent after DOM
ready.However, if setting the prop manually within custom code, in the
AA ext(enable after settings..) or page top rule this appears to work as
expected. I'm unsure if this is due to a race condition or if this i...
actually JS value is an empty string doesn't return the 'Default Value'
is set within the data element. An empty string is returned instead.
Since an empty string is considered to be a false type in JS, developers
might expect then to rely on the 'Default Value' to be populated
instead. Is anyone else experiencing this? If so, this should be updated
if the JS path resolves but return an empty string vs a ref error, then
This setting doesn't allow sub domains. if adding blog.example.com is
says the example.com has already been taken. Some what confusing as to
what sub domains means per that documentation. Are you able to elaborate
on this? Thanks
Thanks BarryLennon for pointing out the event Types! this should really
be stated on the adobe site.Quick question, would recommend configuring
the events Types to 'No Subrelations'? I only ask per Adobe official
recommendation states "In almost every case, you should choose the event
type that does not have the "No Subrelations" condition (Chapter
11-8).Thanks again for pointing this out!