Hi, I added Target 1.0.1 was via DTM install wizard, but with at.js
added manually via the code section of Target (because DTM doesn't
automatically implement at.js)Since updating from 0.9.6 to 1.0.1 I can
see warning messages but can't see any target tracking in the Adobe
Cloud Console.Plus there are some console message that suggest we need
to make changes in the setting (see below)What does this message mean?
I am setting up my first campaign(s) in Target (formerly used Target
Classic) and I am having some trouble setting goal metrics. I have a
50/50 test using a global mbox, and my goal needs to be when a specific
page is visited. the issue I have is that my URL's are not fixed, for
I was trying to set a rule saying Conver...
Hi. I am having trouble understanding how the conversion metrics work
using the global mbox. I would like to create a goal which is achieved
when the visitor sees the global mbox on a specific page (or simply
views a specific page). The issue I have is, my urls are never the same,
I need to able to say eit...
Thanks so much Parit! So it's all working ok?! Wonderful! One last
question, on other sites I have 'on-page' legacy mboxes (see attached).
Can I still use these with at.js? I know I can with mbox.js (fired
through DTM), but I think I recall reading somewhere that at.js isn't
compatible with 'mboxcreate'...?Will send you my Target log in....
Hi, can anyone offer advice on using at.js vs. mbox.js when upgrading to
Target Premium? I understand at.js is necessary for single page apps,
but there is only the option to use mbox.js when using 'Managed by
Adobe'. If I download the at.js file and implement through the custom
code editor it doesn't seem to work (new mbox.js does btw). Any help
would be greatly appreciated! ThanksMatt