Messaging Queues: Targeting

Introduction

Pipelines have a set of settings that define a set of conditions, mostly when a message will be sent to the end-users.

By clicking on the Pipeline settings and choosing the "Scheduling" Tab, you should see the following form:

Pipelines help you send targeted emails to your end-users according to your business peculiarities (i.e average time of delivery, cancelled orders etc).

Pipeline Scheduling

Choosing the proper settings is what you need in order to achieve the best response rate but also not overwhelm your users with messages.

For this reason, you can setup a number of parameters for your Pipelines.

Start and End Time

Each pipeline has a starting and an ending date. This is when your messages will start and stop being sent to your users.

Start Time: Is by default the created date of the Pipeline
End Time: You can choose a specific date in the future to end your Pipeline or leave it blank to run indefinitely

For the Pipeline to be considered open and active, the End Time must either be set to a future date or left empty.

You can clear the End Time by clicking on the field and selecting Clear in the time picker that appears.

Language

Language is used to send messages and display questionnaires to your users. There are two options:

Auto Language Detection: Questionnaire language is adjusted to customers' web browser language.
Fixed Language: Select a specific language that your messages and your questionnaires need to be displayed to.

Dispatch Start and End Time

Define the hours between the questionnaires will be sent to the customers. You can use this option to avoid sending messages to your customers during inappropriate hours.

Messages outside this period are not ignored but are accumulated and will be sent during this period. For example, if a queue item has send time at 00:00, it will be send as soon as the dispatch start time is on.

NOTE: Times are in EST or EEST, whichever applies at the time.

Delay Cap

You can add a delay to displaying your questionnaire to your users, so that they have time to form their experience properly.

The delay cap is separated in 3 values: minutes, hours and days. You can set both values and the delay cap will sum up to the user.

Example: After the entrance on the online page the display of the questionnaire will follow in 1 day, 3 hours and 5 minutes.

Frequency Cap

You can use the frequency cap setting to avoid sending the same questionnaire to the same user multiple times in a given period of time.

The frequency cap is separated in 3 values: minutes, hours and days. You can set both values and the frequency cap will sum up to the user.

Example: After sending a questionnaire to a user, it will take 1 day, 5 hours, 35 minutes and the Delay Cap to be sent again.

Max Retry Attempts

Queue items might failed to be delivered for various reasons. Some of them might be:

Network issues
Host issues
Recipient information issues (this is not recoverable)

Each pipeline has a field called "Max Retry Attempts" where you can set a maximum number of attempts to retry to send a queue item, in case it failed. Default value is 3 but you can set whatever you need, although we suggest you keep it less than 10.

Pipeline Conditions

Apart from the targeting settings described in this article, you can also filter out queue items that match a set of given conditions based on questionnaire or responder metadata.

You can read more about Pipeline Conditions.

Page updated

Report abuse