Automating customer life cycle from the moment of registering\/signing up until conversion and further is a challenge for every marketer. The Work\ufb02ows feature facilitates this process. It allows to build marketing automation scenarios that execute according to the prede\ufb01ned sequence of events. Its easy-to-use interface include interconnected drag&drop elements that help to set up and visualize the logic behind each marketing scenario.<\/p>\n\n\n\n
A Work\ufb02ow is a visual scenario that consists of a series of events. Those events form a sequence that describe what will happen to each subscriber that goes through a particular work\ufb02ow.<\/p>\n\n\n\n
There may be multiple work\ufb02ows de\ufb01ned in each business unit. Many work\ufb02ows may also run at the same time.<\/p>\n\n\n\n
Each work\ufb02ow needs to have a Start event<\/em>. It de\ufb01nes which subscribers will be selected to go through the work\ufb02ow. Subscribers enter the work\ufb02ow whenever they match the settings from the Start event<\/em>. This means that there may only be a few subscribers or a big number of subscribers going through the work\ufb02ow at any given time, depending on the type of the Start event<\/em>. Please refer to the Workflow events<\/a> section for more details about the Start event<\/em>.<\/p>\n\n\n\n Note that it is possible that one subscriber may be processed by multiple work\ufb02ows at the same time provided that there is a match for multiple Start events<\/em> in more than one work\ufb02ow.<\/p>\n\n\n\n Each work\ufb02ow may have one of the following statuses:<\/p>\n\n\n\n The building blocks of each work\ufb02ow are units called events. Each event indicates an activity or a decision point within a work\ufb02ow. Event in the work\ufb02ow needs to be connected with at least one other using arrows in order to indicate the sequence in which they should execute. There needs to be at least one Start event<\/em> and at least one End event<\/em> within each work\ufb02ow.<\/p>\n\n\n\n Each event can have a name that is visible on the work\ufb02ow canvas as well as a longer, initially hidden, description for the reference of a marketer. There are 9 types of events<\/a> that can be used within a work\ufb02ow.<\/p>\n\n\n\n One of the most important purposes of work\ufb02ows is to send the right message (email, sms, Web Push, or even a third-party type of message) at the right time. Only a special type of email and SMS messages can be used within work\ufb02ows. Workflow email messages need to be prede\ufb01ned using the Create work\ufb02ow email message<\/strong> button under the Work\ufb02ows <\/strong>> Email Messages <\/strong>menu, whereas workflow SMS\/MMS need to be set up with Create workflow SMS\/MMS message<\/strong> under Workflows <\/strong>> SMS\/MMS Messages<\/strong>.<\/p>\n\n\n\n It is possible to use particular message only once within any of the created work\ufb02ows. The work\ufb02ow that is using a particular message is indicated on the work\ufb02ow messages list. Only active messages that have no work\ufb02ow assigned can be used for Send events<\/em>. To learn more, consult the Workflow email messages<\/a> section.<\/p>\n\n\n\n It is possible to start work\ufb02ows on demand using an API call. This feature is useful for re\ufb02ecting user interactions with the brand on the website (such as an abandoned shopping cart) or at any other touch point (such as swiping the loyalty card at the cashiers desk) in order to start a corresponding marketing automation scenario within the multichannel platform. <\/p>\n\n\n\n Each custom event is triggered for one subscriber at a time. The custom event API call may include additional data \ufb01elds that will be available within work\ufb02ows for the duration of each work\ufb02ow scenario the subscriber participates in.<\/p>\n\n\n\n One custom event may be used to trigger multiple work\ufb02ows at the same time. <\/p>\n\n\n\n To learn more, consult Working with Custom events<\/a>. Please also refer to the API documentation for more information about triggering Custom events<\/a> through API.<\/p>\n\n\n\n Data \ufb01elds provide a solution if there is a need to add additional information about the subscriber to the marketing automation scenario.<\/p>\n\n\n\n Data \ufb01elds are placeholders for short-lived, work\ufb02ow-speci\ufb01c details. Data \ufb01elds may be the perfect way to store the order id, a parcel tracking number or other similar information.<\/p>\n\n\n\n The values of data \ufb01elds may be provided within the Custom events<\/em> API call and can be accessed by any work\ufb02ow that make use of data \ufb01elds with the same name and type. The values of data \ufb01elds may also be used within the email messages using personalization tags or Dynamic Content<\/a>.\u00a0<\/p>\n\n\n\n Data \ufb01elds can also be used to distinguish instances of the same subscriber in the same work\ufb02ow from each other. For example it is possible to distinguish subscriber instances based on the value of an OrderID<\/em> data \ufb01eld. Each time a subscriber with the same email address will complete another purchase, while still being in a sales completed<\/em> work\ufb02ow from a previous purchase – a new, separate instance of that subscriber may enter the same work\ufb02ow from the very beginning, but with a different OrderID.<\/p>\n\n\n\n Data \ufb01elds are automatically discarded once the subscriber associated with them \ufb01nishes all work\ufb02ows using those data \ufb01elds.<\/p>\n\n\n\nWorkflow statuses#<\/a><\/h2>\n\n\n\n
\n
Events#<\/a><\/h2>\n\n\n\n
Messages#<\/a><\/h2>\n\n\n\n
Custom events#<\/a><\/h2>\n\n\n\n
Data fields#<\/a><\/h2>\n\n\n\n