LogoLogo
LearnDocumentationSupportCommunity
Version 6.30
Version 6.30
  • Welcome
  • Nexthink V6
  • Overview
    • Software components
    • Collector
    • Finder
    • Engine
    • Portal
    • Nexthink Library
    • Digital Experience Score
  • Installation and configuration
    • Planning your installation
      • Overview of the installation process
      • Hardware requirements
      • Connectivity requirements
      • Software requirements
      • Reference architectures
    • Installing Portal and Engine Appliances
      • Installing the Appliance
      • Installing the Appliance on Azure
      • Installing the Appliance on AWS
      • Installing the Appliance on OTC
      • Managing Appliance accounts
      • Setting the names of the Portal
      • Setting the names of the Engines
      • Specifying your internal networks and domains
      • Federating your Appliances
      • STIG compliance in Web Console
      • Connecting the Portal to the Engines
      • Configuring session performance storage
      • Configuring device performance storage
      • Setting up a software license
      • Sending email notifications from the Appliance
      • Allocating resources for the Portal
    • Installing the Collector
      • Installing the Collector on Windows
      • Installing the Collector on macOS
      • Installing the Collector for a Proof of Value
      • Assigning Collectors to Engines
      • Assignment of roaming Collectors
      • Collector MSI parameters reference table
      • Nxtcfg - Collector configuration tool
      • Inspecting the connection status of the Collector
      • Querying the status of the TCP connection of the Collector
      • Reporting the URL of HTTP web requests
      • Auditing logon events
      • Viewing user interactions in virtualized and embedded environments
      • Engage notifications on macOS
      • Configuring Collector level anonymization
    • Collector remote connectivity
      • Redirecting and anonymizing Collector traffic
      • Redirecting the Collector TCP channel
      • Support for DirectAccess
      • Windows Collector proxy support
      • Mac Collector proxy support
    • Installing the Event Connector
      • Installing the Event Connector on Linux
    • Installing the Finder
      • Installing the Finder on Windows
      • Enabling Cross-Engine Finder features
      • Expanding the time frame of investigations in the Finder
      • Enabling Finder access to the Library
      • Finder proxy support
    • Updating from V6.x
      • Updating the Appliance
      • Content centralization when updating the Appliance
      • Updating the Collector
      • Viewing Collector deprecated fields
      • Updating the Finder
    • Security and user account management
      • Importing and replacing certificates
      • Hierarchizing your infrastructure
      • Adding users
      • Enabling SAML authentication of users
      • Just-In-Time provisioning of user accounts
      • Enabling Windows authentication of users
      • Multi-factor authentication for local accounts overview
      • Provisioning user accounts from Active Directory
      • Establishing a privacy policy
      • Disabling local accounts for interactive users
      • Setting the complexity and minimum length of passwords for local accounts
      • Protecting local accounts against brute force attacks
      • Preventing password saving in the Finder
      • Controlling session timeouts in the Portal
      • Security settings in the Appliance
      • Setting the Do Not Disturb periods between campaigns
    • Data retrieval and storage
      • Data retention
      • Increasing the maximum number of metrics
      • Establishing a data retention policy in the Engine
      • Storing Engine data in a secondary disk drive
      • Importing data from Microsoft Active Directory
      • Setting the locale in the Portal
      • Changing the Time Zone of the Portal
      • Time Zones and data collection
      • Changing the data collection time of the Portal
      • Nightly task schedules timetable
      • Changing the thresholds of High CPU warnings
      • Automatic restart of unresponsive Engine
    • Maintenance operations
      • Logging in to the CLI
      • Special operation modes for the Engine and the Portal
      • Changing the default ports in the Appliance
      • Centralized Management of Appliances and Engines
      • Monitoring the performance of the Appliance
      • Resizing partitions in Appliance
      • Configuring the system log
      • Examining the logs in the Portal
      • GDPR - Retrieving or anonymizing personal data
      • Finding out unlicensed devices
      • Removing devices
      • Installing third-party software in the Appliance
      • Installing VMware Tools in the Appliance
      • Operational data sent to Nexthink
      • Sending additional data to Support
    • Disaster recovery
      • Planning for disaster recovery
      • Web Console backup and restore
      • Engine backup and restore
      • Portal backup and restore
      • Rule-based assignment backup and restore
      • License backup and restore
      • PKI backup and restore
    • Branding
      • Branding the Portal
      • Branding of campaigns
  • User manual
    • Getting started
      • Logging in to the Finder
      • Logging in to the Portal
      • Enabling STIG in Webconsole
    • Querying the system
      • Searching the subject of interest
      • Executing an investigation
      • Creating an investigation
      • Editing the options of an investigation
      • Combining logical conditions in investigations
      • Navigating through the results of an investigation
      • Properties of users and devices
    • Visualizing system activity in the Finder
      • Getting a quick overview
      • Graphically observing the activity of users and devices
      • Observing service performance
      • Viewing network connections
      • Viewing web requests
      • Viewing executions
    • Monitoring IT custom metrics
      • Creating a metric
      • Examples of metrics
      • Session performance
      • Device performance
      • Following the evolution of a metric
      • Finding the visuals of a metric
    • Monitoring IT services
      • Analyzing service quality
      • Creating a service
      • Following the evolution of a service
      • Specifying URL paths of web-based services
    • Engaging with the end user
      • Getting feedback from the end users
      • Types of campaigns
      • Creating a campaign
      • Editing a campaign
      • Types of questions
      • Controlling the flow of questions
      • Translating a campaign
      • Triggering a campaign manually
      • Limiting the reception rate of campaigns
      • Scrutinizing the results of a campaign
      • Continuously measuring the satisfaction of employees
    • Rating devices and users with scores
      • Computing scores
      • Creating a score
      • Checking and comparing ratings
      • Computing potential savings
      • Score XML Reference
      • Documenting scores
    • Remotely acting on devices
      • Scenarios for remote actions
      • Creating a remote action
      • Executing remote actions
      • Triggering a remote action manually
      • Writing scripts for remote actions on Windows
      • Writing scripts for remote actions on Mac
      • Example of self-healing scenario
      • Example of self-help scenario
      • Application control and remote actions
    • Organizing objects with categories
      • Classifying objects of the same type
      • Creating categories and keywords
      • Tagging objects manually
      • Tagging objects automatically
      • Importing tags from text files
    • Getting notified by the system
      • Receiving Engage campaigns
      • Receiving email digests
      • Receiving alerts
      • Creating a service-based alert
      • Creating an investigation-based alert
    • Building web-based dashboards
      • Introducing dashboards in the Portal
      • Creating a dashboard
      • Examining metrics in depth
      • Documenting dashboards
      • Assessing license use
      • Computing dashboard data
      • Reusing dashboard content
    • Importing and exporting authored content
      • Methods for reusing authored content
      • Manually sharing Finder content
      • Importing a content pack
      • Conflict resolution
      • Exporting a content pack
  • Library packs
    • Compliance
      • Device Compliance
    • Configuration Manuals
      • Overview (Configuration Manuals)
      • Installing A New Version Of A Library Pack
    • Digital Employee Score (DEX score)
      • DEX Score Installation And Configuration
      • Detailed Library Pack Changelog
    • Device management
      • Reduce logon duration
      • Group Policy Management
      • Hardware Asset Renewal
      • Hardware Asset Renewal Advanced
      • Application Auto-Start Impact
    • Remote Employee Experience
      • Remote Worker Experience
      • Home Networking
      • Change Log And Upgrade Process
      • Remote Worker Vs Office Worker Device Category
      • Remote Worker Insights
      • DEX V2 Upgrade Of Remote Worker
    • Persona Insight
      • Persona Insight - Overview
      • Persona Insight - Library Pack
      • Persona Insight - Score Only Pack
      • Persona Insight - Without Campaign pack
      • Persona Insight - Getting Started and Upgrade Procedure
      • Persona Insight - Configuration Guide
      • Persona Insight - Troubleshooting - Multiple devices on multiple engines
      • Persona Insight - Reference Guide
      • Persona Insight - Example Pack
      • Persona Insight - Device Sizing
        • Persona Insight - Device Sizing Overview
        • Persona Insight - Device Sizing Configuration
      • Persona Insight - Application Sizing
        • Persona Insight - Application Sizing Overview
        • Persona Insight - Application Sizing Configuration
      • Legacy Persona documentation
        • Persona Insight - Library Pack (V.1.0.0.0)
        • Persona Insight - Base Pack
        • Persona Insight - Base Pack Advanced
        • Persona Insight - Customization Guide (V1.0.0.0)
        • Persona Insight - Configuration Guide (V1.0.0.0)
        • Persona Insight - Reference Guide (V1.0.0.0)
    • GSuite
      • GSuite: Health
      • GSuite: Services
      • GSuite: Sentiment
      • GSuite: Advanced Health
    • Support
      • Support: Level 1
    • Shadow IT
      • Shadow IT
    • Malware Protection
      • Malware Protection
    • Office 365 Health
      • Office 365 Health: Overview
      • Office 365 Health: Services
    • Office 365 OneDrive
      • OneDrive Summary
      • OneDrive Operations
      • OneDrive Advanced Health
      • OneDrive Migration
      • OneDrive Sentiment
      • OneDrive Management
      • OneDrive Advanced Operations
    • Office 365 Teams
      • Teams Overall Configuration
      • Teams - Migration
      • Teams - Health
      • Teams - Advanced Health
      • Teams - Adoption
    • Microsoft 365 Apps
      • Microsoft 365 Apps - Operate
    • Employee Self Service
      • Overview
      • Configuration
      • Usage
    • Onboarding Experience Management
      • OEM - Overview
      • OEM - Configuration
    • Office 365 Outlook
      • Outlook Troubleshooting
    • Virtualization
      • Virtualization: Operate
      • Virtualization: AVD - Advanced
      • Virtualization: Citrix Advanced
      • Virtualization: Project
      • Virtualization: Troubleshooting
        • Virtualization: Troubleshooting: Configuration
    • Windows
      • Win10: Configuration
      • Win10: Migration
      • Win10: Feature Update
      • Win10: Quality Update
      • Windows Defender Management
      • Administrators Management
    • Windows 11
      • Windows 11 - Readiness
      • Windows 11 - Migration Pilot
      • Windows 11 - Migration
      • Windows 11 - Operate
    • Webex
      • Webex Operate
    • Zoom
      • Zoom Operate
    • Remote Actions
      • Get Performance Monitor Data
      • Skype For Business
      • Restart Device
      • Upload Logs to S3 using PreSigned URLs
    • Software Asset Optimization
    • Collaboration Optimization
      • Collaboration Optimization - Solution Overview
      • Collaboration Optimization - Configuration
      • Collaboration Optimization - Usage / Troubleshooting
    • Systems Management
      • Manage Configuration Drift
      • MS ConfigMgr - Client Health
        • MS ConfigMgr - Client Health - Summary
        • MS ConfigMgr - Client Health - Configuration Guide
      • Intune
        • Intune - Health
          • Intune - Health - Summary
          • Intune - Health - Configuration Guide
    • Return to the office
      • Return to the office - Planning
      • Return to the office - Readiness
    • Green IT
      • Green IT - Overview
      • Green IT - Configuration Guide
    • Hybrid Working
      • Hybrid Working Experience
      • Hybrid Working Experience - Installation and upgrade procedure
  • Integrations
    • Nexthink ServiceNow Service Graph Connector
      • Overview
        • Roles and Permissions
        • Modules
      • Installation and Configuration Guide
        • Pre-requisites
          • Configure Identification Rules
          • Import and setup the CMDB categories in Finder
        • Setup
          • Configure the connection
          • Configure import properties
          • Configure additional engines
          • Set up scheduled import jobs
      • Data transformation and mapping by default
      • How to customize the behaviour of the Connector
      • FAQ
        • Why ServiceNow Service Graph Connector?
        • What about Nexthink CMDB Connector?
        • Why is the name the primary key for the devices?
      • Troubleshooting
        • IRE identification issues
          • [No Choice found in the sys_choice table for the target table](integrations/nexthink-servicenow-service-graph-connector/troubleshooting/ire-identification-issues/ no-choice-found-in-the-sys_choice-table-for-the-target-table.md)
          • Identification rules not created
          • Discovery_source choice not created
        • Timeout Errors
          • ECCResponseTimeoutException
          • HTTP 0 error
        • MID server issues
          • java.lang.NullPointerException
          • MID Server memory issues
          • Not trusted certificates in Quebec release
        • Configure credentials issues
          • [Not allowing update of property authentication_choice](integrations/nexthink-servicenow-service-graph-connector/troubleshooting/configure-credentials-issues/ not-allowing-update-of-property-authentication_choice.md)
          • Invalid username/password combo (HTTP 401/403)
        • Configure Engines Issues
          • [The client secret supplied for a confidential client is invalid](integrations/nexthink-servicenow-service-graph-connector/troubleshooting/configure-engines-issues/ the-client-secret-supplied-for-a-confidential-client-is-invalid.md)
        • No Cis imported and no errors found in the log
    • Nexthink ServiceNow Incident Management Connector (IMC)
      • Installation and configuration guide (IMC)
      • Troubleshooting Guide (IMC)
      • Domain separation installation (IMC)
    • Nexthink ServiceNow CMDB Connectors
      • Installation and Configuration Guide
      • Troubleshooting Guide
      • Field transformation and normalisation examples
    • Nexthink Event Connector
      • High level overview
      • Installation and Configuration Guide
      • Troubleshooting guide
      • RPM installation
      • Splunk specific documentation
        • Upgrading from Splunk Connector to Event Connector
        • Splunk add-on installation and usage
    • Nexthink Chatbot SDK
      • Introduction and concepts
      • Installation, configuration and update guide
        • Installation and configuration
        • Update to newer version
        • Uninstallation
        • Authentication
        • Topics configuration
        • Remote action configuration
        • Advanced configuration
        • Additional resources and references
      • Dimensioning guide
      • Troubleshooting
      • Technical solution description
      • Downloads and release notes
  • Glossary and references
    • Search and information display
      • Search in Finder
      • Keyboard shortcuts for column display selection
      • Campaign display compatibility
      • Real-time and consolidated service data
      • Service errors and warnings
      • Errors and warnings for devices and executions
      • Types of widgets
      • Widget compute state in charts
      • Errors in the execution of remote actions
      • Top results of Cross-Engine investigations
      • Engine data history
    • Tooltips in the user and device views
      • Alerts tooltips
      • Warnings tooltips
      • Errors tooltips
      • Activity tooltips
      • Services tooltips
    • Database information and organization
      • Maximum supported values
      • Local and shared content
      • Device Identification
      • Local IP address of devices
      • Timestamping of events
      • Boot and logon duration
      • Application startup duration
      • Application not responding events
      • Memory and CPU usage
      • Status of TCP connections
      • Status of UDP connections
      • Network and port scan conditions
      • Binary paths
      • Maximum number of Binaries
      • Package Executable Mapping
      • Metro apps
      • Investigation with packages
      • Portal aggregation and grouping
      • Focus time metric
    • Security
      • Access rights and permissions
      • Active Directory authentication
      • Canonical domain names for Windows authentication
      • System alerts
      • Audit trail
      • Appliance hardening
      • STIG hardening
      • FIPS 140-2 compliance
      • Security bulletins
        • Is Nexthink affected by Okta breach
        • Is Nexthink affected by SolarWinds breach
        • Nexthink and Log4j - Security bulletin
        • CVE-2022-22965 - Security Vulnerability Spring4shell - Spring Framework
        • Version 6.22.2.10: Security Vulnerability Maintenance Release
        • The Collector V6.27.X Release – Security Bulletin
    • References
      • Components of the Collector
      • Server support
      • Compatibility mode
    • Glossary
      • Activity
      • Alert
      • Application
      • Binary
      • Campaign
      • Category
      • Connection
      • Dashboard
      • Destination
      • Device
      • Domain
      • Entity
      • Event
      • Executable
      • Execution
      • Focus time
      • Hierarchy
      • Installation
      • Investigation
      • Keyword
      • Metric
      • Module
      • Object
      • Package
      • Platform
      • Port
      • Printer
      • Score
      • Service
      • Session
      • System boot
      • User
      • User logon
      • Web request
      • Widget
  • API and integrations
    • Integrating with Nexthink
      • Event Connector
      • Getting data through the NXQL API
      • Bidirectional integration with the Finder
      • Count metrics API
      • Software metering API
      • Services API
      • List Engines API
      • GetSID API
      • Triggering campaigns via their API
      • Triggering remote actions via their API
      • Audit trail API
      • Integrating investigation-based alerts
      • Downloads
    • NXQL API
      • Introducing the NXQL API
      • NXQL Tutorial
      • NXQL language definition
      • NXQL Data Model
    • Integrations
      • Excel integration with NXQL
      • Power BI
      • Azure Data Lake Storage Gen2
      • Splunk Event Connector
    • ServiceNow
      • CMDB Connector
      • Incident Management Connector
      • Event Management

© Nexthink

  • Privacy policy
  • Responsible Disclosure Policy
On this page
  • Overview
  • One-off campaign
  • Recurring campaign
  • Continuous Satisfaction Measurement campaign (or continuous campaign for short)
  • Specifying the type of campaign
  • Characteristics of a campaign
  • Target evaluation and re-evaluation
  • Sending the campaign to the end users
  • Reminder of notifications
  • Quiet period
  • Effects of retiring and republishing a campaign

Was this helpful?

  1. User manual
  2. Engaging with the end user

Types of campaigns

Last updated 9 months ago

Was this helpful?

Overview

There are a variety of situations in which you may want to know the opinion of the end users about a particular subject. Depending on the nature of the subject, specially on its temporal characteristics, asking for feedback usually requires different approaches. For instance, you may want to know the reaction of the end users to a single change in the IT infrastructure and ask them about it only once. In the case of a recurring event, however, it may be appropriate to repeatedly ask end users for feedback at every occurrence of the event. In other cases, such as when willing to know how end users perceive the quality of an IT service, it makes sense to continuously measure the evolution of the end-user satisfaction.

Three different types of campaigns let you adapt the measurement of the end-user experience to these usage patterns:

One-off campaign

Ask for feedback to the end users only once.

Recurring campaign

Repeatedly ask the end users for feedback about a matter that happens time and time again.

Continuous Satisfaction Measurement campaign (or continuous campaign for short)

with respect to a particular subject.

Specifying the type of campaign

When , indirectly specify its type by choosing the appropriate options in the RECIPIENTS section.

The first option lets you choose how the campaign targets users, which may already determine the type of the campaign:

  • When targeted manually or with a remote action, the result is a special kind of recurring campaign, as the campaign can target users again manually, through the Engage API, or through a remote action. The way to prevent resending the campaign to the same user in a short period of time depends on the chosen option (see below).

  • When targeted with an investigation, the type of campaign is determined by two additional options that appear just below the placeholder for the investigation that targets users.

The first option of a campaign that targets users with an investigation reads:

  • The campaign will be sent to (...)

    • To create either a one-off or a recurring campaign, choose all target users.One-off and recurring campaigns are sent to all the users retrieved by the investigation associated to the campaign when it is evaluated.

    • To create a continuous satisfaction measurement campaign, choose a different sample of target users every day (continuous measurement)Only a small fraction of the total target population actually receives the campaign each day. The system computes a sample of the target users from the total set of users retrieved by the associated investigation with the aim of maximizing the representativeness of the sample, while minimizing the annoyance of the end users (not all users need to answer the campaign).

Because all targeted users receive one-off or recurring campaigns, the second option for these types of campaigns reads:

  • Target users will receive the campaign

    • To create a one-off campaign, select only once from the list.

    • To create a recurring campaign, select again from the list. A second part of the sentence shows up, letting you define the recurring or quiet period; that is, the time between a user answers a campaign and the same user receives the same campaign again:

      • Enter a number followed by a time unit (to choose from a list) as the quiet period.

Because only a sample of the target users receive a campaign each day in continuous campaigns and because continuous campaigns always define a quiet period, the second option for continuous campaigns switches to:

  • Target users can receive the campaign again after

    • Enter a number followed by a time unit (to choose from a list) as the quiet period.

Characteristics of a campaign

Target evaluation and re-evaluation

In campaigns that target users manually, a Finder user selects the users from a list view or from a user view and then triggers the campaign. Therefore, there is no automatic evaluation of targets. To manually trigger a campaign, the campaign must be published beforehand.

In campaigns targeted with remote actions, the targets are determined by the remote action itself. The users who interact with the devices targeted by the remote action receive the campaign, which must have been published beforehand.

In campaigns targeted with investigations, the evaluation of targets starts at the moment of publishing the campaign. When you publish a campaign, the campaign executes its associated investigation to retrieve target users for the first time. In the case of a continuous campaign, it additionally computes a sample of the target users from the results of the investigation.

After publication, the set of target users is periodically re-evaluated by executing the investigation again and again (and taking a sample, if the campaign is continuous). The frequency of re-evaluation depends on the type of campaign, but it is always relative to the time of the first evaluation:

  • For one-off and recurring campaigns: 10 minutes.

  • For continuous campaigns: 24 hours.

That is, for one-off and recurring campaigns, re-evaluation happens frequently. For continuous campaigns, it happens once every day. Re-evaluation ends when the campaign is retired.

Sending the campaign to the end users

An end user that is retrieved by the investigation associated to a one-off or a recurring campaign, or which is part of the sample of target users selected by a continuous campaign, receives the campaign:

  • The process of sending the campaign to end users starts immediately after the campaign is published.

  • The sending process stops as soon as the campaign is retired.

  • If the campaign is republished, the sending process restarts straightaway.

Users who are offline (that is, not logged in to a device) when the campaign is sent cannot receive it immediately. Instead, the moment when offline users receive the campaign depends on the type of campaign:

  • For one-off and recurring campaigns: users receive the campaign the next time that they are targeted.

  • For continuous campaigns: users receive the campaign as soon as they log in to a device.

Reminder of notifications

An end user who got a notification from a campaign that has notifications enabled is reminded to provide the answers to the questions of the campaign with a new notification if:

  • The user did not answer all the questions of the campaign.

  • The user did not decline to participate in the campaign.

Once a user gets a notification from a campaign, the user keeps receiving reminder notifications to finish answering the questions even if that particular user is no longer part of the selected target users (after the re-evaluation of the investigation associated to the campaign). Reminder notifications appear thus in the device of the end user with the frequency specified in the definition of the campaign until one of the following conditions is met:

  • The user fully answers the campaign.

  • The user declines to participate in the campaign.

  • The campaign is retired.

Reminder notifications work with all types of campaigns, except for those launched from remote actions, and are independent of the quiet period.

Quiet period

The quiet period is a method of recurring and continuous campaigns to avoid bothering users more than is strictly necessary. Because of the repetitive nature of these types of campaigns, users may have to respond to the questions of a campaign more than once. The quiet period defines the minimum time interval between the moment when a user answers all the questions of a campaign and the moment when the same user receives the same campaign again.

  • The quiet period of recurring and continuous campaigns that are targeted with an investigation is specified in the definition of the campaign.

  • The quiet period of campaigns that are targeted with a remote action is controlled by the triggering period of the associated remote action.

  • The quiet period of manually targeted campaigns is fixed to two hours to prevent accidental re-triggering.

Effects of retiring and republishing a campaign

When a campaign targeted with an investigation is retired, it stops evaluating the target users and stops being sent. If the campaign is republished, it must be emphasized that it is still the same campaign that is relaunched again, which is different from starting anew. The history of the campaign is kept and, in particular, the status of the end users in relation to the campaign. The effects of republishing a campaign on the end users depends thus on their status and on the type of campaign:

  • On users who declined to participate

    • Republishing the campaign has no effect on these users, regardless of the type of campaign. They already declined to participate and will never receive the same campaign again.

  • On users who fully answered the campaign

    • For one-off campaigns, republishing has no effect, since the users already answered the campaign and will not receive it any more.

    • For recurring and continuous campaigns, users who already answered the campaign may be retargeted again, but always respecting their quiet period.

  • On users who were notified, but neither answered completely nor declined

    • For one-off campaigns, users are retargeted immediately, as long as they are still part of the results of the investigation that retrieves target users. Otherwise, users do not receive reminder notifications right away, but only when they become target users again.

    • For recurring and continuous campaigns, users may be retargeted respecting their quiet period, which is enforced in this case even though users did not fully answer the campaign in its previous incarnation. In the same way as in one-off campaigns, until users are not selected again as targets, they do not receive reminder notifications.

To target again users who declined to participate or users that fully answered a one-off campaign, you must create and publish a new campaign.

Retiring a manually targeted campaign implies that no Finder user can trigger the campaign, unless it is republished again. In the latter case, the quiet period of two hours applies to the retargeting of users who already answered the campaign.

Retiring a campaign targeted with a remote action implies that the remote action will not be able to display the campaign. Republish the campaign for the remote action to work properly.


RELATED TASK

Continuously measuring the satisfaction of employees
Continuously estimate the overall satisfaction of end users
creating a campaign
quiet period