Exporting your Multitudes data

1. On the Multitudes App, go to Settings > Export Data.
2. Select the filters for the data you want to download
   
   • Date range
     Note: We recommend selecting full periods, for example 1 Jan - 30 Sept instead of partial periods like 1 Jan - 15 Oct. This will help to ensure the reporting is complete and the trends are more accurate.
   • Timescale (either ‘weekly’ or ‘monthly’)
   • Teams
   • Repositories
3. Request your export
4. Once your data export is ready we will email you - depending on the amount of data this may take a little while to arrive. Data exports should be available within 1 business day, if not please contact us.
5. Follow the link in the email to download your CSV file.  
   Note: Only the person who requested the export can download the CSV file from the app.
6. Your export will be stored for 30 days in case you need to revisit it and download it later. You can access your previous 30 days of exports in the Requests log at the bottom of the Export Data page.
   

Note: Anyone with Multitudes access can export data from the app.

All Multitudes time series metrics are included in your export.

Multitudes metrics not shown: Some Multitudes charts don't show here, because they're not time series data. The following metrics are not exported:

• Value Delivery: Feature versus Maintenance chart (from Linear, JIRA, or conventional commits data)
• Quality of Work: Number of pages
• Collaboration: Feedback Flows

MTTR and MTTA: In the Multitudes app, these numbers are grouped by service and escalation policy. In the export, we show one aggregate value over time per team.

For each metric, we export the data available in the app so you have the flexibility to analyze it as you need.

For example:

• For Change Lead Time metrics (incl Coding Time, Review Wait Time, Editing Time and Deploy Time) we export: p75; p75 (excl weekend hrs); median; and median (excl weekend hrs).
• For Merge Frequency, we export all PRs per person; all PRs total; collaborative PRs per person; and collaborative PRs total.

‍

Timezone: Multitudes data is displayed in your organization's time zone.

Deployment data source: If an organization has both the Deployments API AND GitHub Actions set up, this tool will prioritize the Deployments API data and show that over the GitHub Actions data.

Team data only: This export is designed to be used to report on team data, not individual data. 

Take action tools not included: The Multitudes app also has other functionality not shown in the data export – the insights, actions, facilitation guides, and custom targets are all excluded.

It’s likely that you’ll have a lot of data in your export!  The way that you share and analyze it is important, so we’ve created a tool to help you turn a csv of your engineering metrics into a format that's easier to read and share.

Our public Google Sheet template allows you to input a CSV of your data and get an output table showing how metrics have changed over time for different teams.

View the template

1. Make a copy of the Google Sheet template
2. Paste your raw data into "INPUT_csv data”.  Your CSV download from our app will be in the correct format already.
   If you are using a different CSV, check the template readme for details on setting up your data.
3. Review your metrics in the Output sheet
   Use the Select fields at the top of the sheet to filter between teams, normalising per people, and specific toggles for Flow of Work and Collaboration options.

The Output sheet includes:

• A link to read about each metric and why it’s measured in our Help Docs
• The unit of measurement
• A benchmark
• A sparkline reflecting the change over time
• Data is colour coded to show changes