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 7 Next »

As previously explained for the Journey Designer (click here if you don’t know what we’re talking about), C-S Storyboard conditions allow to make widgets within a story more dynamic.

How they work

  1. The Storyboard allows to create a sequence of widgets within a single story of your campaign;

  2. Each action the user does on the story (interactions with widgets, clicks on the video…) would then be registered by the Storyboaard and checked against the conditions set in the sequence;

  3. According to the conditions fullfilled by each single user, the Storyboard is able to understand at what stage of the sequence he or she is and will serve him/her the most appropriate widget at the next impressions.

In the storyboard conditions are represented by blue (If the Else) and light blue (Switch) boxes which must contain a set of conditions each.

Following you can find a list of all the Storyboard's conditions offered by Connected-Stories which are similare to the Journey Designer’s ones and work in the same way:

User Device Conditions:

  • Country

  • Device

  • Language

  • Network

  • Os Type

User Date / Time Conditions:

  • Date 

  • Day of the Week

  • Time

User Behavior Conditions:

  • Widgets (Poll or Quiz)

  • Video View %

  • Random Boolean

  • Custom Text

Campaign Macros:

  • DV360

 User Device Conditions

  • Country: This condition determines the country from where the user is seeing the ad. It is possible to select every world's country and, depending on the place he or she is in a specific moment, will be shown different widgets.

<< Back to the Condition’s List

  • Device: This condition allows to show the user different widgets depending on the device the user is watching the ad from (desktop, mobile, tablet, TV).

<< Back to the Condition’s List

  • Language: This condition determines which language the user speaks and consequently he or she will see a personalized widgets with texts or audio elements in the same language (English, Spanish, Italian, French...).

<< Back to the Condition’s List

  • Network: With this condition the user will see a different widget depending on the network he or she is using (4G, 5G, WiFi...).

<< Back to the Condition’s List

  • OS Type: This condition will show users a different widget depending on the Operative System they're using (Android, iOS, Linux...).

<< Back to the Condition’s List

User Date / Time Conditions

  • Date: This condition determines which widget to show to the user depending on the the single date or multiples dates set into the Storyboard.

<< Back to the Condition’s List

  • Day of Week: This condition determines which widget the user must see each day of a single week or multiples weeks. (I.e. each Monday he or she an interactive ad, each Thursday a new one and so on).

<< Back to the Condition’s List

  • Time: This condition determines which widget has to be shown to the user depending on the day's time (i.e. if it's morning he or she will see a dedicated content and if it's night the user will see a different one).

<< Back to the Condition’s List

User Behavior Conditions

  • Widgets (Poll or Quiz): These conditions determines the user's stage based on the answers provided on a quizz or poll.

<< Back to the Condition’s List

  • Video View %: This condition determines the user's stage based on what percentage of a video has seen (25%, 50%, 75%...) and will show him or her a different widget depending on that percentage.

<< Back to the Condition’s List

  • Random Boolean: This condition show the user different widgets in a random way. This one is also useful to run A/B tests between widgets to see which one has been triggered the most by the user.

<< Back to the Condition’s List

  • Custom.Text: This condition determines what stage users are, based on the clicks they've done on one or more widgets. These clicks can be differentiated by adding a Key Value when setting up a widget which will be also 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.

<< Back to the Condition’s List

NEXT STEP: Simulator >>


  • No labels