Hi @Jamie_Re ,I somehow missed your question, sorry about that. When
analyzing Target data in Analytics you need to use the "Same touch"
attribution model because this model is used in Target reporting as well
-> so when trying to compare data Target vs. Analytics you need to
always set "Same touch" attribution model in
Let me know if this helps.
If you have two activities with the same priority running on the
global-mbox, one is changing the global navigation and the other one is
changing the footer for example, both changes will be applied and
displayed to users.If both activities would change the global navigation
then only the latest activated activity changes will be displayed to
This is the link for the SPA documentation:
I think that if the Analytics call is starting before Target call
finishes might generate the problem you're seeing.
Thank you everyone for joining today's Coffee Break, it was great to be
able to answer your questions! Please mark your calendars to join us on
January 19th for our next Target Coffee Break and first Target Coffee
Break of the new year 🙂Happy Holidays!
Usually you could create div-based mboxes when using the Form-based
Composer for authoring your Target activities so that you know exactly
what part of the page you are modifying. If you want to A/B test
something that's side-wide (like global navigation) you can use the
"Page Delivery settings" to add a Template rule to match the URL or the
entire domain and apply the changes across.See the screenshot below:If
you have other activities that are running on other parts of the page
then those can ...
Hi @DillanGump ,You might want to check this troubleshooting guide to
see if it helps:
If there is no supplemental data ID in the Target call, confirm that the
VisitorAPI.js file is loaded before at.js. If there is no supplemental
data ID in the Analytics call, confirm that the Target call fires before
the Analytics call.
Hi Brian, Thanks for the questions! 1. Can you please elaborate more on
the "60 seconds limitation" - how does it manifest and why it's a
struggle?2. This is something that I need to check with Analytics team
and get back to you3. If you are using the A4T panel in Analysis
Workspace, then the attribution model should be set by default to
"Same-touch". Otherwise, if you are creating a new freeform panel then
you need to modify it.4. I'll log this as a enhancement request 🙂
Thanks so much for this feedback. In order to ensure that it is captured
effectively, please feel free to share this as an "Idea" in the
Community. You can do this by clicking here: