--- title: "Building your own metrics" slug: "create-a-basic-metric" updated: 2026-10-12T12:48:27Z published: 2026-10-12T12:48:27Z canonical: "help.gong.io/create-a-basic-metric" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.gong.io/llms.txt > Use this file to discover all available pages before exploring further. # Create a basic metric > **Who can use this**: Business admin > > **Available on**: Gong Forecast > > **Ideal for**: RevOps > > **Required permissions:** Manage metrics A basic metric measures one field on a CRM object, such as total opportunity amount or a count of deals at a certain stage. Use this metric type when you want to measure one specific field directly. For calculations that combine multiple entities, see [Create a formula metric](https://portal.us.document360.io/2837c190-3ec8-4120-9116-6d427e774667/document/v1/view/03743d50-68d4-4666-adde-42b1fe95b1db). ## Before you begin For metrics based on CRM data, connect your CRM to Gong. New CRM fields may take a few hours to sync after import. ## Create a basic metric ### Step 1: Open the metric Navigate to Data Studio and open the metric. **To open the metric:** 1. From the left sidebar, click **Admin center**. 2. In the **Settings** tab, click **Metrics** on the **Data Studio** card. 3. Click **New metric** and select **Basic metric**. ### Step 2: Define the metric Choose the object and fields the metric measures, then set any conditions, grouping, or other options. **To configure a basic metric:** 1. Enter a name for the metric. 2. Under **Base object**, choose the object to measure, such as Deals, Accounts, Contacts, or Leads. 3. (Optional) Turn on **Enable history tracking** to make an eligible deal-based metric available in the **Custom trend** mode of a Trends widget and the **Custom changes** mode of a Changes widget. > [!NOTE] > Note: > > Every Opportunity field the metric uses must already have history tracking enabled in [Field Management](/v1/docs/track-history-for-opportunity-fields). 4. In **What's aggregated and how**, select the aggregation type and field to measure. > [!NOTE] > Note: > > To count distinct values instead of records, select **Count uniques**. This option is available only for reference fields, such as when counting unique accounts across deals. 5. (Optional) In **Apply conditions**, click **+ Add** and select: > [!NOTE] > Note: > > Related object fields are available at the bottom of the field list under **Related Objects**. Select the related object, then select its field. For example, a deal-based metric can use account fields, including custom account reference fields such as **Partner Account ID**. This lets you group opportunities by parent account owner or filter opportunity line items by the parent opportunity’s stage, close date, or owner. - **Single condition:** Add one filter using the base object or related object fields. - **Condition group:** Combine multiple conditions with **AND** or **OR** logic for more complex filtering. 6. (Optional) Turn on **Apply splits** to distribute the calculation across everyone involved in a deal. This requires Salesforce integration with the [Opportunity Split](/v1/docs/opportunity-teams-and-splits-faqs) object imported into Gong. 7. Under **Team member attribute**, select the CRM field that identifies the relevant team member, for example Owner. This controls who the metric is grouped by. You can also select a related object field, such as an account field for a deal-based metric. 8. When opportunity splits or teams are enabled and the base object is Deals, set **Show deals where team members are** in to include deals where the selected team member is on the opportunity team or appears in the selected team member field. 9. Under **Date attribute**, select the CRM field that defines the date for qualified deals or accounts. You can also select a related object field, such as an account field for a deal-based metric. 10. (Optional) Turn off **Apply external period filters** if the metric should ignore the dashboard's selection period. Use this when time doesn’t matter for the metric or when it should always use specific dates set in its conditions. 11. Under **Drilldown view**, choose the list view or deal board that opens when a team member clicks the metric value on a dashboard. The options shown depend on the base object. Widget settings can override this selection. > [!TIP] > Tip: > > Use condition groups when you want to measure a specific subset of deals or accounts — for example, won deals in a particular region or enterprise accounts above a certain threshold. Keeping conditions focused prevents a metric from including records that would skew the result. ### Step 3: Save the metric Review the metric in the Preview panel to validate your settings, then save it. **To save the metric:** 1. Check the **Preview** panel to confirm the metric calculates correctly for the selected team and period. 2. Click **Save**. The metric appears in your metrics list and is available to select when configuring dashboard widgets and Forecast boards. > [!NOTE] > Note: > > Any edits to metrics take effect immediately across all dashboards and Forecast boards that use it. Learn more about [managing your metrics](https://portal.us.document360.io/2837c190-3ec8-4120-9116-6d427e774667/document/v1/view/ebc9fa1a-a505-45eb-a6ad-f8b50d48dff0). ## Frequently asked questions ****What is the difference between a basic metric and a formula metric?**** A basic metric aggregates a single field on a CRM object, such as summing an amount field or counting records. A formula metric combines two or more existing metrics, targets, or forecast submissions using a mathematical expression, making it suitable for calculations like win rate or pipeline coverage. If your measurement requires multiple entities or a ratio, use a formula metric. ****Why can’t I turn on history tracking for my metric?**** History tracking is available only for eligible deal-based metrics. Every Opportunity field the metric uses must already have history tracking enabled and backfilled in Field Management. If a field isn’t tracked, enable history tracking for it first. A team member who manages the business entities in Gong, such as deal and forecast boards. [Find my Business admin](/v1/docs/find-your-technical-or-business-admin). Gong’s full Forecast package for next-level forecasting and revenue optimization. Access to features depends on your [company’s plan and your assigned seat](/v1/docs/plans-and-seats). A team member who manages and optimizes revenue-related workflows by managing business entities such as metrics, targets, and dashboards.