Basic concepts

Each journey has an audience component

When designing a journey always link an audience component after the Start component. For blasts it determines the audience (selection). For pages and forms usually the entire audience list is set as a selection. It  determines where to store the data.

Different Scheduling types depending on type of journey

A blast journey executes the journey only once, for all the contacts in the audience. This type of journey uses a single shot scheduling type and needs to be executed (started, stopped, paused). After execution the journey is automatically put on hold.

Non-blast journeys, e.g., forms only, do not need to be activated or scheduled.  

Journeys contain multiple components.

 It is a path the contact follows. When creating journeys take the contact’s point-of-vue.

A story/campaign is split up in different journeys.

Often a campaign is built from multiple journeys interacting with each other.

For instance, a journey that sends out an email with a form that needs to be filled out, a storage of data and a thank you. Contacts not reacting on the email can be sent to a Reminder journey for instance to follow up on them.

Links between journeys can be made in different ways. One is a Redirect component, another one is using a sensor that when clicked redirects the contact to another journey.

What if other data besides the audience list is required

Several components are available. Lookup component to search for info in other lists, or load the profile extension in the audience list itself.

Anonymous versus known profiles.

Although messages can only be sent to known contacts, it is possible to engage with anonymous contacts through forms, surveys or pages.

The webpage or form can be made accessible online (e.g. on the website) for unknown persons (anonymous profiles) by using the Selligent Campaign webpage or form’s URL as a hyperlink.
But the webpage or form’s content can also be integrated in your website, for known contacts or anonymous profiles. Selligent offers a server-side content integration called “content rendering”. The Selligent Campaign webpage or form’s content can be retrieved as data and merged with your existing website(s) pages. The client’s website development team decides where on the website page the Selligent Campaign content should appear. Selligent provides a library with classes and methods to integrate the content in your website.