How does the journey builder work?

The entry node is the starting point of the journey. The node looks like this:

Profiles are added to the journey in this node when they meet the requirements of your journey settings. Read more about this in the article: Journeys. By clicking on the entry node you open the settings. After the entry node profiles go directly to the next node in the journey.

The exit or goal node is the end point of the journey. The node looks as follows:

Goal node

Exit node

Profiles are removed from the journey in this node. In the node you can choose between exit node or goal node (by checking goal is reached):

Profiles ending in a goal node can be added to a goal audience. Based on all goal nodes in a journey, the conversions of the journey are measured. In the statistics of the journey (see journey overview) you can see the profiles that have left via a goal node as Completed:

Profiles that have left the journey via an exit node are listed as Exit and are not added to the goal audience. The goal audience do you set-up in the settings of the journey. The goal audience can be directly synchronized to external channels.

 

An email node allows you to trigger an email template in your Email Service Provider (ESP). The node looks like this:

For applying an email node an Email Service Provider needs to be connected, for more information:

• Mail+ 
• Deploytec
• MailCampaigns
• MailPro (Webpower/Tripolis)
• Copernica
• Klaviyo
• Pure360
• Mailchimp (limited linking)
• Mailjet

In the email node you can set the following:

• Node title: the name of the node in the journey
• Limit: a (possible) limit to the number of times the node can be triggered. When a profile exceeds the limit, the profile goes to the Reminders in the journey.
• Required consent: the consent needed for triggering the email template in the ESP. When a profile does not have the required consent, the profile goes to the Remainders in the journey.

A messaging node allows you to trigger a web push notification in the browser. The node looks like this:

To apply a messaging node web push must be activated for your account. The activation of web push can be requested at sales@squeezely.tech. For more information see Add on Features.

In the messaging node you can configure the following:

• Node title: the name of the node in the journey
• Image Url: an image (if any) which is shown in the web push
• Icon Url: an icon (if any) to be shown in the web push
• Title: the title to be shown in the web push
• Body: the body to be displayed in the web push
• CTA url: the link behind the Call To Action in the web push
• CTA text: the text of the Call To Action of the web push

An audience node allows you to add or remove a profile from an audience. The node looks like this:

In the audience node you can set the following:

• Action
  • Add to audience: add profiles to the audience
  • Remove from audience: Remove profiles from the audience
• Audience: Select an existing audience or create a new audience to which the above action is applied
• Channels: synchronize the audience to certain channels

A webhook node allows you to send profile data via an API call to an external URL. The node looks like this:

In the webhook node you can set the following:

• Method: the method to request, send or update data
• URL: the URL to which the method is applied
• Content-Type: the type of content of the API call
• Auth: the authentication (if any)
• Request Headers: the headers of the request
• Extra fields: the Spotler Activate fields (if any)

Note: Setting up a webhook requires specialist knowledge. Consult a person with knowledge of API calls for the application of this node.

 

An update profile node allows you to update profile fields of profiles. The node looks like this:

In the update profile node you can set the following:

• Node title: the name of the node in the journey
• Field: the profile field that should be updated
• Value: the value in the profile field that must be updated

A notification node allows you to send an email to one of the Squeezely users. The email includes a link to the relevant profile that triggered the node. The node looks like this:

In the messaging node you can set the following:

• Subject: the subject of the e-mail
• Image Url: the recipient of the e-mail. 

 

A wait node holds profiles for a certain time before the profile moves to the next node. The node looks like this:

In the wait node you can set the following:

Wait period: the period the profiles wait in the node

A wait until node holds profiles until the selected date, before the profile moves to the next node. The node looks like this:

Choose between the following options in the wait until node:

• A date: The profiles wait until a certain date
• A contact property: The profiles wait until a certain profile or event field, where possibly:
  • Days are subtracted from the certain date
  • Days are added to the given date

Example: If you select the option a contact property with the field birthdate and subtract one day, profiles will move to the next node in the journey one day before their birthday.

Date already past? When a profile has reached the Wait untill node and the chosen property for that profile is already in the past, the profile will go to the Remainder brench. For the birthday field, we use the upcoming birthday, so you will rarely fill the Remainder branch.

An A-B split node randomly partitions profiles into one of the outgoing streams. The node looks like this:

In the A-B split, you can set the following:

• Percentage: the percentage distribution of profiles between the outgoing flows

Percentage: the percentage distribution of profiles between the outgoing flows

You can set the following in the visitor split:

• Node title: the name of the node in the journey
• +: the plus sign enables you to add an extra path
• Title: the name of the continued path
• Select filter: the filter to which the split is applied

An audience split node splits profiles into two streams based on any participation in the selected audience. The node looks as follows:

In the audience split you can set the following:

• Node title: the name of the node in the journey
• Audience: the selected audience, with:
  • Participation the profile goes to the yes stream
  • No participation the profile goes to the no stream

A product split node checks the product fields of the product with which the profile entered the journey. The node looks like this:

In the product split you can set the following:

• Node title: the name of the node in the journey
• Wait time: the period in which the product fields are checked:
  • If the criteria are met the profile goes to yes
  • Not meeting the criteria within the set period the profile goes to no
• Product criteria: the criteria of the product fields of the product from the entry event

A teleport node moves profiles from the first teleport node to the second teleport node. There are always two of the teleport nodes, which look like this:

When you stand on one of the nodes you can see which one is the second teleport node by the blue frame.

An engagement split node splits profiles into two streams based on certain interactions of profiles. The node looks like this:

In the engagement split you can set the following:

• Node title: the name of the node in the journey
• Engagement period: the period in which certain engagement is measured, when:
  • Engagement takes place the profile goes directly to the yes stream
  • If no engagement takes place the profile goes to the no stream at the end of the engagement period
• Select filter: the filter to which the split is applied