Hey Eric9876543214444554,You are correct, when using Auto-Target and
Auto personalization it is using Target as the data source, and will not
make it into analytics. One suggestion is to use the target code to
create an analytics call in a variable, however, it won't work as an
Analytics as a data ...
If you are using DTM ensure that _satellite is firing in the
section of the page.Also, if this was an activity created when using
mbox.js, it may need to be updated to work with at.js, as per: Migrate
to at.js from mbox.js Append the URL with mboxDebug=console and confirm
that all AT actions are re...
Hey bkmills1,The best way to go about this is to use the Global Auto
Create with at.js. As for the form based composer auto create is not
essential in this case.However, if you are still experiencing flicker
with at.js and auto create global mbox, then try disabling the mbox on
the page by using mbo...
Hey Brion,In general at.js is better suited at reducing flicker on the
page as per: How at.js Manages Flicker Having said that, if you are
creating VEC activities, you must have Global MBOX Autocreate enabled in
at.js to ensure content is delivered correctly to the page. In general
we do not suggest...