The new experience platform debugger is much worse than the old
experience cloud debugger for Analytics debugging. It needs to be
much-improved before it will be useful.1. The top half of the output is
all information that is not useful for day-to-day debugging/testing. The
key information, like Page Name, Link Name, Events, eVars and Props are
all below the fold, requiring the user to scroll to see anything
useful.2. Unless you scroll all the way to the bottom and use the bottom
scroll bar, it ...
@jkm-disco I've now just added my support to the 'idea' for logging of
these user deletions. In a large organisation like ours, with multiple
admins of the various Adobe tools in different parts of the business, we
need to be able to identify and retrain (or remove) admin users who do
not follow the correct process, or owners of 'rogue' integrations that
are not operating correctly. If you agree this logging is needed, please
add your vote :
I absolutely agree with @Prasanna_R .We've had issues with active users'
Experience Cloud IDs being mysteriously deleted (their linked Analytics
accounts remain untouched, causing more confusion). We need log files
within Experience Cloud Admin that show us the 'friendly' user names
(not just Adobe IDs) of the deleted users, together with the friendly
usernames and/or Adobe IDs for the person or connector that did the
deletion.Without this we can't do proper audits or take action against
For people using appMeasurement, the updated getVisitNum plugin code is
currently (Jan 2021) available here :
Hi @eham06 I'm trying to find the same info
Did you get a useful answer in the end?
I'm trying to find out whether the AMCV cookie can be used to identify
unique sessions - specifically so we can sessions between Adobe and a
3rd party tool (we can pass the cookie ID through to it). I know the
MCAAMB part of the cookie is the encrypted Audience Manager 'blob' but
I'm not clear whether it is consistent across a session and if it then
changes from one session to another. All the other elements of the AMCV
cookie appear to be static across sessions for the same visitor on the
Can anyone confirm what the 'MCIDTS' part of the AMCV cookie does? Is it
a counter for session number? - I saw that it incremented by one between
sessions, whilst the rest of the AMCV cookie stayed unchanged. I just
can't find any documentation about it anywhere.
@Brandon_George_ So the first point above has been 'on the backlog'
since 2018? Please can you chivvy the developers up, to get some kind of
status log added so we can see whether scheduled projects are actually
running as expected.It wastes everyone's time when I have to raise a
ticket with ClientCare, just to find out if the projects are being
delivered normally again, after a processing issue has affected them.
Hi @jkm-disco Unfortunately we're not able to identify the admin who is
deleting users (large organisation & logs don't show such activity) -
Adobe ClientCare agree it's an issue and suggested I raise this 'idea'
specifically because they couldn't help us to identify the culprit. It
might not even be a 'real' person but could be the result of some bug
deep in adobe admin; It's only happened to 3 users so far and we have
very few admins able to delete users, and no reason at all that they
It should not be possible to delete an Experience Cloud login that is
linked to an analytics login, without FIRST deleting the Analytics
login. That would prevent the situation we currently have where users'
Experience Cloud logins have been deleted - presumably by an admin
elsewhere in the business - when they still require Analytics access.
The user then sees an error when they try to login, telling them their
account is no longer linked to an EC login, and we have to re-add that
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.