Thanks @Jennifer_Dungan Have someone that wants to use Azure Blob and will try to dissuade because of that uncertaintyWas unable to find notice that they have an end date, but should assume that someday they will, like SFTP Thanks!

For the listed destination types under "Legacy", does it make sense to use these in 2024? Are they to be deprecated as a Data Feeds destination?  

Marking the above as the correct reply for those that DO want to preserve paramsEither send the entire URL into a var on every HIT, or only the querystring In my case I want to make sure that no params are preserved at-rest so we do not do the above, though it is the right solution

Jen. I just confirmed with support that they use default setting per-RSID which strips paramsI asked about referrer (r) and it too is strippedIt can be changed to keep parameters at-rest if you request The context in their response that it was a storage size issue This is an optimal outcome for me, ...

I double checked appMeasurement extension and we do not set pageURL in Custom Code or under the "Additional Settings" area of "Global Variables" I did find this snippet from a related thread with support last year, which is why I assumed that the stripping of params for use in DW was normal "Query s...

The (g) dimension is not altered and I can see that it includes paramsWhen extracting from Data Warehouse (Page URL) I do find that they are all without params, as expected. I do recall, but can't find DW documentation that says they are stripped of params for DW Now, at some point parameters are ne...

In Data Warehouse requests the pageURL dimension contains the truncated, non-parameterized version In Data Feeds is the original pageURL available in its parameterized form?The same question applies to referrers. Is the parameterized version of the referrer available?

So, the answer is yes This type of solution requires merchandising evars. I was hoping not to involve the product string, let alone merch vars Having set these as using the product syntax above and numeric events (I decided to allow duplicates in the list, they still sum), I was able to get predict...

Yes. This worked to individuate the items in the list, ignoring the serialization applied with the index # of the item. I definitely learned a trick here Unfortunately, the events didn't sum. So, where there were duplicates, we get a sum of 1 for the events sent along with the hit These items from t...

Thanks @Jennifer_Dungan Missing from my table above is the case where a category/id can be duplicated in the listSince List Vars dedupe, I wouldn't get an accurate count in that case I pushed in some sample data with classifications as illustrated and it worked as expected, except I had fewer unique...