--- schema_version: "1" id: b55869b562104bd9a0d3a840723a24d825c73f3dd5f860346b832fc9b76cb513 title: Enablement Measures Examples collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/enablement_measures_examples.md canonical_url: https://help.salesforce.com/s/articleView?id=sales.enablement_measures_examples.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: fd5a638642a8a3f4a30e5cf3c51f502ec682c062961be6cafbc3586699a0aed9 description: Find inspiration for creating Enablement measures that track job-related activity for your Enablement program outcomes and milestones. For some examples, a Salesforce admin must set up other features or create custom objects, fields, or picklists. Some examples offer There can be multiple ways to track the same behavior or goal, so you can consider multiple options. To further refine the specific activity that a measure tracks, combine field filters from multiple examples products: - Sales Cloud - Sales Enablement release: "264" --- # Enablement Measures Examples Find inspiration for creating Enablement measures that track job-related activity for your Enablement program outcomes and milestones. For some examples, a Salesforce admin must set up other features or create custom objects, fields, or picklists. Some examples offer There can be multiple ways to track the same behavior or goal, so you can consider multiple options. To further refine the specific activity that a measure tracks, combine field filters from multiple examples ## Customer Service Examples
What You’re Measuring Object Who, When, How Field Filters Required User Action
Number of resolved cases. Case
  • Display Field: Subject
  • User Field: Created By
  • Date Field: Date/Time Closed
  • Calculation Method: Count
 Field Filter: Status Equals Closed The user listed in the Created By field must create a case and set the Status field to Closed. The user is credited for meeting this goal on the date and time recorded in the Date/Time Closed field.
## Einstein Conversation Insights (ECI) Examples ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-enablement-264-0-0-production-enus/4a7278f8-cbf0-413e-95e6-6a1aa646877b/images/icon_important.png) Important ECI isn’t supported in Developer Edition, isn’t supported in Partner Enablement programs in Experience Cloud sites, and isn’t included with Enablement Lite. However, if you’re trying Enablement Lite and your company already uses ECI, you can still use ECI measures with Enablement Lite programs.
What You’re Measuring Object Who, When, How Field Filters Required User Action

Number of customer calls with keywords mentioned.

This measure requires a Salesforce admin to set up ECI Call Insights and to create custom call insights for any keywords you want to follow.

For example, add key phrases from your company call scripts or sales playbooks, or the names of products that you want sales reps to drive sales for.

 Unified Voice Call
  • Related Object: Unified Voice Call Participant
  • Unified Voice Call Participant Field Filters:
    • Filter Logic: All conditions met (AND)
    • Field Filter 1: Person ID Equals User whose work is measured
    • Field Filter 2: Participant Type Equals From
  • Related Object: Unified Activity Insight
  • Unified Activity Insight Field Filters:
    • Filter Logic: All conditions met (AND)
    • Field Filter 1: Insight Type Equals the name of the ECI call insight that includes keywords that you want to track.
    • Field Filter 2: Aggregated Keyword Occurrences Greater or Equal to the number of times you require users to use keywords on each call.
  • Display Field: Unified Voice Call ID
  • User Field: Voice Call (Voice Call ID).Owner ID
  • Date Field: Activity Date and Time
  • Calculation Method: Count
 The call owner must say the keywords identified in the ECI call insight the total number of times that you specified in the field filter. Both calls that the call owner creates and calls that the call owner participates in qualify for this measure. The call owner is credited for meeting this goal on the date and time recorded in the Activity Date and Time field.
## Opportunity Examples
What you’re measuring Object Who, When, How Field Filters Required User Action

Number of deals in pipeline

This measure requires Salesforce admins to set up and customize opportunity contact roles.

 Opportunity
  • Display Field: Name
  • User Field: Created By or Owner ID
  • Date Field: Created Date, Due Date, or the date field that represents when an opportunity is considered in the pipeline
  • Calculation Method: Count

Field Filters:

  • Stage Equals the Stage field value or values that represent your pipeline.
  • If counting the number of deals for a specific product line, add a related object for Opportunity Product and set a filter for Opportunity Product Name Equals the product field value that you want to count deals for.

The opportunity owner or the user listed in the Created By field must set the Stage field to one of the values that you specified in the field filter. The user is credited for meeting this goal on the created date, due date, or the date field that represents when an opportunity is considered in the pipeline.

If counting the number of deals for a specific product line, the user must also set the Opportunity Product Name field to the value that you specified in the field filter.
Number of deals qualified for a target persona. Opportunity
  • Display Field: Name
  • User Field: Created By or Owner ID
  • Date Field: Close Date
  • Calculation Method: Count
  • Opportunity Field Filter: Stage Equals Qualification
  • Related Object: Opportunity Contact Role
  • Opportunity Contact Role Field Filter: Role Equals the value for the persona that you want to target.
 The opportunity owner must set the Stage field to Qualification and the Role field to the value that you indicated in the field filter. The user is credited for meeting this goal on the date they provide in the Close Date field.
Number of deals that meet a minimum deal size. Opportunity
  • Display Field: Name
  • User Field: Owner ID
  • Date Field: Close Date
  • Calculation Method: Count
  • Filter Logic: All conditions are met (AND)
  • Field Filter 1: Stage Equals Closed Won
  • Field Filter 2: Amount Greater or Equal to the minimum amount you want each deal to meet.
 The opportunity owner must set the Stage field to Closed Won and the Amount field must meet the minimum requirement that you set in the field filter. The user is credited for meeting this goal on the date they provide in the Close Date field.
Number of deals won for a specific product. Opportunity
  • Display Field: Name
  • User Field: Owner ID
  • Date Field: Close Date
  • Calculation Method: Count
  • Opportunity Field Filter: Stage Equals Closed Won
  • Related Object: Opportunity Product
  • Opportunity Product Field Filter: Opportunity Product Name Equals the name of the product that you want to count deals for.
 The opportunity owner must set the Stage field to Closed Won and the Opportunity Product Name field to the product name you set in the field filters. The user is credited for meeting this goal on the date they provide in the Close Date field.

Number of deals won using a company playbook.

This measure requires Salesforce admins to add a customization to track whether your company playbook was used to win a deal.

For example, Salesforce admins can add the custom field Playbook Used.

 Opportunity
  • Display Field: Name
  • User Field: Owner ID
  • Date Field: Close Date
  • Calculation Method: Count
  • Filter Logic: All conditions are met (AND)
  • Field Filter 1: Stage Equals Closed Won
  • Field Filter 2: Playbook Used Equals Yes (or your equivalent customization)
 The opportunity owner must set the Stage field to Closed Won and the Playbook Used field to Yes (or your equivalent customization). The user is credited for meeting this goal on the close date.

Number of deals won with more than two products.

This measure requires Salesforce admins to add a customization to track the number of products that are included on a deal.

For example, Salesforce admins can add the custom field Product Count.

 Opportunity
  • Display Field: Name
  • User Field: Owner ID
  • Date Field: Close Date
  • Calculation Method: Count
  • Filter Logic: All conditions are met (AND)
  • Field Filter 1: Stage Equals Closed Won
  • Field Filter 2: Product Count Greater or 2 (or your equivalent customization)
 The opportunity owner must set the Stage field to Closed Won and the Playbook Used field to Yes (or your equivalent customization). The user is credited for meeting this goal on the close date.
Total amount of revenue in pipeline. Opportunity
  • Display Field: Name
  • User Field: Owner ID
  • Date Field: Created Date, Due Date, or the Date field that represents when an opportunity is considered in the pipeline
  • Calculation Method: Sum
  • Field for Calculation: Amount Field

Field Filters:

  • Stage equals the Stage field value or values that represent your pipeline.
  • If counting the number of deals for a specific product line, add a related object for Opportunity Product and a filter for Opportunity Product Name Equals the product field value that you want to count deals for.

The opportunity owner or user listed in the Created By field must set the Stage field to one of the values that you specified in the field filter. The user is credited for adding the monetary amount in the Amount field to their pipeline on the created date, due date, or the date field that represents when an opportunity is considered in the pipeline.

If counting the number of deals for a specific product line, the user must also set the Opportunity Product Name field to the value that you specified in the field filter.

Total amount of upsells generated.

This measure requires your Salesforce admin to add a customization to track deal expansions.

For example, Salesforce admins can create the custom picklist value Expansion for the Type field.

 Opportunity
  • Display Field: Name
  • User Field: Owner ID
  • Date Field: Close Date
  • Calculation Method: Sum
  • Field for Calculation: Amount
  • Filter Logic: Custom logic is met (OR/AND)
  • Custom Logic: 1 AND (2 or 3)
  • Field Filter 1: Stage Equals Closed Won
  • Field Filter 2: Type Equals Existing Business
  • Field Filter 3: Type Equals Expansion
 The user opportunity owner must set the Stage field to Closed Won, and the Type field to either Existing Business or Expansion. The user gets credit for meeting this goal on the close date.
## Task and Event Examples
What you’re measuring Object Who, When, How Field Filters Required User Action

Number of discovery calls booked.

This measure requires Salesforce admins to add a customization for tracking the status of discovery calls.

For example, on Task or Event, Salesforce admins can add the custom picklist value Discovery Call to the Type field, set the Field-Level Security for Type to Edit Access, and add Type to the object page layout.

 Task
  • Display Field: Subject
  • User Field: Created By or Assigned To
  • Date Field: Created Date or Due Date
  • Calculation Method: Count
  • Filter Logic: All conditions are met (AND)
  • Field Filter 1: Type Equals Discovery Call (or your equivalent customization)
  • Field Filter 2: Status Equals Completed
 The user listed in the Created By or Assigned To field must complete a task in which the Type field is set to Discovery Call (or your equivalent customization). The user is credited for meeting this goal on the created date or due date.
Event
  • Display Field: Subject
  • User Field: Created By or Assigned To
  • Date Field: Created Date
  • Calculation Method: Count
 Type Equals Discovery Call (or your equivalent customization) The user listed in the Created By or Assigned To field must conduct an event in which the Type field is set to Discovery Call (or your equivalent customization). The user is credited for meeting this goal on the created date.

Number of meetings with a target customer persona.

This measure requires Salesforce admins to add a customization to track the target persona who participated in the meeting. It also requires Salesforce admins to set the Field-Level Security for the Type to field to Edit Access, and add Type to the object page layout.

 Event
  • Display Field: Subject
  • User Field: Assigned To
  • Date Field: End Date
  • Calculation Method: Count
  • Filter Logic: All conditions are met (AND)
  • Field Filter 1: Type Equals Meeting
  • Field Filter 2: Add a filter for the custom field your company uses to track the participating persona.
 The user listed in the Created By or Assigned To field must conduct an event in which they set the Type field to Meeting and provides a value for the field used to track the participating persona. The user is credited for meeting this goal by the event end date.

Number of completed demos.

This measure requires Salesforce admins to add a customization for tracking demos.

For example, on Task or Event, Salesforce admins can add the custom picklist value Demo to the Type field, set the Field-Level Security for Type to Edit Access, and add Type to the object page layout.

 Task
  • Display Field: Subject
  • User Field: Created By or Assigned To
  • Date Field: Created Date or Due Date
  • Calculation Method: Count
 Field Filter: Type Equals Demo (or your equivalent customization) The user listed in the Created By or Assigned To field must set the Type field to Demo (or your equivalent customization). The user is credited for meeting this goal on the created date or due date.
Event
  • Display Field: Subject
  • User Field: Created By or Assigned To
  • Date Field: Created Date
  • Calculation Method: Count
 Field Filter: Type Equals Demo (or your equivalent customization) The user listed in the Created By or Assigned To field must conduct an event in which the Type field is set to Demo (or your equivalent customization). The user is credited for meeting this goal on the created date.
#### See Also - [Considerations for Creating and Editing Measures](https://help.salesforce.com/s/articleView?id=sales.enablement_measures_considerations.htm&release=264.0.0&type=5 "Work with your business operations expert and other Enablement team members to carefully identify the objects and fields you want to use for tracking job-related activity. Before you start creating or editing measures, review how you can safely modify prebuilt measures or measures that are already used in published programs. See how you can preview measures, handle invalid measures, and create more elaborate measures using related and custom objects.") - [Guidelines for Creating Einstein Conversation Insights Measures for Conversation-Based Goals](https://help.salesforce.com/s/articleView?id=sales.enablement_measures_eci_guidelines.htm&release=264.0.0&type=5 "To add conversation-based goals to your Enablement programs using voice and video calls recorded with Einstein Conversation Insights (ECI), create a measure that uses ECI objects. Learn guidelines for building successful ECI measures, such as which parameters are required. Also, get ideas for incorporating ECI Call Insights into your programs, such as counting key phrases that call owners mention during their customer calls.") - [Set Field-Level Security for a Field on All Profiles](https://help.salesforce.com/s/articleView?id=platform.users_fields_fls.htm&language=en_US) - [Create Page Layouts](https://help.salesforce.com/s/articleView?id=platform.customize_layoutcreate.htm&language=en_US) - [_Trailhead_: Understand Custom and Standard Objects](https://trailhead.salesforce.com/content/learn/modules/data_modeling/objects_intro)