Yep, if you need attribution, then you will need to use eVar...However, there are different approaches you can take...   First, if you have finite number of items (i.e. one or two values), you don't need to use a "list". You can actually send these as a normal dimension, and use classifications to s...

Report Builder can use Segments, but they apply to the entire request...    I'm still more familiar with the older Report Builder, but when you start to build your request, you can choose a segment here:     Filters are different... the best way I can describe this, is that in order to use a segmen...

While you can do a lot, there are some things that can't be done (even when they look like they should be able to work).   Too bad, but if you are using a global suite with Web and App, you might need to do some work on the website to have all the data available for all platforms in your custom dime...

Hmmm trying to override a core app context variable may not be possible...  or the value that you are passing is in an unacceptable format so Adobe is ignoring it outright.   I am checking our apps using AEP Assurance... the Operating System isn't actually shown in the Post Processed data (there is ...

I agree with @bjoern__koth... if you know the data you are going to collect is always going to fit into 100 characters max, then a List Prop is fine...   Otherwise, the only way to ensure that you don't lose data is to use a list. I am a big supporter of the "namespace" or "value set" method to incr...

OK, but then wouldn't asking for more control on this existing function, with more options be better than creating a whole new function? One that will leave people confused over which "grand total" they should use?

No worries @LukasSi2; this happens more often than you would think... I just want to be sure the right people see your idea, cause if it only lives here it's less likely to have the correct team look at it (I am not sure if the Adobe folks actually share when an idea is posted in the wrong spot... )...

OK, that's good to know.. yes, if this is new, then 1 month should be fine....     One suggestion I have seen when it comes to Classification Rules, is to set up one "catchall" at the end, and set that value to something like "none" or "unknown"...   That way you can see what hasn't been processed a...

Doesn't this already exist?     Changing the behaviour from "Standard Column Sum" to "Grand Total Column Sum"?

Hello,    This is the Adobe Analytics forum, you should re-post this in the Creative Cloud Forum (specifically the Lightbox Classic category) here: https://community.adobe.com/t5/lightroom-classic/ct-p/ct-lightroom-classic?page=1&sort=latest_replies&lang=all&tabid=all