As others have shown, it is possible, but instead of using multiple conditions, its easier just to create an exclusion segment on hit level and using "equals any of" as the match condition, so you can list values that are excluded, instead of creating each of them as a separate condition. This also ...

There are plenty of quite well made plugins for scroll tracking on the GA community, for example this one, which is a jQuery plugin: GitHub - robflaherty/scroll-depth: Google Analytics plugin to track visitor scroll depth You can easily fork the code and adjust so it uses Web SDK instead, e.g. direc...

There is nothing illegal about using cookies per say, but there needs to be a justification for it. This is of course also down to local and per company interpretations, which I will not go into. As you said this is really easy to do with AppMeasurement, as you can do a scenario like you did, or sim...

Hey!As you stated in your other post, Adobe does not provide this capability. While there are options to copy between environments and access control, there is no automation integration directly for e.g. QA and no version control. I know that this has been done (I was not part of this though) and pr...

A major difference with Web SDK and the old library is that Web SDK is built around using only ECID. There are likely other ways to do this, perhaps even using Data Prep, but the way I see it there are no direct ways to avoid using ECID unlike before. I am working with cases who do what you're aimin...

In that case the only option is to use an external piece of script that rewrites the cookie duration after Target has run. These solutions work, but need special care as Target overrides the duration whenever it runs. 

Absolutely so, the override is to change the configuration ID used, just as you said. This solution would be my suggestion as well and we have done this, but for different reasons (swap data stream based on consent and security control to limit loading of external content for some pages). There are ...

Let me get started by saying that it doesn't differ too much for FID or ECID as such, it's more in what you tie into them. Instead of using different ID's, one could possibly create a different ruleset in Tags, or a custom method of running only limited set or rules, variables and events for those t...

The default should indeed be 2 years, I think there has been a small slipup defining 2 weeks for lifetime. As the document describes, there is no way to change this without e.g. a separate script that adjusts the lifetime (note that Target script will restore it to 2 years when run).  I'm curious: I...

Are you using the unified call or the new beta feature to separate Target call, named "Guided events"? Since Target with at.js runs independent of Analytics, it actually seems to have less delay than WebSDK and it's default model of a single call. This varies somewhat, but im general separate calls ...