Data Validation

After initial setup, your team enters the data validation stage. This is an opportunity to review the data most relevant to your organization, confirm that it looks correct, and understand how Antenna derives each metric. The Antenna team is available throughout this process to answer questions, investigate discrepancies, and work through the data with you.

Metric traceability

Antenna aggregates activity from your connected tools into top-level metrics and charts. Metric traceability keeps these summaries connected to their supporting records, so you can see the activity behind any metric and understand how its value is derived.

Begin with the charts that are most relevant to your organization. Review the overall trends and values, then select any chart element—such as a bar, a point, or a headline number—to open its detail view.

The detail view connects the aggregate result shown in a chart to the records used to calculate it. Depending on the metric, those records may include pull requests, deployments, contributors, dates, and other values from your connected tools. For derived metrics such as ROI and AI Developer Equivalents, the detail view also shows the equation used to calculate them, so you can follow a result from the headline number down to the underlying activity and assumptions.

As you review these records, compare them with the activity you expect to see. This helps confirm that a metric accurately reflects your organization’s work and, when it does not, shows you where to investigate further.

Settings to review

When a metric doesn’t look the way you expect, the cause is usually one of a few settings. Start with the areas below, which can often resolve some of the most common questions teams have during validation.

Check integrations

Confirm that Antenna includes activity from each Git provider, project tracker, and AI tool you expect. If activity is missing, check the source’s last sync time in Settings > Sources.

Review deployments

Deployment metrics depend on the deployment method set for each repository. Go to Settings > Repositories and review every repository alongside its configured method. Each one shows the last deployed time, so you can confirm that recent activity matches what you expect. If it doesn’t, select the repository and choose a different method from the ones detected in your Git provider.

You can also turn deployment tracking on or off per repository, which is useful for repositories that run CI but never deploy to production.

Confirm account mapping

Antenna links accounts across Git, project trackers, and AI tools into a single contributor profile. Accounts that cannot be matched automatically may leave a contributor’s activity split across profiles or unattributed.

Go to Settings > Identities and review two things:

• Duplicate identities. A contributor’s accounts are sometimes split across two or more identities that should be a single person. Merge these identities so that each contributor’s activity is represented in one profile.
• Unmapped accounts. New accounts discovered in a data source may not always be matched to an existing identity. Review the Accounts tab and map any unresolved accounts to the right contributor so their activity is attributed.

Additional resources

If you have further questions about your data, the following resources are available:

• Search this documentation for the metric or setting to confirm how it’s defined and calculated.
• Use the Questions or Issues button in the relevant detail view to share the data point with the Antenna team.
• Contact support@antenna.dev with the chart, data, or metric in question.