Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

Conditions are what determine the stage of the user within a sequence at any point in time of a campaign and allow for personalization of the message based on user behavior. Stories are delivered based on conditions fulfilled by the user.

Here is how: At the start of the campaign, the audience wouldn't have fulfilled any condition yet. The Journey Designer will therefore trigger the story at the first stage of the sequence. Each action of the audience on the stories (interactions with widgets, CTAs, videos, etc.) would then be registered by the Journey Designer and checked against the conditions set in the sequence. According to the conditions fulfilled by each single user, the Journey Designer is able to understand at what stage of the sequence the user is and serve them the most appropriate story.

Each If then Else or Switch block must contain a set of conditions.

There are two main types of conditions that can be used in each sequence. User interactions conditions and browsing history conditions. The first ones are calculated based on users behavior on the ads, while the latter are based on users browsing behavior on whichever properties Connected-Stories tags are placed.

User Behavior Conditions

  • Widgets (Poll or Quiz)
    • These conditions determine what stage the user is based on the answers provided on the quizzes or polls.


  • Video View %
    • This condition determines what stage the user is based on what percentage of a video has been see.


  • Random Boolean
    • This condition allows to run A/B tests between stories at each stage of journey (It can only be used within If Then Else blocks).

  • Custom.Text
    • This condition determines what stage the user is based on a click on a widget. Clicks can be differentiated by adding a Key Value on the widget itself and then reporting it as a key value to be matched when setting the condition.  A True or False needs to be applied as a qualifying statement when creating the block itself for the action.


Browsing Behavior Conditions

These types of conditions are frequently used for remarketing campaigns and allow the journey designer to define a sequence based on the browsing interests of each single user.

  • Remarketing.OG.Description
    • This condition checks whether the user has browsed a webpage where the OG (Open Graph) description within the HTML code of the page contains a specific set of words.
  • Remarketing.Description
    • This condition checks whether the user has browsed a webpage where the description within the HTML code of the page contains a specific set of words.
  • Remarketing.Keywords
    • This condition checks whether the user has browsed a webpage where the keywords within the HTML code of the page contain a specific set of keyowrds.
  • Remarketing.OG_Image
    • This condition checks whether the user has browsed a webpage where the image url on the Open Graph schema within the HTML code of the page contain a particular image url.
  • Remarketing.OG_Title
    • This condition checks whether the user has browsed a webpage where the OG (Open Graph) title within the HTML code of the page contains a specific set of words.
  • Remarketing.Query_String
    • This condition checks whether the user has browsed a webpage where the query string (all parameters after the ? in the url) contains a specific set of parameters.
  • Remarketing.Referral
    • This condition checks whether the user has browsed a webpage reffered by a specific source.


  • Remarketing.URL
    • This condition checks whether the user has browsed a webpage linked to a specific url.


  • No labels