![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1546940331633-workflows_start_event_EN.png\")
<\/p>\nStart event#<\/a><\/h4>\n<\/div>\nThe Start event<\/em> describes subscribers’ entry conditions to each work\ufb02ow. It is a required element to activate each work\ufb02ow. There can be more than just one Start event<\/em> in each work\ufb02ow, which allows to use the same marketing scenario for subscribers entering it due to different business reasons.<\/p>\nStart event<\/em> settings allow to specify when and which subscribers will enter the work\ufb02ow, as well as how to identify and handle duplicate subscribers.<\/p>\n\nHow to configure the start event?#<\/a><\/h2>\nTypes of the Start event<\/em>:#<\/a><\/h4>\n\n- Opt-in<\/strong> \u2013 a subscriber enters the work\ufb02ow upon opting-in to a list<\/li>\n
- Open\u00a0<\/strong>\u2013 a subscriber enters the work\ufb02ow upon opening a message<\/li>\n
- Click\u00a0<\/strong>\u2013 a subscriber enters the work\ufb02ow upon clicking a link inside a message<\/li>\n
- Goal\u00a0<\/strong>\u2013 a subscriber enters the work\ufb02ow upon completing a goal tracked by the email platform<\/li>\n
- Scheduled\u00a0<\/strong>\u2013 the work\ufb02ow will commence for selected subscribers at a speci\ufb01ed time\/date or upon prede\ufb01ned recurring schedule<\/li>\n
- Custom event<\/strong> \u2013 a subscriber enters the work\ufb02ow upon an API call triggering a prede\ufb01ned custom event<\/a>. Custom events must be prede\ufb01ned to appear on the selection list.<\/li>\n<\/ul>\n
List#<\/a><\/h4>\nSome types of start events require a subscriber list to be indicated. For example, the list is a required parameter for the Opt-in start event<\/em> type. This, combined with the type of the start event, indicates which subscribers will enter the work\ufb02ow.<\/p>\nSegment#<\/a><\/h4>\nAs with regular message types, Work\ufb02ows can be initiated not only for subscribers pulled from speci\ufb01ed lists, but also for subscribers de\ufb01ned by lists and segments. Segments use demographic or behavioral restrictions to narrow or broaden the scope of subscribers. In order to use them in a work\ufb02ow, they need to be prede\ufb01ned in the Subscribers\u00a0<\/strong>> Segments\u00a0<\/strong>section.<\/p>\nHandling duplicate subscribers#<\/a><\/h4>\nIn case the same subscriber matches the conditions to enter a work\ufb02ow, while still going through it due to a previous match, the user allows to determine how a duplicated subscriber should be handled.<\/p>\n
There are 3 options to choose from:<\/p>\n
\n- Create new instance<\/strong> \u2013 in this case the subscriber enters the work\ufb02ow again without affecting its earlier state in the cycle. The former instances proceed through the work\ufb02ow events, while another cycle starts for the subscriber upon meeting the entry criteria.<\/li>\n
- Ignore\u00a0<\/strong>\u2013 in this case the subscriber will NOT enter the work\ufb02ow again. The former instance proceeds through the work\ufb02ow events unaffected.<\/li>\n
- Move to start<\/strong> \u2013 in this case the subscriber enters the work\ufb02ow pipeline again, while his former instance gets reset.<\/li>\n<\/ul>\n
Data \ufb01eld used as an additional duplicate identi\ufb01er#<\/a><\/h4>\nBy default, an email address is used as the unique identi\ufb01er of a subscriber within a work\ufb02ow. It is possible to add at least one data \ufb01eld as an additional identi\ufb01er in order to distinguish a duplicated subscriber.<\/p>\n
When additional data \ufb01elds are set, the subscriber with the same email address and values of all speci\ufb01ed data \ufb01elds is treated as duplicate according to the Handling duplicate subscribers<\/em> settings.<\/p>\nThe only way to supply the value of data \ufb01elds is to start a work\ufb02ow using the Custom event API call<\/a>.<\/p>\nData \ufb01elds must be prede\ufb01ned for each work\ufb02ow before they can be used within it. Click Manage data fields<\/strong>, and choose Add new record<\/strong> or Add multiple records\u00a0<\/strong>to add new data fields:
\n![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1547037286149-workflows_adding_data_field_EN.png\")
<\/p>\n<\/div>\n\n
![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1546940363047-workflows_end_event_EN.png\")
<\/p>\nEnd event#<\/a><\/h4>\n<\/div>\nThis is a mandatory event that marks the end of the process for the subscribers that entered the work\ufb02ow. Once reached, it marks the work\ufb02ow as completed for a given subscriber and any data \ufb01elds that were associated with a subscriber are removed. It is possible to have multiple End events<\/em> set up within a single work\ufb02ow, which is especially handy with more complex work\ufb02ows.<\/p>\n![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1546941245700-workflows_send_email_EN.png\")
<\/p>\nSend email#<\/a><\/h4>\n<\/div>\nWhen a subscriber reaches this event in a work\ufb02ow, an email message is sent to that subscriber. The only setting of this event requires selecting a prede\ufb01ned email message<\/a>. To select an email message, it must not be in use within the same or other work\ufb02ows.<\/p>\n\n
![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1546940435126-workflows_send_sms_EN.png\")
<\/p>\nSend SMS\/MMS#<\/a><\/h4>\n<\/div>\nSend a predefined SMS or MMS message. Note that you may only use a message created as a workflow SMS\/MMS message, and, like with email messages, you cannot use the same message more than once.<\/p>\n
\n
![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1559313587315-workflow_events_web_push_EN.png\")
<\/p>\nSend Web Push#<\/a><\/h4>\n<\/div>\nSend a predefined Web Push notification. Note that you may only use a message created as a workflow Web Push message, and, like with email messages, you cannot use the same message more than once.<\/p>\n
![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1546940485196-workflows_api_call_EN.png\")
<\/p>\nAPI call#<\/a><\/h4>\n<\/div>\nThis event allows you to send an API call from within a workflow.<\/p>\n
\nHow to set up an API call?#<\/a><\/h2>\nNote that this option was created to enable accessing foreign\u00a0<\/strong>APIs, rather than the\u00a0<\/em>ExpertSender API<\/em><\/a>. If you need to send an ExpertSender API call from within the workflow, analyse what this call is expected to do and use another workflow event which achieves exactly that. In case of doubt, consult your Account Manager.\u00a0<\/em><\/p>\nTo configure an API call:<\/p>\n
\n- Click on the API call icon on the workflow diagram. You will see the configuration window.<\/li>\n
- Enter the Name\u00a0<\/strong>and Description\u00a0<\/strong>of the call.<\/li>\n
- Within an API call, select the request type:\n
\n- GET – to obtain data<\/li>\n
- POST – to create new data<\/li>\n
- PUT – to update data<\/li>\n
- DELETE – to delete data<\/li>\n<\/ul>\n<\/li>\n
- Enter the URL of the call (including query parameters, if relevant).<\/li>\n
- Under Header\u00a0<\/strong>you may add HTTP headers.<\/li>\n
- You may choose to save the response in a data field. Note that in order for a data field to be used within a workflow, it also needs to be created within this workflow. To create a workflow data field, click Manage data fields<\/strong>, and choose Add new record<\/strong> or Add multiple records<\/strong>.
\n<\/li>\n- You may also check if the API call returns a desirable response for a given email address. Under the Test Call<\/strong> heading enter any email address which belongs to one of your lists and click the Test Call<\/strong> button.<\/li>\n<\/ol>\n<\/div>\n
![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1546940518658-workflows_code_EN.png\")
<\/p>\nExecute Code#<\/a><\/h4>\n<\/div>\nThis event allows to run a piece of Dynamic Content code.<\/p>\n
\n
![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1546940583813-workflows_delay_event_EN.png\")
<\/p>\nDelay event#<\/a><\/h4>\n<\/div>\nThe Delay event<\/em> allows to temporarily prevent subscriber from advancing to the next event in the work\ufb02ow. There are three types of the Delay event<\/em>:<\/p>\n\n- Time-lapse<\/strong> – it halts the subscriber for the speci\ufb01ed amount of time (defined in minutes\/hours\/days\/weekdays\/weeks\/months)<\/li>\n
- Time-lapse with custom field<\/strong> – it halts the subscriber for a speci\ufb01ed amount of time that relates to a date\/time stored in the subscriber’s custom \ufb01eld (for instance, one week after the last login, or a month after the last purchase)<\/li>\n
- Specific date time<\/strong> – it halts the subscriber until the occurrence of a speci\ufb01ed date and\/or time<\/li>\n<\/ul>\n
\n
![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1546940602349-workflows_set_data_EN.png\")
<\/p>\nSet data#<\/a><\/h4>\n<\/div>\nIt allows to set or change a value of a custom \ufb01eld<\/a> of each subscriber reaching this event in the work\ufb02ow. Depending on the type of the custom field, there are following options:<\/p>\n\n- Set to constant<\/strong> – sets the field to a constant value, such as a predefined text (for fields with the Text\u00a0<\/em>type), number (for numeric fields) or True\/False (for fields of the Boolean\u00a0<\/em>type)<\/li>\n
- Increase by constant<\/strong> – increases the field value by a constant, e.g. adds 1 to the number of orders placed by the subscribers (option available for numeric fields only)<\/li>\n
- Decrease by constant<\/strong> – decreases the field value by a constant, e.g. subtracts 1 from the number of orders the subscribers can have a discount on (option available for numeric fields only)<\/li>\n
- Set to data field value<\/strong> – sets the field to a value provided in an API call which triggers the event<\/li>\n
- Increase by data field value<\/strong> – increases the field value by a value provided in an API call which triggers the event (option available for numeric fields only)<\/li>\n
- Decrease by data field value<\/strong> – decreases the field value by a value provided in an API call which triggers the event (option available for numeric fields only)<\/li>\n<\/ul>\n
\n
![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1546940623268-workflows_data_switch_EN.png\")
<\/p>\nData switch#<\/a><\/h4>\n<\/div>\nData switch<\/em> allows you to divide the stream of subscribers in a workflow into several branches, based on subscriber data. The Data switch<\/em> event allows to create between 2 and 10 branches, which are added or removed using the +<\/strong> and –<\/strong> buttons below the event on the workflow canvas. Each branch of the switch is assigned to one of the predefined segments<\/a> or Data Fields<\/a>.<\/p>\n\nHow are subscribers divided into branches?#<\/a><\/h2>\nTo get into a particular branch, the subscriber must fulfill the conditions of the corresponding segment. Since segments can intersect, the subscriber will fall into the first branch, to the segment of which he or she belongs. This means that the order of branches in the data switch matters.<\/p>\n
![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1547122333954-workflow_events_data_switch_ex_EN.png\")
<\/p>\n
In the example above, we divided our subscribers into three segments: those who clicked a life insurance offer, car insurance and home insurance. Of course, there may be subscribers who clicked two or all three insurance offers. However, our data switch establishes a hierarchy: each subscriber who clicked on life insurance falls into the first branch and is excluded from further analysis, even if he or she clicked car and home insurance.<\/p>\n
If the subscriber does not match any of the segments, it will go along the Default\u00a0<\/em>branch. This assures that none of the subscribers will “get stuck” inside the switch.<\/p>\n<\/div>\n![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1546940645135-workflows_winner_switch_EN.png\")
<\/p>\nWinner switch#<\/a><\/h4>\n<\/div>\nThe winner switch is an option which performs a split test of a message. It sends two (or more) versions of a message to selected test groups<\/em> of recipients in order to determine which of them is more effective (for example, which of them was opened more frequently). Then, the remaining subscribers receive the winner\u00a0<\/em>variant of the message.<\/p>\n\nHow to configure the winner switch event?#<\/a><\/h2>\nTo configure the winner switch event:<\/p>\n
Start event<\/em> settings allow to specify when and which subscribers will enter the work\ufb02ow, as well as how to identify and handle duplicate subscribers.<\/p>\n Some types of start events require a subscriber list to be indicated. For example, the list is a required parameter for the Opt-in start event<\/em> type. This, combined with the type of the start event, indicates which subscribers will enter the work\ufb02ow.<\/p>\n As with regular message types, Work\ufb02ows can be initiated not only for subscribers pulled from speci\ufb01ed lists, but also for subscribers de\ufb01ned by lists and segments. Segments use demographic or behavioral restrictions to narrow or broaden the scope of subscribers. In order to use them in a work\ufb02ow, they need to be prede\ufb01ned in the Subscribers\u00a0<\/strong>> Segments\u00a0<\/strong>section.<\/p>\n In case the same subscriber matches the conditions to enter a work\ufb02ow, while still going through it due to a previous match, the user allows to determine how a duplicated subscriber should be handled.<\/p>\n There are 3 options to choose from:<\/p>\n By default, an email address is used as the unique identi\ufb01er of a subscriber within a work\ufb02ow. It is possible to add at least one data \ufb01eld as an additional identi\ufb01er in order to distinguish a duplicated subscriber.<\/p>\n When additional data \ufb01elds are set, the subscriber with the same email address and values of all speci\ufb01ed data \ufb01elds is treated as duplicate according to the Handling duplicate subscribers<\/em> settings.<\/p>\n The only way to supply the value of data \ufb01elds is to start a work\ufb02ow using the Custom event API call<\/a>.<\/p>\n Data \ufb01elds must be prede\ufb01ned for each work\ufb02ow before they can be used within it. Click Manage data fields<\/strong>, and choose Add new record<\/strong> or Add multiple records\u00a0<\/strong>to add new data fields: \n This is a mandatory event that marks the end of the process for the subscribers that entered the work\ufb02ow. Once reached, it marks the work\ufb02ow as completed for a given subscriber and any data \ufb01elds that were associated with a subscriber are removed. It is possible to have multiple End events<\/em> set up within a single work\ufb02ow, which is especially handy with more complex work\ufb02ows.<\/p>\n When a subscriber reaches this event in a work\ufb02ow, an email message is sent to that subscriber. The only setting of this event requires selecting a prede\ufb01ned email message<\/a>. To select an email message, it must not be in use within the same or other work\ufb02ows.<\/p>\n \n Send a predefined SMS or MMS message. Note that you may only use a message created as a workflow SMS\/MMS message, and, like with email messages, you cannot use the same message more than once.<\/p>\n \n Send a predefined Web Push notification. Note that you may only use a message created as a workflow Web Push message, and, like with email messages, you cannot use the same message more than once.<\/p>\n This event allows you to send an API call from within a workflow.<\/p>\n Note that this option was created to enable accessing foreign\u00a0<\/strong>APIs, rather than the\u00a0<\/em>ExpertSender API<\/em><\/a>. If you need to send an ExpertSender API call from within the workflow, analyse what this call is expected to do and use another workflow event which achieves exactly that. In case of doubt, consult your Account Manager.\u00a0<\/em><\/p>\n To configure an API call:<\/p>\n This event allows to run a piece of Dynamic Content code.<\/p>\n \n The Delay event<\/em> allows to temporarily prevent subscriber from advancing to the next event in the work\ufb02ow. There are three types of the Delay event<\/em>:<\/p>\n \n It allows to set or change a value of a custom \ufb01eld<\/a> of each subscriber reaching this event in the work\ufb02ow. Depending on the type of the custom field, there are following options:<\/p>\n \n Data switch<\/em> allows you to divide the stream of subscribers in a workflow into several branches, based on subscriber data. The Data switch<\/em> event allows to create between 2 and 10 branches, which are added or removed using the +<\/strong> and –<\/strong> buttons below the event on the workflow canvas. Each branch of the switch is assigned to one of the predefined segments<\/a> or Data Fields<\/a>.<\/p>\n To get into a particular branch, the subscriber must fulfill the conditions of the corresponding segment. Since segments can intersect, the subscriber will fall into the first branch, to the segment of which he or she belongs. This means that the order of branches in the data switch matters.<\/p>\n In the example above, we divided our subscribers into three segments: those who clicked a life insurance offer, car insurance and home insurance. Of course, there may be subscribers who clicked two or all three insurance offers. However, our data switch establishes a hierarchy: each subscriber who clicked on life insurance falls into the first branch and is excluded from further analysis, even if he or she clicked car and home insurance.<\/p>\n If the subscriber does not match any of the segments, it will go along the Default\u00a0<\/em>branch. This assures that none of the subscribers will “get stuck” inside the switch.<\/p>\n<\/div>\n The winner switch is an option which performs a split test of a message. It sends two (or more) versions of a message to selected test groups<\/em> of recipients in order to determine which of them is more effective (for example, which of them was opened more frequently). Then, the remaining subscribers receive the winner\u00a0<\/em>variant of the message.<\/p>\n To configure the winner switch event:<\/p>\nHow to configure the start event?#<\/a><\/h2>\n
Types of the Start event<\/em>:#<\/a><\/h4>\n
\n
List#<\/a><\/h4>\n
Segment#<\/a><\/h4>\n
Handling duplicate subscribers#<\/a><\/h4>\n
\n
Data \ufb01eld used as an additional duplicate identi\ufb01er#<\/a><\/h4>\n
\n<\/p>\n<\/div>\n<\/p>\nEnd event#<\/a><\/h4>\n<\/div>\n
<\/p>\nSend email#<\/a><\/h4>\n<\/div>\n
<\/p>\nSend SMS\/MMS#<\/a><\/h4>\n<\/div>\n
<\/p>\nSend Web Push#<\/a><\/h4>\n<\/div>\n
<\/p>\nAPI call#<\/a><\/h4>\n<\/div>\n
How to set up an API call?#<\/a><\/h2>\n
\n
\n
\n<\/li>\n<\/p>\nExecute Code#<\/a><\/h4>\n<\/div>\n
<\/p>\nDelay event#<\/a><\/h4>\n<\/div>\n
\n
<\/p>\nSet data#<\/a><\/h4>\n<\/div>\n
\n
<\/p>\nData switch#<\/a><\/h4>\n<\/div>\n
How are subscribers divided into branches?#<\/a><\/h2>\n
<\/p>\n<\/p>\nWinner switch#<\/a><\/h4>\n<\/div>\n
How to configure the winner switch event?#<\/a><\/h2>\n
![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1547135138886-workflow_events_winner_switch_ex_EN.png\")
<\/li>\n![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1547136366087-workflow_events_winner_switch_window_EN.png\")
<\/li>\n![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1546940714707-workflows_distribution_EN.png\")
<\/p>\n![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1547473080526-workflow_events_distribution_switch_EN.png\")
<\/p>\n![](\"https:\/\/help.expertsender.com\/wp-content\/uploads\/2024\/03\/1546940742243-workflows_comment_EN.png\")
<\/p>\n