It would be great to be able to use calculated metrics within segments.
For example, create a segment that includes visitors who have a
calculated score of > 500, or a bounce rate of < 50%, or a Tax > $1000
across all their purchases. THanksTim
HiIts not actually about how to use them - we know how to do that - it's
how to get them working in DTM and AppMeasurement.js as they're not even
getting passed through. It appears like DTM is resetting contextData and
so no value is ever passed through.T
Hi We've a number of implementations where we've extensively used
s.contextData["name"] = "value".Whats the best way to integrate using
existing contextData on the page and use that data to trigger events etc
in DTM? When I try to use it I keep getting a JS error saying that
s.contextData is not defined.ThanksTim
HiWe have a number of sites that use s.contextData on the page and we
use the s_code to pick up the value and write it into props and evars
etc. Some are also using processing rules as well.Using DTM and
AppMeasurement.js we're unable to get contextdata to work. We have a
block of code on the page as follows:
if(s){ s.contextData["page"] = "product.category"; } It seems
to be getting re-initialised when the DTM code actually loads and we're
therefore unable to use it. Is this correct? Does DTM and AppMeasurement
still support contextData in this ma...
Hi Is the recently announced Visitor ID Service
(https://microsite.omniture.com/t2/help/en_US/sc/implement/index.html#Visitor_ID_Service)
available currently in when implementing via DTM? If so, can you
elaborate on how it's achieved? ThanksTim
Have to agree, even as a Discover user. It would be very handy to be
able to compare multiple segments in the reports. GA still rules the
roost on this one. While you can compare report suites, I wonder how
many use that functionality. Comparing two (or more preferably) segments
in SCv15 should be possible given the new architecture of the data.