The issue is almost guaranteed going to be in 1 of 3 places: Implementation, processing rules, or VISTA rules, the most likely being Processing Rules (as Andrey mentioned).Let us know if you're able to find it, and we can explore some further edge-case scenarios.

Not yet, but there's this idea thread currently open: Workspace to FTP

You'll want to use a JSON web token: analytics-1.4-apis/auth_service_account.md at master · AdobeDocs/analytics-1.4-apis · GitHub

With the month dimension, are you using the purple date one or orange dimension one? Do results change if you switch to the other?

I don't think this is possible.You can exclude certain positions using a custom attribution model, but not a specific channel. You can exclude certain hits using segmentation, but the same rules of attribution apply to the remaining hits.

Web Service Access lets you do things like authenticate with Adobe Launch or Power BI. All report access means that for the report suites that you have permissions to, you can access all the reports in them.Report suite permissions must be explicitly given. As Karandeep said, work with your manager ...

Archiving due to age and relevance. If this is still something that is desired while using the latest version of Analytics/Analysis Workspace, I'd highly recommend creating a new idea and linking this idea there. Thanks!

Archiving due to age and relevance. If this is still something that is desired while using the latest version of Analytics/Analysis Workspace, I'd highly recommend creating a new idea and linking this idea there. Thanks!

Rolling date ranges and hourly breakdowns should fulfill this use case.

Up until recently, you had two options:Don't set any timestamps anywhere, and let Adobe data collection servers take care of it for you. If Adobe sees any hits with timestamps, the hit is discarded. Almost all standard implementations use this method.You set the timestamps in every hit. If Adobe see...