Skip to main content
Gainsight Inc.

Using Calculated Fields in Programs

Gainsight NXT
Gainsight helps innovative companies protect and nurture their most valuable asset - their customers - with the power of our award-winning platform. With our Customer Success Solution, you can gain deeper insights into customer behavior, operationalize the customer lifecycle, and coordinate actions and results across teams.

This article supports Gainsight NXT, the next evolution of the Customer Success platform. New and upgraded customers are deployed on Gainsight NXT.

If you have not upgraded and are using Gainsight Salesforce Edition, you can find supporting documentation here.

Not sure what your team is using? Click here.

 

This article explains how Admins can use Calculated fields in configuration of the Programs. You can create Calculated Fields using fields from a Gainsight object as part of the Program configuration. Calculated fields can query account variables such as the number of Active users per Account, the number of logins by the user, and the utilization rate. You can add new calculated fields from the Participant and Conditional Wait configuration pages in a Program. Calculated fields can be used in the following configurations:

  • Conditions within the Conditional Wait step to determine how the Program journey progresses.
  • Tokens in the Program email steps.
  • Tokens in the Program CTA steps.

Adding Calculated Fields

Calculated Fields can be added from the Participant and Conditional Wait configuration pages in a Program.

Participant Configuration

You can create calculated fields under the Calculated Fields section on the Participant Configuration page. The configured calculated fields can then be used within any step in the Program.

To create a calculated field in the participant configuration:

  1. Navigate to Journey Orchestrator > Programs and add either a new Program or edit an existing one. For more information on creating new program, refer Program List View and Create New Program.
  2. Select the green Participant Configuration step in the Model Configuration page.

Using Calculated Fields in Programs11.png

  1. Expand the Calculated Fields section on the Participant Configuration page.
  2. Click +CALCULATED FIELD to open the Calculated Field page.

Using Calculated Fields in Programs1.png

  1. Configure the new Calculated Field. Refer to Configuring Calculated Fields for more information on this step.
  2. Click SAVE to save the calculated field configuration.

Using Calculated Fields in Programs2.png

For more information on the Calculated Fields section of the Participant Configuration page, refer to Adding Participants to a Program.

Conditional Wait Configuration

You can create new Calculated Fields under Conditional Wait steps that you have added to the program model. The configured calculated fields can then be used within any step in the Program. You can create calculated fields only in a Conditional Step configuration that is added after the Responded step.

To create a calculated field in the Conditional Wait step configuration:

  1. Click the edit icon in any  Conditional Wait step that you have added in the Model Configuration page.

Using Calculated Fields in Programs12.png

  1. Click the +CONDITION drop-down list and select New Calculated Field. Calculated Field configuration dialog is displayed.

Using Calculated Fields in Programs4.png

  1. Configure the new Calculated Field. For more information on this step, refer to Configuring Calculated Fields.
  2. Click SAVE to save the calculated field configuration.

Using Calculated Fields in Programs5.png

Configuring Calculated Fields

After you select  to create a new calculated field from either the Participant Configuration page or Conditional Wait step configuration, Calculated Field configuration dialog is displayed.

Configure the Calculated field as shown below:

  1. Field Name: Create a name for the Calculated Field.
  2. Data Source: Select an MDA object from the drop-down.
  3. Show Me: Select the field to be displayed from this query. Depending on the field selected, you can configure aggregation options including Count, Count Distinct, Min, Max, Average, and Sum. For number fields, you can also configure the number of decimal places displayed and can select any combination of Sum, Average, and Median for Column Calculation.
  4. Filters: Define filters for the query. You should define filters on the mapped participant fields in the Participant Configuration page.

Using Calculated Fields in Programs6.png

Note: It is important to complete this mapping to participant fields so that the Calculated Field fetches the correct value for the participant in question. Not doing this could lead to incorrect data being queried.

You can use a combination of Field and Value to define the filters.

  1. If users select Field, all mapped participants fields can be used.

Using Calculated Fields in Programs7.png

  1. If users select Value, the user can enter/search for values.

Using Calculated Fields in Programs8.png

  1. Advanced Logic: Apply Advanced Logic. “AND” or “OR” can be used between filter attributes.
  2. SAVE: Saves the Calculated Field.

Using Calculated Fields

Calculated Fields can be used while configuring conditions under Conditional Wait, as well as tokens to reference dynamic information for program Email and CTA steps.

Conditional Wait

For more information on using Calculated Fields as Conditions, refer to Programs: Conditional Wait.

Email Steps

After a Calculated Field is created, you can add it as a tokenization option while configuring any program Email Step as shown below.

Using Calculated Fields in Programs9.png

For more information on configuring email steps, refer to Configure Model and Emails for Programs.

Create/Close CTA Steps

After a Calculated Field is created, you can add it as a tokenization option while configuring any text field in the Create CTA and Close CTA steps as shown below:

Using Calculated Fields in Programs10.png

For more information on adding CTA steps to programs, refer to Configure Model and Emails for Programs.

Notes:

  • When a calculated field is used as a token, it can not be deleted from the program.
  • If the calculated field value is Null for a participant, that participant is dropped during participant sync.
  • Was this article helpful?