---
title: CI/CD Optimization Billing
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: Docs > Account Management > Billing > CI/CD Optimization Billing
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# CI/CD Optimization Billing

{% callout %}
# Important note for users on the following Datadog sites: app.ddog-gov.com, us2.ddog-gov.com

{% alert level="danger" %}
This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site.md). ({% placeholder "user-datadog-site-name" /%}).
{% /alert %}

{% /callout %}

## Overview{% #overview %}

This guide provides a non-exhaustive list of billing considerations for CI/CD Optimization, which includes [CI Visibility](https://docs.datadoghq.com/continuous_integration/pipelines.md) and [Test Optimization](https://docs.datadoghq.com/tests.md).

## Counting committers{% #counting-committers %}

A committer is an active Git contributor, identified by their Git author email address. For billing purposes, a committer is included if they make at least three commits in a given month.

## Billing for commits made by bots or actions performed in the GitHub UI{% #billing-for-commits-made-by-bots-or-actions-performed-in-the-github-ui %}

Commits made by verified bots or through actions performed directly in the GitHub UI are not billed by Datadog. These are automatically excluded from billing calculations. Only verified bots are excluded from billing.

## Excluding commits from specific people{% #excluding-commits-from-specific-people %}

Yes, you can exclude commits from specific people by using [exclusion filters](https://docs.datadoghq.com/continuous_integration/guides/ingestion_control.md).

## Billing enrichment{% #billing-enrichment %}

Billing enrichment correlates your billable-committer metrics with data from a [reference table](https://docs.datadoghq.com/reference_tables.md), using the committer's email address as the join key. This adds tags such as `vp_name` or `director_name` to your billing data, so you can break down billing data by organizational structure.

To set up billing enrichment:

1. Create a [reference table](https://docs.datadoghq.com/reference_tables.md) that contains a column with committer email addresses, along with any additional columns you want to expose as tags (such as `vp_name`).
1. In Datadog, go to [CI/CD Optimization > Billing & Committers](https://app.datadoghq.com/ci/settings/ci-cd/billing-committers).
1. Turn on Enrich billing metrics.
1. Select the Reference table to use.
1. Select the Email key column: the column in the reference table that contains the committer email address. Datadog uses this column to join billing data with the reference table.
1. Select the Enrichment columns: the columns from the reference table to expose as tags on billing metrics. Leave empty to include all columns.

After billing enrichment is configured, the additional tags from the reference table appear alongside your existing billable-committer metrics.

## Deduplicating committers across email addresses{% #deduplicating-committers-across-email-addresses %}

In some cases, a single developer's commits can be split across multiple Git author emails. For example, a developer might set a different email with `git config user.email` in different repositories. If more than one of those emails passes the three-commit billing threshold described above, each counts as a separate committer.

For repositories hosted on GitHub, Datadog can map each Git author email to the underlying GitHub user so that the developer is counted once, even when they push under different emails. This requires a Datadog [GitHub App](https://docs.datadoghq.com/integrations/github.md) installed on the affected repositories with the `Contents: Read` permission.

This mapping is available for GitHub repositories only. Repositories hosted on GitLab, Azure DevOps, or Bitbucket are not deduplicated.

If your committer count looks higher than expected for GitHub repositories, check that the Datadog GitHub App is installed on those repositories with the `Contents: Read` permission. You can review your installation from the [GitHub integration tile](https://app.datadoghq.com/integrations/github/).

## Counting test spans{% #counting-test-spans %}

In Test Optimization, every individual test run counts as a test span, except for the test spans that Test Optimization features generate. Test spans affect your bill only when your usage exceeds the test span allotment included for each committer in your plan.

### Test spans generated by Test Optimization features{% #test-spans-generated-by-test-optimization-features %}

Some Test Optimization features run or report tests on your behalf. The test spans that these features generate do not count as billable test spans:

- Retries from [Auto Test Retries](https://docs.datadoghq.com/tests/flaky_tests/auto_test_retries.md), [Early Flake Detection](https://docs.datadoghq.com/tests/flaky_tests/early_flake_detection.md), and the [Attempt to Fix](https://docs.datadoghq.com/tests/flaky_management.md#confirm-fixes-for-flaky-tests) remediation flow. The first execution of the test is billed, but the retries that the feature adds are not.
- Tests skipped by [Test Impact Analysis](https://docs.datadoghq.com/tests/test_impact_analysis.md).

These test spans are still ingested and indexed. You can search and analyze them in the [Test Optimization Explorer](https://docs.datadoghq.com/tests/explorer.md) like any other test span.

The following test spans are billed:

- Retries configured in your test framework.
- Tests that you skip in your code or test framework configuration.

These exceptions don't change how committers are counted.

## Further Reading{% #further-reading %}

Additional helpful documentation, links, and articles:

- [Learn about Pipeline Visibility](https://docs.datadoghq.com/continuous_integration/pipelines.md)
- [Learn about Ingestion Controls for CI Visibility](https://docs.datadoghq.com/continuous_integration/guides/ingestion_control.md)
- [Learn about Test Optimization](https://docs.datadoghq.com/tests.md)
