More In-depth Program Reporting

This feedback was shared by Marco Tannert, at Mobile.de.

- Ideally I don't touch the project structure as is, as I don't understand what impact it would have to change it.

- What I would like to achieve:

- structure all experiments on team basis so in reports we can understand data on overall and team level

- analyse budget use (impressions) per team

- analyse runtime average / traffic / users per team

- understand which experiments are outliers in the stats

Additional Ideas from Justin Vos, Customer Success Manager:

• Make the project level filter in the impressions dashboard the names of the projects, rather than IDs.

• Give the option to select multiple projects.

• Show the total # of impressions consumed when filtering on a project.

• Show a table of # impressions consumed by project, sorted by most to least, including % of the total impressions bundle.

• REST API endpoint to retrieve runtime/traffic of experiments, to generate averages?

• Stretch the "teams" functionality from just permissions to experiment ownership.