Products
Contact Support Additional Learning Monthly Product Updates
Menu

Forsta CATI Support

All the topics, resources needed for Forsta CATI.

Supplementing CATI Paradata with Survey Variables

  • Last updated:

Articles in this section

In this article

    1: Overview

    In addition to synchronizing standard CATI paradata to SmartHub, you can now enhance your reporting dataset by including selected survey variables alongside call history data. This enables more advanced reporting scenarios in Studio, where operational metrics (paradata) can be analysed in combination with respondent-level or survey-captured information.

    2: Why use this feature?

    While CATI paradata provides rich insight into interviewer activity and call outcomes, there are many cases where combining this with survey data adds valuable context. For example:

    • Segmenting productivity by respondent attributes (e.g. region, customer type)

    • Analysing outcomes based on survey responses

    • Reviewing interviewer performance alongside call attempt-level metadata captured in survey loops

    • Building more comprehensive, business-specific reports in Studio

    This feature allows you to define up to 5 additional variables that will be included with the synced call history data in SmartHub.

    3: Configuring Custom Call History Fields

    To configure these additional fields:

    1. Navigate to Admin in CATI Supervisor

    2. Select Custom call history fields

    This opens the configuration screen where you can define up to five variables to include in the SmartHub sync.

    3.1: Field Configuration Options

    For each custom field, you can define the following:

    1. Source Survey Data

    Select where the variable originates from:

    • Respondent

      Variables stored at the respondent (background) level

    • Response

      Variables captured as part of the survey responses

    • Call history loop (e.g. callhistoryinfo)

      Variables captured within a repeating loop used to store call attempt-level information (e.g. interviewer name, call time per attempt)

    Note: The call history loop name may vary depending on your survey design. The default CATI starter template includes a loop named callhistoryinfo, but this may have been renamed or removed.

    2. Source Survey Field Name

    Enter the exact variable name as defined in your survey.

    • This must match the survey variable name precisely

    • The system uses this to extract and sync the data to SmartHub

    3. CATI Display Name (Optional)

    • Provide a user-friendly label for the field as it will appear in the CATI and reporting interfaces.

    • If left blank, the original variable name will be used

    4. Description (Optional)

    Add a description to help other users understand the purpose and usage of the field.

    4: Important Considerations

    • A maximum of 5 custom fields can be configured

    • These fields are globally configured, so it is recommended to select variables that are:

      - Common across multiple CATI surveys

      - Consistently named and structured

    • If a variable does not exist in a particular survey, it will not populate for that dataset in SmartHub

    • Changes to configuration will apply to newly synced data going forward

    5: Best Practices

    To get the most value from this feature:

    • Standardise key variables across your CATI surveys (e.g. region, interviewer ID, quota group)

    • Retain and consistently use the call history loop in your survey design for capturing attempt-level data

    • Use clear and consistent naming conventions for variables

    • Add display names and descriptions to improve usability for report builders in Studio