The ‘Start on Event’ object specifies the starting point of a campaign path. Unlike the ‘Start on Time’ object, the starting point is not determined by a predefined time, but by when an event occurs. This could be a ‘Bounce’ from a QuickMail or an ‘Unsubscribe’ process started when a contact clicks on ‘Unsubscribe’.

The ‘Start on Event’ object can also be used to activate a campaign path on the basis of a form not defined in Deployteq, but defined on the contact’s website. The object can read the values from the form and make them available within the campaign, so that they can be processed in Deployteq.

The ‘Start on Event’ object will become the default starting point of a campaign when a ‘Bounce’ or ‘Unsubscribe’ process is created using the Campaign Designer.

The ‘Start on Event’ object has a URL. When you place a form with an iframe on your website, it is best to use the URL of this start object. This is because it does not change, even though you may use a different page or want to perform an extra action before the customer arrives at the landing page.

In addition, you can set variables that can be saved as part of environment variables. These can be enclosed with the URL.

Give the object a name and configure the start time. If you choose ‘Campaign Start’, the path will be activated as soon as the campaign goes live.

If the start date is changed in the campaign settings, the start date for the path will also change. For ‘Static’, you must enter a set date and time.

This can also be at a time after the campaign has already started.

You then configure the repeat interval and, if desired, specify an end date for the interval.

No configuration is necessary for this object.

User-defined campaign objects

This object makes it possible to link the flow to the ‘Callcenter’ campaign within a campaign.

This object is a user-defined campaign object that you can configure as you wish. Customers pass through this object and are exported to your customer service department at a specified time. In this campaign object, you can configure which fields you want to have exported and at what interval.

• Continue
• End object

This object makes it possible to link the flow to the ‘Printer’ campaign within a campaign.

• Continue
• End object

The Page object makes it possible to display a webpage from Deployteq.

• On submit (if page has been sent)

• Continue
• On bounce (if e-mail bounces)
• On click (if click takes place in the e-mail)
• On open (if e-mail is opened)
• On complaint (if complaint is submitted)

• Continue
• On bounce (if SMS has been bounced)

• Continue
• On fail
• On success

The ‘Get Data Model Record’ object selects a row from the data model.

Only the contact selected from the flow is used as a source. This object examines all the contact’s data model rows and ignores rows that may previously have been selected from the flow.

In ‘Table’, you can specify which table to retrieve a row from.

The columns in the table are made available as environment variables within the flow.

The names of the variables are displayed in the overview.

• Continue
• On record found
• On record not found

Specify the source: all contact data or only data from the current selection.

In ‘Table’, you can specify the table for which a flow should be started for each record.

• Continue
• For each

The contacts from the flow are used as a source. This object examines all the contact’s data model rows and ignores rows that may previously have been selected from the flow.

In ‘Table’, you can specify the table in which to modify the rows. Once a table has been chosen, a value can be specified for each column.

If you choose a table that hangs ‘underneath’ another table, you will first need to specify which row in that table should be chosen to add the underlying row to.

• Continue

The contacts from the flow are used as a source.

This object examines all the contact’s data model rows and ignores rows that may previously have been selected from the flow.

In ‘Table’, you can specify the table from which a row should be sought.

The columns in the table are made available as environment variables within the flow. The names of the variables are displayed in the overview.

• Continue
• On customer found
• On customer not found

The contacts from the flow are used as a source. This object examines all the contact’s data model rows and ignores rows that may previously have been selected from the flow.

In ‘Table’, you can specify the table in which to modify the rows. Select the column to be modified and the corresponding value, and then underneath the condition for selecting the row.

• Continue

The contacts from the flow are used as a source. This object examines all the contact’s data model rows and ignores rows that may previously have been selected from the flow.

In ‘Table’, you can specify the table from which to delete the rows. Filters can be used to select specific rows from that table.

• Continue

• Continue
• Clicked
• Not clicked

To determine whether one of more customers have opened (or not opened) the e-mail.

• Continue
• Opened
• Not opened

To determine whether an e-mail sent to one or more customers has bounced.

• Continue
• Bounced
• Not bounced
• Hard bounced
• Soft bounced

The ‘Apply Condition’ object sets a condition with which a fork in the path can be created.

A group of contacts that fulfils the condition follows a different path from the group of contacts that does not fulfil the condition.

Different follow-on objects can be defined for each of the two groups.

• Continue
• On match (fulfills conditions)
• On fail (does not fulfill conditions)

The 'In Profile' object essentially functions the same as the 'Apply Condition' object. However, it checks if someone meets the conditions set in a profile.

It's important to specify when not to use it. The In Profile-object is not used to initiate a mailing. It does not select contacts within Deployteq.

You select the profile that someone needs to meet. This could be used, for instance, if someone completes a form (you have no control over the selection). You use the profile to check whether someone has placed an order in the past month and continue the flow based on the answer.

• Continue
• On match (matches conditions set in profile)
• On fail (does not match conditions set in profile)

• Continue
• Other
• Custom Created Links

• Continue

• Flow names as configured in the object

• Continue

• Continue
• On time (once timer has run down)

Specify how many customers are allowed to pass through this object per hour, day, week, or month. You can then specify the days on which e-mails may be sent. Finally, you can also specify times between which e-mails may be sent, so that, for instance, your customers are not sent e-mails in the middle of the night by an automated process.

The ‘Continue’ exit will be used until the limit is reached. A signal is sent when the limit is reached and you can search for yourself via the ‘Limit has been reached’ exit to send yourself a notification e-mail. The customers who you can no longer send an e-mail to once the limit has been reached are directed through the ‘Past limit’ exit. These people can be placed in a group that is added to the flow again the next morning when the limit is reset.

• Continue
• Limit has been reached
• Past limit

The possibility to export records that have entered a specific flow in a campaign. For example, you could export all bounced records daily so that they can be followed up by your customer service department.

Place a 'Bucket' object in front so that you can collect the customers first before exporting them, otherwise an export will be performed per customer.

• Continue

This campaign object is used to configure an import as you are used to doing, but now the campaign will only continue once the import has finished. This object imports customers and select these customers within the campaign. Use the data model objects to perform a data model import.

You can also use these objects in succession.

• Continue
  • This exit contains all new and updated customer records
• New customers
  • This exit contains all new imported customer records
• Modified customers
  • This exit contains all updated customer records
• On fail

You can unsubscribe a customer for:

• Active Campaign: unsubscribe a contact from the current campaign.
• All Future Mailings: unsubscribe a customer from all e-mail batches by setting Opt-in (e-mail) to ‘No’.
• All Future SMS Batches: unsubscribe a customer from all SMS batches by setting Opt-in (SMS) to ‘No’.

• Continue

This object can be used to modify customer data. This may be done in response to a customer action (e.g. clicking in an e-mail updates a field) or to add environment fields (e.g. a temporary value from an API call) to your contact database.

First give the object a name. Choose the field to which the new data should be added. Choose the ‘Fixed’ context value option, enter the value or environment (the value from this environment field), and select the environment field.

These values will be added to the selected database field for all customers that go through this object.

• Continue

This object is used to identify a contact based on specific customer fields. The object searches your contact database for contacts that meet your specified criteria.

Give the object a name. Then select a customer field or customer option field from the list of fields. Now select an environment field in the drop-down menu.

The data from the customer database is now compared with the data from the environment field. You can specify multiple conditions.

• Continue

Similar to the ‘Add customer’ object, it is possible to add customers that enter a campaign via a ‘Start on Event’ or ‘Start on SMS’ to the database.

However, this object immediately assesses whether it is a new or existing customer record. It is also possible to deduplicate on the basis of one or more fields to prevent a contact from being included in the database several times.

In ‘System field’, you choose which Deployteq field you want to update and in ‘Context value’ you specify whether this value should be a fixed value or an environment value. Tick ‘Unique’ for the field on which deduplication should be based so that a check is made to see whether that field already exists in the database.

• Continue
• Existing customer
• New customer
• New and existing customer

The ‘Add customer’ object is used to add a contact to the contact database. Under normal circumstances, contacts are added to the database by means of an import or subscription form.

It is also possible to add contacts, which enter a campaign via a ‘Start on Event’ or ‘Start on SMS’ object, to the database. No deduplication will take place, but you can use the ‘Find customer’ object to check whether a contact already appears in the database.

On this basis, appropriate follow-up actions can be carried out. The default (e-mail) Opt-in value is ‘Yes’, while the default (SMS) Opt-in value is ‘No’.

Give the object a name. You then specify which (environment) variables should be saved in which customer fields. You can, for example, save an e-mail address from a URL parameter in a customer field belonging to this new record.

It is a good idea to place a ‘Find customer’ object in front so that you only add customers that do not yet exist and only modify other customers.

• Continue

The ‘Remove customer’ object can be used to delete a contact from the database. This is useful if you only want to keep a contact in your database temporarily (e.g. for Forward-to-a-friend campaigns).

This action cannot be undone.

By default, this object deletes customers in a single customer flow only. In the settings you can choose to delete several customers simultaneously.

• None

This object is used to select a group of contacts based on the current campaign, profile, or group. The group that is selected proceeds to the next step in the campaign.

Enter a name for the object. Then choose whether you want the selection to be made on the basis of the current campaign, a group, or a profile. If you opt for a group or profile, select the desired group or profile in the file manager. 

You can choose from all groups and profiles that were created in the 'Profiles' and 'Groups' components in Deployteq. In the CRM, you can make contacts members of a campaign, such as for an import.

• Continue

• Continue

You can delete selected contacts from a group in the campaign.

• Continue

Use this object to easily capture the customer selection in a campaign and store it in a group.

After dragging the object into your campaign, you can customize its name. Then, you select the desired group to be synchronized. You can choose from all groups created in the 'Groups' section of Deployteq.

The object before the 'Sync to Group' object in the campaign flow should be the 'Select customers' object. With this object, you select a group of relationships based on the current campaign, profile, or group. The group selected moves on to the Sync with Group step.

• Continue

• Continue

Global Environment

This object makes it possible to insert temporary variables throughout the path, which only apply inside the campaign.

This object can be used, for instance, as a counter within a path.

First give the object a name. For the field name, select an existing environment field or enter a new name to create a new field.

In ‘Field Option’, select the type of action. Then define the field value, such as ‘Counter’ (field name) ‘increase by’ (field option) ‘1’ (field value). The object will now ensure that the counter is increased by 1 for every contact that passes the object.

Elsewhere on the path, the counter can be reused in a condition, e.g. ‘Counter’ (field) ‘is’ (condition) ‘500’ (fixed value). The contact that makes the counter tick over to 500 fulfils this condition.

• Continue

Private Environment

The ‘Private Environment’ object is virtually similar to the ‘Global Environment’ object. The difference is that ‘Private Environment’ only applies to active users.

It allows you to define variables at individual level that you can reuse further on in a campaign path to link conditions, for example, or to save specific values to customer records.

In a private environment, you can also first give the field a name. You then specify what you want to do with this field. Again, you can enter a value, increase or decrease, or enter a value before or after.

However, in a private environment, this will be a personal value. Whereas a counter is used for the entire campaign in the global environment, here you can count how many times a person has passed through a specific flow. For example, a person is allowed to receive a reminder twice. You increase the counter to 1 after sending the first reminder and then increase by 1 again after the second reminder. The condition then checks whether the counter is greater than 1. If it isn’t, the customer is allowed to receive another reminder and if it is, the customer will leave the flow. The customers who are in the flow can all have a different value in their private counter.

• Continue

Bucket

This is used to collect customer records in a campaign flow and is often used to export customers in the campaign flow. In this way, you don’t have to create an export for each customer who goes through the flow.

• Continue
• Threshold reached

Extract Value

When you have JSON code in an environment variable or customer field, this is normally read out as text, which means that you cannot do much with the values in your JSON code. This object can be used to save the values in your code as separate elements in a field or as a separate environment variable.

• Continue
• On success
• On fail

Landing Page

This object makes it possible to direct users to an external page, e.g. a page on your website, based on a specified URL.

You have the option to use GET variables to enclose customer data in the URL of the external page.

• Continue

• Continue
• On match
• On fail

Set Error

You can enter an error message in the campaign. This is used, for instance, for a login process when the authentication fails.

• Continue

Confirm Relation

The ‘Confirm Relation’ object confirms the relationship between two persons, brought about, for example, by a Forward-to-a-friend form. 

This confirmation follows automatically when, in the case of the Forward-to-a-friend form, the e-mail sent to the subscribed friend is clicked on.

• Continue

Import From URL

When the webhook is configured in the store, the "Import from URL" object becomes available. With this object, you can retrieve and process an XML, RSS, or JSON feed through a webhook into the datamodel.

This object allows you to, for example, store a product feed in the data model so that it can be easily used in your content.

Because this data is stored in the datamodel, you also benefit from the maximum delivery speed compared to the solution where a feed is fetched when rendering an email (Datafeeds app).

The only downside of this object is that you can't use a personalised feed.