Marking as a duplicate of Possibility to manually reorder rows in a Workspace Freeform Table - please show your support there!

Hi Andrew, that's an awesome thread that goes into pretty solid detail on the issues you're experiencing!Do you feel like these two topics are related closely enough for them to be considered duplicates so we can focus the conversation in this thread, or do you feel like the two topics are different...

Yeah, see the 'Breakdown reports' section on this page: analytics-2.0-apis/reporting-guide.md at master · AdobeDocs/analytics-2.0-apis · GitHub There's also using multiple breakdowns here: analytics-2.0-apis/reporting-multiple-breakdowns.md at master · AdobeDocs/analytics-2.0-apis · GitHub In worksp...

The time series example located here: analytics-2.0-apis/reporting-guide.md at master · AdobeDocs/analytics-2.0-apis · GitHub Replacing "dimension":"variables/daterangeday" with "dimension":"variables/daterangeminute" should do the trick.

I'll let others weigh in here, but with the new features Adobe Analytics continually gets, omitting props altogether becomes more and more enticing. You don't need to worry about having to explain the differences between props and eVars to colleagues - they're all just custom variables (eVars). Path...

This would be pretty tough to get within the Analytics UI, but I could see it reasonably working within Report Builder. It would require some implementation changes, though.First, you'd want to implement an eVar that is populated with publish date. You could also create a classification of publish d...

Did you hear back from Customer Care on this one? I would agree that they would be the ideal channel to get this resolved.

Data Warehouse doesn't allow daily scheduling if the data range is too wide. I think(?) anything longer than 2 weeks won't allow daily scheduling.Try shortening your date range then scheduling it for daily delivery. Let me know if that doesn't work for you.

Yes, you can match up offline and online data using transactionID​. Basically how it works is that you'll want to define transactionID on your site where you want the offline/online data to match up. Then you'll want to use the same transactionID in your data sources upload for that user. When an on...

Hi Mihai, is this for the API, Workspace, something else?