Understanding campaign targeting models
Refer to the Launching campaign programs documentation for guidelines on planning, gaining approval, testing and launching your campaign within your organization.
Five different models of campaign targeting allow you to adapt the measurement of employee experience to campaign usage patterns:
Manual campaigns
Scheduled campaigns
Remote action campaigns
API campaigns
Workflow campaigns
Manual, API, and workflow campaigns can be parameterized. In such cases, users who trigger the campaign manually or systems that execute it via an API call must provide the required input values.
Refer to Configuring campaign parametersfor more information.
Configuring campaign trigger method
Manual campaign configuration
Select the Manual trigger to request feedback from employees through a manual action. After the campaign is published, you can send it directly to selected users or VDI sessions from the Investigations page.
Refer to Campaign sending methods documentation.
Campaign scheduling
Select the Schedule trigger to ask employees for feedback based on a regularly evaluated investigation.
After selecting the Schedule trigger on the General tab of the campaign Edit page, navigate to the Schedule tab. Define the campaign recipients using NQL, and choose the campaign retargeting rule.
Targeting query
Write an NQL query to define who receives a campaign. You can use queries that return users in the following forms:
Query that starts with
users. These queries allow the employee to see the campaign on any of their devices.Query that starts with
devicesand return a columnuser_sidin its list statement (query must include| list ..., user_sid, ...). These queries target users with device issues, showing the campaign only on the corresponding device. For example, the last users of devices that experienced system crashes in the last week:
To target a specific VDI session instead of a device, you must run a query for VDI sessions.
Targeting a campaign at a specific user deploys it to all devices assigned to that user.
Targeting a campaign at a specific VDI session deploys it to the virtual device corresponding to that session.
The system evaluates the query after the campaign is published and sends it based on the option that you selected in the Target users will receive the campaign section. Refer to the Campaigns NQL examples for query examples.
Target employees will receive the campaign
Choose one of the following options to define how the system sends the campaign.
Once you publish the campaign, you cannot change this setting. To change the schedule, you need to retire the campaign.
The Remote Action trigger type cannot be selected or deselected once the campaign is published. All other trigger types can be changed if the campaign is briefly retired and republished for reconfiguration.
Only once: The campaign will only be sent once to the employee, and will never recur. Use this option, for example, for employee onboarding campaigns, one-time surveys or notifications, and other one-time communications. With this option, the system evaluates the NQL query every 24 hours after the campaign is published to identify new employees to target. Employees who answered or declined the campaign will no longer see it.
Again after: Select this option to enable recurring campaigns. Use it, for example, for proactive fixes, a reminder to restart computers regularly, or for surveys that need to be sent at specific intervals. To provide more immediate feedback, the system evaluates the campaign every hour. To protect employees from unnecessary interruption, they will not receive the campaign if they have already answered it or declined it within the selected timeframe.
For example, if you choose the campaign to be resent again after one week, the system will resend it seven days after the employee has either answered or declined the campaign. If you choose one month, the system will resend it 30 days after the employee has either answered or declined the campaign.
If the user is targeted at a given time, they receive the campaign even if the NQL query no longer returns the user later. Reevaluation ends when you retire the campaign.
Set up continuous employee sampling using NQL
You can set up the query to randomly select a different sample of employees and continuously collect sentiment data. Replace #dex_campaign_name with the campaign NQL ID and adjust the limit to specify the number of new users the campaign targets each hour.
Note that you need to:
Define the Schedule trigger method on the General tab.
Select Again after from the Target employees will receive the campaign section and provide the minimum number of days you want between responses for each employee.
Save the campaign at least once before using the NQL query below. This ensures the system recognizes your campaign and avoids a Table does not exist error during NQL query validation.
Refer to Scheduling recurring campaign for more information.
Remote action campaign configuration
Select the Remote action trigger method on the General tab of the campaign Edit page to ask questions and inform employees during the execution of a remote action script.
Unlike other types, remote action campaigns do not have campaign dashboards, and their responses are not reported to the platform. Instead, the results are only available locally to the remote action script.
After publishing the campaign, add its NQL ID to the remote action’s scripts to trigger the campaign.
Retrieving campaign NQL ID
Select Campaigns from the main menu.
Click on Manage campaigns in the navigation panel.
Click on the title of the campaign you wish to connect to.
Copy the NQL ID value from the NQL ID field in the General tab of the configuration page.
Paste the value into your remote action script. Refer to the following documentation for details:
Nexthink recommends using NQL ID as a campaign identifier if you use Collectors version 23.5 or higher. You can still use campaign UID for compatibility reasons.
Retrieving campaign UID
Select Campaigns from the main menu.
Choose the campaign you wish to connect to from the navigation menu.
Locate the UID of the campaign as part of the URL and copy it for the remote action.
API campaign configuration
Select the API trigger to ask employees for feedback based on an API call.
Trigger campaigns using the Nexthink Campaigns API, which enables integrations with external applications. For parametric campaigns, specify the values of each parameter. Visit the developer.nexthink.com website to learn more.
Workflow campaign configuration
Select the Workflow trigger method on the General tab of the campaign Edit page to ask questions and notify employees during the execution of a workflow.
Trigger campaigns using the Nexthink Workflow API to notify employees about remediations that are taking place, or to prompt for permission or additional information that a workflow needs to continue running an automated remediation.
To use a campaign in a workflow, ensure that:
The workflow trigger is set.
The campaign contains only single answer questions.
The campaign is published.
Target evaluation and reevaluation
Depending on the selected targeting method, the system evaluates and, where applicable, reevaluates campaign targets differently.
When targeted manually, via API, with a workflow, or a remote action, a campaign can repeatedly retarget the same users.
Manual campaigns
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.
Scheduled campaigns
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 targeted employees are periodically reevaluated by repeatedly executing the NQL query.
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.
API campaigns
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. Like 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.
Workflow campaigns
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. Like 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.
Remote action campaigns
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.
RELATED TOPICS
Last updated
Was this helpful?