Types of campaigns
Refer to the Launching campaign programs documentation for guidelines on planning, gaining approval, testing and launching your campaign within your organization.
Five different types of campaigns allow you to adapt the measurement of employee experience to campaign usage patterns:
Manual campaigns Ask employees for feedback one or several times based on a manual action.
Scheduled campaigns Ask employees for feedback once based on a regularly evaluated investigation.
Remote action campaigns Ask questions and inform employees during the execution of a remote action script.
API campaigns Ask employees for feedback whenever required based on an API call.
Workflow campaigns Ask questions and notify employees during the execution of a workflow.
When targeted manually, via API, with a workflow, or a remote action, a campaign can repeatedly retarget the same users.
When targeted with a Scheduled campaign based on an NQL query, choose the campaign retargeting rule by selecting the relevant option in the Schedule tab.
Remote action campaigns, unlike other types, do not have campaign dashboards, and their responses are not reported to the platform, as the results are only available locally to the remote action script.
Target evaluation and reevaluation
In campaigns that target employees manually, the system selects one or multiple employees from a query result on the Investigations page. There is no automatic reevaluation of targets. To manually trigger a campaign, you must first publish the campaign. If a user already has a pending response—not answered or not declined yet— for the same campaign, the system automatically discards any new attempt to target the same user to avoid double notifications.
In campaigns that target employees via API, the system targets employees from a list of SIDs specified in the API call. To trigger a campaign via API, you must first publish the campaign. Similar to manual targeting, if the user already has a pending response—not answered or not declined yet—for the same campaign, the system automatically discards any new attempt to target the same user to avoid double notifications.
In campaigns that target employees via workflows, the system targets the employee when the Campaign Thinklet is executed as part of a workflow. To use and trigger a campaign via workflows, you must first publish the campaign. Similar to manual targeting, if a user already has a pending response—not answered or not declined yet—for the same campaign, the system automatically discards any new attempt to target the same user to avoid double notifications.
In campaigns targeted with remote actions, the remote action determines the targets. Those employees who interact with the devices targeted by the remote action receive the campaign. You must first publish the campaign.
In campaigns targeted with NQL queries, 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 targeted employees for the first time.
After publication, the set of targeted employees is periodically reevaluated by repeatedly executing the NQL query. Refer to the Schedule section in the documentation for more information.
If a user is targeted on a given day, then that user receives the campaign even if, at a later date, the user is no longer returned by the NQL query. Reevaluation ends when you retire the campaign.
Parameters for Manual, API and Workflow campaigns
Specify parameters for API, manual and workflow campaigns.
Parameters are placeholders in campaign questions requiring input by a user sending a manual campaign, by a third-party system via Nexthink API or with data available inside a workflow. The system saves parameter values along campaign responses, linking answers back to these parameters.
For each campaign, use up to 30 parameters.
Parameters use cases
Below are examples of use cases related to parameters.
Creating parameters
From the New Campaign Draft page, under the General tab:
Select Manual, Workflow or API under Trigger.
Click on the Parameters toggle button.
Add a new parameter and fill in the fields:
Name: Enter a unique name for the parameter.
ID: Enter a unique ID for the parameter to use in NQL queries and when sending API campaigns.
Description: Enter a description to help identify the parameter when sending a campaign from an investigation.
Change the number of parameters and associated IDs for campaigns in a Draft state. For published or retired campaigns, you can only edit the name and description of the parameters.
In API campaigns, parameter IDs must match those of the third-party system.
Using parameters in Campaign questions
After setting up parameters, from the New Campaign Draft page or Edit Campaign page:
Go to the Content tab.
Insert parameters inside Text questions, and their translated versions, using the {x} icon in the Text toolbar.
Follow the parameter
{{parameter_id}}syntax.
Below are examples of using parameters in manual and API-triggered campaigns.
Example of using parameters in Manual campaigns
The following example displays the use of parameters {{service_name}}, {{impact}}, {{timeframe}} and ({{incident_id}}) for a manually triggered campaign.
When you launch and send out a manual campaign to users from the Investigations page, you must input the values of the campaign parameters by filling in the Send campaign pop-up window.
Example of using parameters in API campaigns
The following example displays the use of parameters {{ticket_description}} and {{ticket_number}} for an API-triggered campaign.
Remember, parameter IDs must match those of the third-party system calling the Nexthink API.
RELATED TOPICS
Last updated
