Yea, but I doubt the average user would be okay with a million popups for every bit of blocked traffic. Most major sites use multiple tracking mechanisms where a user would get a list of blocked tracking every time they navigated to a new page. If this is something you suspect will be an issue movin...

Ah, yea, it sounds like there isn't much you can do to get around this. Do many of your users actually use this blocking list? The only possible ways I can think of to get around this would be to either have Adobe modify their tracking servers (and subsequently the Launch code)--not very likely, or,...

@Andrey_Osadchuk, several times I've mentioned permission-related bugs/issues, they claim is was designed that way.... do you get similar responses?

@pramseycom , good find. Sounds like a clever blocking list. Luckily, you can actually create whatever CNAME records you want, as long as they resolve to Adobe's host. Maybe just come up with an uncommon naming convention and distinguish between secure/non-secure protocol.

This seems to be an oversight on Adobe's part since so many other solution variables are included.

If the issue is an Adobe-blacklist you should look into first-party tracking--unless your IP is also on a blacklist.Also, if it is blocking Launch/DTM code, you can host your own versions instead of using Akamai.

This sounds like a stale login cookie.You should try having the user clear their Adobe-set cookies and login from scratch. This often happens if significant changes in permissions have happened to the account or if they haven't used AA for a long time without signing in.

The point of the question is that Ad parameters are not showing up in the section you have highlighted with the rest of the solution dimensions and events.

Within Analytics, there are ways to configure sensitive data through the Admin > Data Governance section. Some solution dimensions don't appear within this section. In particular, I'm not finding any of the Ad Parameters (e.g. a.media.ad.creative which is ultimately reported through "Creative ID"). ...

Is there any documentation which actually mentions which Lifecycle metrics are enabled in Workspace and which ones need to be manually stored from context data?