This should either be renamed or give the user greater control over what
gets cleared. From my understanding in talking with Support, the Clear
Variables (previously clearvars()) only clears props and events, but not
evars, so I thought it was odd that something that is labeled "Clear
Variables" would only clear certain variables, but not others
(especially not the one with "var" in it's name).
Looking through my clickstream data it seems that some email packages do
support cookies, but not all do. I've run a test by setting the vid to a
unique id and that seemed to track nicely in the clickstream and it
keeps my visits (20 minute increments) together and it keeps my unique
visitor proper. Plus I'd be able to easily track usage across devices,
which would help answer the question of how many times to people use
both phone and desktop for email (or at least multiple devices).
Interesting, but this would mean we'd need to pass the vid on each
request, correct? We have something that we could use, but we're not
using it yet (I inherited this application and I'm busy trying to undo
several knots).
We currently have email opens working pretty well, we have an image in
place that calls our adobe endpoint and passes variables, both props and
evars. I was thinking though, what's the purpose of using an evar in an
email open, especially when not all email clients don't support cookies
(I'm guessing browser based clients may support cookies). If a true
session was being set with a visitorID and all, I could see the point of
having a session variable like an evar. Is there something I'm missing?
Peter,Not sure if what you say makes sense, I'm not sure if I follow
that first sentence. We're looking to do the same, with DTM. From what
I've seen in DTM when you load the Target extension, it starts loading
on every page load. If for example we only want to load target on a
given
path:https://blah/load/target/herevshttps://blah/everyotherpath*Can you
do that with DTM? Seems that you can with Launch, but I haven't see that
in DTM.Philip
I was able to show the adobe tech who was working with me the issue and
they were confused about why it would show it's firing, but not record
the event.
Tanvia,It was all working as it should, I saw the click in the debugger,
but target itself wasn't recording it. I went to Adobe support, they
took a while to get back, by then we had to remove target from that
application since it was causing issues with different parts of the
application and IE 11. We're working to get it reinstalled.Philip
Gauresh,Thanks for the reply, what I'm seeing is:notifications: [{id:
"xxxxxxxxxxxxxx", type "click", timestamp: xxxxxxxxxx....In the adobe
debugger I'm seeing the same thing (but part of a longer string). So the
click is being sent back. I'm not seeing an "actions" section. I'm not
seeing the "click" notification for any other link, just the links I've
marked.I'm not seeing any of the reserved characters in my selectors, so
I don't think that's the issues either. I've gone through the snippet
f...
I've added two links using VEC, I'd like to be able to track if either
link was tracked as part of my test (main reason for the test is to see
if we can get more clicks on this link). So I've added the links in VEC
and then in "Goals & Settings" I've set a conversion metric to "clicked
on an element" and then I selected the two links. Problem is I'm not
seeing the link clicks being recorded. I'm seeing page loads, but not
link clicks, in the Experience Cloud Debugger, I'm seeing something fire
w...
We are trying to use the form composer to create an A/B test that adds a
link to the end of a div on every landing page. I can use the visual
composer to add it to a given page, but this needs to be added to
multiple pages, so I'm thinking it needs to be done via a form. I've
added an mbox via DTM around the given element, but when I try to add
the link it messes up the CSS (or completely replaces the element I'm
matching in DTM). Any ideas on a better way to do this?
