Introduction

Field Settings is the base from which available Filters, Import fields and field labels are being pulled from. The field settings allows you to manage which fields exist in CustomerGauge, and how they're called. You can add fields to various "Objects" (types of data) that exist within CustomerGauge.


Good to Know

  • Field Settings is only available to Admin users without Data Access Restriction
  • Fields can not be moved between objects
  • Fields can not be removed
  • Field Settings currently apply to the following areas:
    • Reporting Filters
    • Account and Account Alias Imports
  • Your CSM will need to manage fields used in the following places:
    • Customer Details Page
    • "Import Data" (Survey data, Historical data, Address Book, Revenue)
    • Export Engine
    • API Field Names


Using the Field Settings

You can find the Field Settings by navigating to Settings → System Admin → System Settings → Field Settings.


  1. Navigate the tabs to the objects you'd like to interact with.
  2. In the Accounts column, you can find all the properties configured on the Account level. Hover over the existing fields to access Edit.
  3. Adding fields in Accounts creates a copy of that field on Survey Records in Field Settings. You can upload data on survey imports once your CSM also adds it in the backend for you - please tell them the "Classic Label" name for the field (visible while in Edit).
    1. This allows you to upload a snapshot in time. E.g. the Account Manager for the survey sent now is "John", but a year from now it might be "Jane". When you look back to "now", a year from now, you'd still want to see the survey attached to "John", while the account belongs to Jane now.
  4. In the Contacts column, you can find all the properties configured on the Contact level. Hover over the existing fields to access Edit.
  5. Adding fields in Contacts creates a copy of that field on Survey Records in Field Settings. You can upload data on survey imports once your CSM also adds it in the backend for you - please tell them the "Classic Label" name for the field (visible while in Edit).
    1. This allows you to upload a snapshot in time. E.g. the Job Level for the survey sent now is "B", but a year from now it might be "A". When you look back to "now", a year from now, you'd still want to see the survey attached to "B", while the contact is belongs to A now.
  6. In the Survey Records column, you can find all the properties configured on the Survey level. Hover over the existing fields to access Edit.
    1. Making changes in Field Settings do not directly impact data. Do note that changing the context of a field (e.g. changing the field label to something completely different) is ill advised.
  7. Adding fields in Survey Records enables it to be turned into a filter. You can upload data on survey imports once your CSM also adds it in the backend for you - please tell them the "Classic Label" (visible while in Edit).


Asking CSM to Update

Your CSM will need to manage fields in a couple of places that are not controlled by Field Settings yet. Each scenario is listed below.


Customer Details Page

Your CSM can help with the following actions:

  • Add or Remove a field to the Customer Details Page
  • Re-label an existing field on the Customer Details Page


Import Data

Your CSM can help with the following actions:

  • Add or Remove a Survey field to be available to be imported
    • Emphasis: If you have added a field to Survey Records in Field Settings, and would like to use it in survey imports, make sure to ask your CSM to update the Import Settings of your platform!

  • Re-label an existing field or change its technical name


Export Engine

Your CSM can help with the following actions:

  • Add or Remove a Survey field to be available to be exported
  • Re-label an existing field or change its technical name


Import Data

Your CSM can help with the following actions:

  • Add or Remove a Survey field to be available in the GET Transactions APIs
  • Change how a Survey field is called in the GET Transactions APIs


Classic Labels

Accounts

Field nameDescription
referenceUnique identifier of an Account record
startEarliest contract start date. Can be provided through the PUT Contracts API.
endLatest contract end date. Can be provided through the PUT Contracts API.
segment_a - segment_zFields that can be used to describe important Account properties. Can be used in Account Filters and Group By in Reporting. Examples: Account Manager, Parent Account, Industry, Company Size


Survey Records

Field nameDescription
touchpointDescribes the survey touchpoint that this survey applies to.
companyUnique identifier of the related Account record.
job_levelPlace in the organisational hierarchy (A, B, C, U) where "A" is the top level in the organization (C-Suite) and "C" is Operational / Frontline. "U" stands for "Unknown".
job_positionJob title of the survey recipient.
countryISO 3166-1 alpha-2 codes of a country describing something about the survey.
segment_a - segment_zFields that can be used to describe important Survey properties. Can be used in Survey Filters and Group By in Reporting. Examples: