For team work, it is essential that all team members have a basic set of
"official" and approven segments at their disposal.If changes need to be
made to a basic segment, all segments that use it should also benefit
from those changes directly!
Beware. Serialization applies *forever* essentially. So if you set an
event, serialised to a user ID, then it will only be counted once *ever*
for that User ID. It doesn't cause them to be only counted 'once per
visit' as you've stated here. It would be better to use the 'Once per
visit' option for the event rather than Serialization, for this specific
use-case I think.
alim92960278That sounds working as expected to me. As mentioned
response tokens would be delivered on the mboxes where Target activity
is delivered.In the case of redirect activities, the activity is
actually delivered on the first page and not the page where the visitor
is redirected to. Hope that helps. You may need to use 'preserve log'
option in browser's developer tool to view the response tokens on the
target call of first page. Hope that helps.
Sorry forgot to add.......but yes - in a world of cohort analysis,
instant segmentation on millions of rows and all the other impressive
things Adobe has - it seems crazy that we are limited on the email
We have an app that is tracked like a website (not a native app). When
debugging on my PC (local GIT repository/Ionic) I've noticed a lot of
extraneous server calls when navigating from screen to screen.Here you
can see that it's sending a server call for a link click:I believe it's
tracking the navigation arrows:How can I stop it from
tracking this click?Ali