We need to pull an unlimited number of rows using the Reporting API but to do so we have to set the source to data warehouse.  But when using data warehouse, you cannot retrieve the current day's data.  We would like to see the ability to retrieve unlimited rows of data that also include data from t...

I also miss being able to set s.visitorID in the interface for rules and have to use custom code.  In Launch, I only see it in the global variables area, which is not picked up on a direct call rule.

I also need to change to development and staging libraries in IE/Edge (I know, I'd rather just stay in Chrome too, but that is not an option).

Here is what I did, and hopefully it will work for you.  I created a new data element and set the type to custom script.  In the editor I added the getPreviousValue() and split() plugin code and then called getPreviousValue() with the current page name, returning the return value.  I use this data e...

We need the ability to create an alert at the dimension level, which we were able to do with the old "top 1000 items" functionality in the legacy alerts.  The alert should fire if any single item in a dimension reached a certain threshold. 

We run an ETL process with a scheduled Data Warehouse report as input.  When the format of this report changes between CSV and ZIP from one month to the next, it breaks our ETL process.  I would like to see an option to choose the format of the Data Warehouse report so that it is consistent every ti...

Hi Pankaj!The selector that I was using was just "[digitaldata-feature]".  Adding the option didn't work, but it did give me some ideas to try.  I had the attribute added to several different types of fields, so I broke up my one rule into separate rules using the different elements (a and input), b...

I have an application where I want to track the selection of an item in a dropdown.  I've asked the dev team to add a custom data attribute to each of the <option> tags.  Here is an example of one:<option digitaldata-feature="filter" value="Other"> Other</option>I have an EBR set up to look for the ...

Ah that is good to know.  In my particular situation, the image request is sent from a container app on an iOS device.  I wonder if the switch to POST happens the same on mobile?  I'll have to check it out!

I'm trying to understand why AppMeasurement places list variables high up in the image request.  In s_code, list variables were included near the bottom so that if the list variables became very long it was less likely to truncate other variables in the image request.  This is not true in AppMeasure...