Specific journeys

Targeting and retargeting journeys

These journeys are used in combination with Site. With targeting journeys, Campaign pages can be used to fill out placements on the website. A targeting journey typically has an input component, referred to from within Site. The page in the journey is the content to be displayed on the website. Note that the journey properties must be set to Targeting journey and the scheduling is set to single shot. The journey does not need to be activated

A Retargeting journey allows following up on Site contacts that have or haven't converted on an offer. Retargeting is based on action records in an action list that triggers an execution for specific action codes. These action records are created automatically when Site triggers the Retargeting journey. If input parameter values are passed on from Site, they are automatically stored in the action list and can then be used to personalize the message. The input component is used to send contacts from Site to the journey. It uses a parameter and depending on the parameter, the contact arrives in the first or the second input component.

Emails in Retargeting journeys are set to instant. The journey is set to single shot and does not need to be activated.

BMP journeys

This is a basic example on how to use the BPM components. BPM stands for "Business Process Management", i.e. life cycles. A BPM journey defines the states the contact can be in, the states are stored in a BPM list. A global customer life cycle for instance, with states "welcome, retention, loyalty, etc.".

Typically, a Welcome Stream is a series of messages that introduce a brand or an idea and inspire first purchase. The first touch will be a Welcome offer. If the contact does not purchase after three days, they will receive a reminder about our new products. If no purchase is made after seven days, the contact will receive a "don't miss out" email that could be about hot trends for back to school or any other calendar event. If the contact made a first purchase, they are re-routed from the Welcome stream and diverted to the First-purchase Life Cycle.

 

 

Interfaces

Interfaces are mini-modules that allow interaction between Selligent and external software. For example, defining integrations with an SMS-software (allowing e.g. The-marketing, Call-center follow-up …. There are Plugin Interfaces which use a custom DLL called “plug-in” to manage interactions with the external software. A specific plug-in is created for each external tool. It mainly concerns interfaces with a low amount of data transferred regularly such as The. And there are File Interfaces which create directly their data on the specified location such as a FTP server, email attachment... Those interfaces do not require a specific plug-in and are used to transfer a huge volume of data at a defined moment (typically for bulk export).

Following is an example of a multi channel journey, using File interfaces to print birthday wishes and Plugin based interfaces for sending sms messages.

 

Filling Site audiences with Selligent Contacts in an Offer journey

Sometimes you want identified contacts to be included in the audience of an offer based on a trigger in a journey. This component allows to do exactly that. Use a contact interaction such as a click in an email, an answer in a survey, a submit of a registration, etc as a trigger to include the individual contact in a specific active target offer. At the same time this implies that the offer component cannot be used for sending contacts in bulk to the offer audience.