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

# CI Visibility 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 Visibility](https://docs.datadoghq.com/continuous_integration/pipelines.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).

## 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/).

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

- [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)