3 Conditional logic

00:00:04.400 –> 00:00:06.400
Hello there, welcome back. In this step,

00:00:06.400 –> 00:00:08.240
we are looking at conditional branching

00:00:08.240 –> 00:00:10.440
logic, which is where the next branch

00:00:10.440 –> 00:00:12.880
shown to your audience depends on a

00:00:12.880 –> 00:00:15.600
condition that you set being met or
>
00:00:15.600 –> 00:00:18.560
not. There are so many use cases

00:00:18.640 –> 00:00:20.800
for this, so we’ll just show you a few.

00:00:21.440 –> 00:00:24.080
The first one is age gating. The

00:00:24.240 –> 00:00:26.840
second one will be checkbox related. The

00:00:26.840 –> 00:00:28.880
third will be UTM tag related and the

00:00:28.880 –> 00:00:31.040
fourth will be a login form via the data

00:00:31.040 –> 00:00:33.600
layer. So these are the four

00:00:33.680 –> 00:00:34.880
examples that we’re going to look at.

00:00:35.280 –> 00:00:38.160
Let’s go into the first one with

00:00:38.240 –> 00:00:40.080
age gating. Sometimes you may want to

00:00:40.080 –> 00:00:42.160
show different content based on how

00:00:42.960 –> 00:00:44.480
old someone is and the example we’re

00:00:44.480 –> 00:00:46.560
going to look at is where you only want

00:00:46.560 –> 00:00:48.840
participants aged 18 or over to enter

00:00:48.840 –> 00:00:51.040
into one of your competitions that you

00:00:51.040 –> 00:00:53.760
may have attached to one of your quizzes.

00:00:54.000 –> 00:00:55.360
So for this, we’re going to be using this

00:00:55.360 –> 00:00:56.960
travel competition form.

00:00:58.600 –> 00:01:00.280
And as you can see here, I’ve created a

00:01:00.880 –> 00:01:03.520
form that has information about a

00:01:03.520 –> 00:01:06.400
prize draw to do with a travel

00:01:06.400 –> 00:01:07.680
company or an airline.

00:01:09.240 –> 00:01:12.000
And the different form fields I have

00:01:12.000 –> 00:01:14.560
here are name, email, date picker, and

00:01:14.720 –> 00:01:17.040
terms and conditions checkbox. What I

00:01:17.040 –> 00:01:19.760
want to do now is use a

00:01:19.760 –> 00:01:22.560
condition based on the date picker to

00:01:22.560 –> 00:01:25.440
determine what comes next. So if

00:01:25.440 –> 00:01:27.840
someone is under 18 they

00:01:28.480 –> 00:01:31.200
get taken to one thing and if they are

00:01:31.200 –> 00:01:34.080
over 18 to something else. So

00:01:34.480 –> 00:01:37.120
go to configure results and

00:01:37.120 –> 00:01:40.080
now you can see that under branching type

00:01:40.160 –> 00:01:42.760
for this maker form I’ve selected

00:01:42.760 –> 00:01:44.960
data layer slash form fields

00:01:45.760 –> 00:01:48.400
and now I need to set up my condition.

00:01:48.880 –> 00:01:51.720
So what I have done is from the dropdown

00:01:51.720 –> 00:01:54.560
menu here, I’ve selected date picker

00:01:54.560 –> 00:01:56.480
because that’s the condition I want to

00:01:57.120 –> 00:02:00.080
set here. And I

00:02:00.080 –> 00:02:02.800
want it to be less than or equals to.

00:02:04.560 –> 00:02:07.520
And here I’ve put in a date that

00:02:07.520 –> 00:02:10.080
means someone is definitely 18 as of

00:02:10.240 –> 00:02:12.240
today in 2025.

00:02:12.960 –> 00:02:15.840
And so I want to

00:02:15.840 –> 00:02:18.800
make sure that their date

00:02:18.800 –> 00:02:21.760
of birth is this or less as

00:02:21.760 –> 00:02:24.320
in older so that’s the

00:02:24.320 –> 00:02:27.160
condition that I’m setting and

00:02:27.160 –> 00:02:29.760
now I can choose what happens with that

00:02:29.760 –> 00:02:31.760
condition or when that condition is met

00:02:31.760 –> 00:02:34.560
or not. When it is met, when

00:02:34.560 –> 00:02:35.920
that person is

00:02:37.280 –> 00:02:40.240
18 or over, then they get

00:02:41.280 –> 00:02:42.880
the result page ‘Thank you for filling out

00:02:42.880 –> 00:02:44.840
the form’. I’ll show you that in the

00:02:44.840 –> 00:02:47.600
Creator. They see this here.

00:02:48.560 –> 00:02:49.520
And if

00:02:53.360 –> 00:02:55.200
that condition doesn’t apply, so if

00:02:55.200 –> 00:02:57.680
they are younger, i.e. if that

00:02:58.320 –> 00:03:00.600
date is bigger than that date there,

00:03:01.440 –> 00:03:04.280
then they will get this result page here,

00:03:04.280 –> 00:03:05.960
enter one of our other competitions. I’ll

00:03:05.960 –> 00:03:08.080
just show you how I did that.

00:03:08.400 –> 00:03:11.200
So I have other quizzes, other

00:03:11.200 –> 00:03:14.080
competitions where people who

00:03:14.240 –> 00:03:17.200
are under 18 can enter. And I’ve got a

00:03:17.360 –> 00:03:19.680
CTA that takes them there from here.

00:03:20.880 –> 00:03:23.760
So that’s it. You’ve got

00:03:23.760 –> 00:03:26.560
your branching type selected here.

00:03:27.600 –> 00:03:30.160
You’ve got which form

00:03:30.160 –> 00:03:32.560
field you want to take into

00:03:32.560 –> 00:03:35.520
consideration, then what

00:03:35.520 –> 00:03:38.480
you want that condition to be. And

00:03:38.480 –> 00:03:40.560
then here, what should happen if that

00:03:40.560 –> 00:03:43.040
condition is met, and if that

00:03:43.120 –> 00:03:45.840
condition isn’t met. Let me just show you

00:03:45.840 –> 00:03:46.960
how that works.

00:03:49.600 –> 00:03:52.520
So here I can enter

00:03:52.520 –> 00:03:53.840
all my details.

00:03:56.080 –> 00:03:57.840
Here, enter my date of birth. And

00:04:00.880 –> 00:04:02.560
now I get this ‘Thank you for filling out

00:04:02.560 –> 00:04:05.280
the form’ screen here. If I did

00:04:05.280 –> 00:04:05.680
it,

00:04:15.520 –> 00:04:17.760
if I put this in, for example,

00:04:19.120 –> 00:04:20.880
I then get this result page here, sending

00:04:20.880 –> 00:04:23.760
me to another quiz and competition page.

00:04:23.920 –> 00:04:26.120
Okay, that’s example one. Let’s go to

00:04:26.160 –> 00:04:28.240
example two now. In this second

00:04:28.240 –> 00:04:30.520
conditional logic example, we’re going to

00:04:30.640 –> 00:04:33.600
look at a checkbox as a condition. This

00:04:33.600 –> 00:04:35.200
means that if you have a checkbox asking

00:04:35.200 –> 00:04:36.600
your audience to agree to something, for

00:04:36.600 –> 00:04:38.880
example, you can decide what block they

00:04:38.880 –> 00:04:41.720
see next, depending on whether they check

00:04:41.720 –> 00:04:44.520
that box or not. For this, we are

00:04:44.520 –> 00:04:46.320
going to look at a coffee survey.

00:04:47.360 –> 00:04:48.800
You’re a coffee company and you’re

00:04:48.800 –> 00:04:51.360
getting insights into your customers’

00:04:51.360 –> 00:04:53.600
coffee habits by asking them some

00:04:53.600 –> 00:04:55.440
different questions. You are also using

00:04:55.440 –> 00:04:58.320
the survey as part of a campaign for

00:04:58.520 –> 00:04:59.920
a new sort of coffee that you are

00:04:59.920 –> 00:05:02.640
selling. And so after all these

00:05:02.640 –> 00:05:04.800
questions, you’ve got result pages that

00:05:04.800 –> 00:05:07.720
take or different result pages that

00:05:07.720 –> 00:05:09.760
take different users to

00:05:10.560 –> 00:05:13.200
different vouchers, for example, for a

00:05:13.200 –> 00:05:15.680
percentage off code or for free coffee.

00:05:16.000 –> 00:05:18.480
And we want these different result pages

00:05:18.720 –> 00:05:20.400
to be shown depending on whether they

00:05:20.400 –> 00:05:22.640
checked a checkbox,

00:05:23.040 –> 00:05:25.840
which allows you as a company

00:05:25.840 –> 00:05:28.800
to store their data and make them part of

00:05:28.800 –> 00:05:31.280
a newsletter that you have. So

00:05:32.000 –> 00:05:34.080
that’s the form, here we have that

00:05:34.080 –> 00:05:36.560
checkbox asking for consent

00:05:37.040 –> 00:05:39.040
for storing data and therefore also

00:05:39.840 –> 00:05:42.160
signing up for a newsletter that you send

00:05:42.160 –> 00:05:44.920
out. And depending on whether

00:05:44.920 –> 00:05:46.800
they check this box, we want to send them

00:05:46.800 –> 00:05:49.720
to one of two result pages. I actually

00:05:49.720 –> 00:05:51.000
have three result pages because of

00:05:51.000 –> 00:05:53.840
another branch that is based on

00:05:54.040 –> 00:05:55.840
an answer earlier on in the quiz, but

00:05:55.920 –> 00:05:57.520
we’re just looking at these two for now.

00:05:58.680 –> 00:06:01.040
So we’re looking at this one here. If

00:06:01.040 –> 00:06:03.600
they didn’t check the box, then they get

00:06:03.600 –> 00:06:06.520
10% off. If they did check the box, then

00:06:06.520 –> 00:06:09.360
they get free coffee. So I know which

00:06:09.360 –> 00:06:12.000
one I would pick, but let’s go

00:06:12.080 –> 00:06:14.320
into branching now.

00:06:14.960 –> 00:06:17.640
Configure results, scroll down to

00:06:18.160 –> 00:06:21.040
that form. We’ve enabled

00:06:21.040 –> 00:06:23.880
form fields as the

00:06:23.880 –> 00:06:26.560
logic or as a branching type and I’ve

00:06:26.960 –> 00:06:29.720
chosen the checkbox as the component

00:06:29.720 –> 00:06:32.480
for this logic. This,

00:06:32.560 –> 00:06:34.800
the condition should be that if it is

00:06:35.120 –> 00:06:38.040
checked. It could also be if it’s

00:06:38.040 –> 00:06:39.760
skipped or if it’s not checked but I want

00:06:39.760 –> 00:06:42.640
it to be checked. If it is

00:06:42.640 –> 00:06:44.640
checked and that is true, if that

00:06:44.640 –> 00:06:46.880
condition applies, then

00:06:47.440 –> 00:06:50.400
I want them to enjoy

00:06:50.480 –> 00:06:52.080
their next cup of coffee for free and

00:06:52.080 –> 00:06:54.560
give them that result page. If it doesn’t

00:06:54.560 –> 00:06:56.480
apply, so if they didn’t check the box,

00:06:56.960 –> 00:06:58.800
they still get a result page but they

00:06:58.800 –> 00:07:01.200
just get 10% off. So that’s

00:07:01.360 –> 00:07:03.560
checkbox condition. I’ll just show you

00:07:03.560 –> 00:07:05.840
how that works as well. So if we go

00:07:05.840 –> 00:07:06.640
through this.

00:07:41.320 –> 00:07:43.200
Okay, then I fill out the form

00:07:47.520 –> 00:07:50.480
and I agree, submit

00:07:50.480 –> 00:07:53.080
and continue, and I now get my next cup of

00:07:53.080 –> 00:07:55.120
coffee for free. If I hadn’t ticked it,

00:07:55.200 –> 00:07:57.520
then I would get the other result page.

00:07:57.920 –> 00:08:00.840
Okay, that’s use case number

00:08:00.840 –> 00:08:03.320
two, let’s go on to use case number

00:08:03.320 –> 00:08:06.040
three. And for this we are

00:08:06.040 –> 00:08:08.640
looking at UTMs.

00:08:09.520 –> 00:08:11.520
So I’ll just go back to my Riddles.

00:08:12.640 –> 00:08:14.720
What this sort of branching logic also

00:08:14.720 –> 00:08:17.360
incorporates is the Riddle data layer,

00:08:17.520 –> 00:08:20.000
another feature which if you’re not

00:08:20.000 –> 00:08:22.680
familiar with feel free to read our help

00:08:22.680 –> 00:08:25.400
guide on the data layer. But if you’re

00:08:25.400 –> 00:08:28.360
already using data layer then it

00:08:28.360 –> 00:08:30.800
might be a really good option for you to

00:08:31.200 –> 00:08:34.000
add another level of customization

00:08:34.000 –> 00:08:36.400
for your Riddles,

00:08:37.360 –> 00:08:39.920
with combining the data layer with

00:08:40.000 –> 00:08:42.720
branching logic. So for this

00:08:42.720 –> 00:08:44.160
example, we’re going to use a product

00:08:44.160 –> 00:08:46.800
survey to show you how this

00:08:46.800 –> 00:08:49.640
works. And you might have this

00:08:49.640 –> 00:08:51.360
product survey embedded on your website.

00:08:51.360 –> 00:08:53.280
It’s a classic Promoter Score

00:08:54.320 –> 00:08:56.920
survey combined with some other

00:08:56.920 –> 00:08:59.000
questions, also some ads that I’ve put

00:08:59.000 –> 00:09:01.760
in. And of course,

00:09:02.080 –> 00:09:04.640
using branching logic to show specific

00:09:05.000 –> 00:09:07.840
blocks depending on a UTM parameter

00:09:07.840 –> 00:09:09.760
that we’re going to set up now. That’s

00:09:09.760 –> 00:09:12.320
the first step. Go into the data layer,

00:09:13.200 –> 00:09:15.160
which you do under Publish, data layer.

00:09:15.760 –> 00:09:18.640
And here I’ve set up an item for

00:09:18.640 –> 00:09:21.360
the source website. So I want

00:09:21.640 –> 00:09:24.560
to track whether my

00:09:24.800 –> 00:09:26.720
participants in this Riddle are

00:09:27.840 –> 00:09:30.720
coming from website A or website

00:09:30.720 –> 00:09:33.520
B, and once I’ve set that up here,

00:09:33.760 –> 00:09:35.600
then I will see that wherever I’m

00:09:35.760 –> 00:09:38.640
tracking my Riddle. So I can see not only

00:09:38.640 –> 00:09:40.880
the data that a user has

00:09:41.760 –> 00:09:43.080
entered themselves, whether it’s a name

00:09:43.080 –> 00:09:45.200
and email address, for example, but also

00:09:45.280 –> 00:09:47.400
the source website. So that’s happening

00:09:47.400 –> 00:09:49.200
in the background. And now I want to use

00:09:49.200 –> 00:09:51.920
that information to branch

00:09:52.320 –> 00:09:54.800
to specific blocks. So

00:09:54.800 –> 00:09:57.000
go back into

00:09:57.360 –> 00:10:00.000
your Riddle, and as

00:10:00.000 –> 00:10:02.640
always, configure results. Okay

00:10:03.280 –> 00:10:06.240
now here I’ve

00:10:06.240 –> 00:10:08.560
got my form and I’ve

00:10:08.960 –> 00:10:11.200
chosen data layer here

00:10:12.000 –> 00:10:14.080
as the branching type and this time

00:10:14.800 –> 00:10:17.760
I’ve selected this data layer item that

00:10:17.760 –> 00:10:20.160
I just added so in this case the source

00:10:20.240 –> 00:10:23.080
website and now I want to

00:10:23.080 –> 00:10:25.960
set it up so that if the

00:10:26.080 –> 00:10:28.000
source website contains, you could also

00:10:28.000 –> 00:10:30.600
do equals, but I recommend using contains

00:10:30.600 –> 00:10:32.720
so that you can just have an element of

00:10:32.720 –> 00:10:35.440
that URL that is definitely going to be

00:10:36.000 –> 00:10:38.480
in that parameter so that you don’t miss

00:10:38.480 –> 00:10:41.360
anything. And so let’s call

00:10:41.360 –> 00:10:44.080
it, they’ve come from one

00:10:44.320 –> 00:10:46.840
brand website. And if it

00:10:46.840 –> 00:10:49.520
contains that, then

00:10:49.680 –> 00:10:52.160
they should see this next

00:10:52.160 –> 00:10:54.960
block. If they came from

00:10:55.040 –> 00:10:56.480
the other websites, so let’s say you’ve

00:10:56.480 –> 00:10:58.800
got this the link to this Riddle on two

00:10:58.800 –> 00:11:01.120
different websites, if it came from brand

00:11:01.120 –> 00:11:03.880
two, let’s say, then they should see the

00:11:03.920 –> 00:11:06.000
other block, which I’ve set up for two

00:11:06.000 –> 00:11:08.800
different brands. And that’s

00:11:08.800 –> 00:11:10.720
it. So if

00:11:11.680 –> 00:11:14.400
I were to play this Riddle

00:11:15.560 –> 00:11:16.560
and I come to

00:11:17.920 –> 00:11:20.720
this question here,

00:11:20.800 –> 00:11:23.680
I’ve filled out the form, and then if I

00:11:23.840 –> 00:11:26.720
came from this website here, brand

00:11:26.880 –> 00:11:29.520
A, then I will see this question. If I

00:11:29.520 –> 00:11:31.840
came from brand B website, I will see

00:11:31.840 –> 00:11:34.120
this question here. And so based on that

00:11:34.120 –> 00:11:35.440
information, I can

00:11:36.160 –> 00:11:39.040
personalize that experience for that

00:11:39.040 –> 00:11:42.000
sort of customer and segment my

00:11:42.000 –> 00:11:44.720
leads. And of course, this is a

00:11:44.720 –> 00:11:47.360
fantastic marketing tool for

00:11:47.360 –> 00:11:49.880
your product campaigns. That’s the

00:11:50.160 –> 00:11:52.880
UTM branching condition.

00:11:54.000 –> 00:11:55.840
In our fourth example, we’re going to use

00:11:56.080 –> 00:11:58.720
logged in status as a branching logic

00:11:58.720 –> 00:12:00.760
condition. A lot of customers want to

00:12:00.760 –> 00:12:03.520
have limited content available

00:12:03.520 –> 00:12:06.400
to all site visitors and then much more

00:12:06.400 –> 00:12:09.080
content behind a login wall. And that’s

00:12:09.080 –> 00:12:11.320
what we’re doing here. This use case is

00:12:11.320 –> 00:12:12.840
based on a quiz here,

00:12:14.240 –> 00:12:17.000
this Latin words and phrases one, in

00:12:17.000 –> 00:12:19.800
connection with this website here, the

00:12:20.400 –> 00:12:22.880
Daily Gladiator news website.

00:12:23.360 –> 00:12:25.280
And what we want here is to

00:12:26.080 –> 00:12:28.320
show a quiz, like here.

00:12:29.280 –> 00:12:31.120
And we’ve advertized that it’s only

00:12:31.920 –> 00:12:34.480
available for logged-in users and if you

00:12:34.480 –> 00:12:36.960
are logged in you can click on

00:12:36.960 –> 00:12:39.600
start and then play that

00:12:39.680 –> 00:12:42.120
Riddle. If you’re not logged in, so I’ll

00:12:42.120 –> 00:12:44.720
just show you what happens, then

00:12:47.040 –> 00:12:49.920
when I click on start it tells

00:12:49.920 –> 00:12:52.200
me I’m not logged in yet and I need to

00:12:52.320 –> 00:12:55.160
log in. So let’s go into the

00:12:55.160 –> 00:12:56.160
Creator to set that up.

00:12:58.480 –> 00:13:00.640
We’ve got our Riddle here, open that.

00:13:01.280 –> 00:13:04.080
And here are all our blocks, including

00:13:04.320 –> 00:13:06.400
the text box that you saw, ‘You are logged

00:13:06.400 –> 00:13:09.120
in’ and the text box that you are not

00:13:09.120 –> 00:13:11.920
logged in. Okay. And you can also

00:13:11.920 –> 00:13:14.720
see here that we’ve got that

00:13:14.800 –> 00:13:17.760
variable display name entered in there,

00:13:18.040 –> 00:13:19.840
which we’ll set up in the data layer now

00:13:19.840 –> 00:13:22.240
before we go into branching logic.

00:13:22.720 –> 00:13:25.640
So go into your data layer. And

00:13:25.640 –> 00:13:27.840
I’ve set up three items here, one for the

00:13:27.840 –> 00:13:30.400
logged in status, one for the display

00:13:30.400 –> 00:13:32.400
name, which is the nickname that you have

00:13:32.400 –> 00:13:34.800
to create for this website,

00:13:35.520 –> 00:13:38.240
and your email address for that

00:13:38.240 –> 00:13:40.640
account. So all these things are being

00:13:40.640 –> 00:13:43.360
tracked, and now we can use that both in

00:13:43.360 –> 00:13:45.840
the Riddle and for the branching logic.

00:13:46.920 –> 00:13:49.440
In the Riddle, you saw here that if you

00:13:49.440 –> 00:13:52.000
are logged in, then the data layer sends

00:13:52.000 –> 00:13:54.240
that information into the Riddle. And then

00:13:54.240 –> 00:13:56.240
it will say your username is whatever

00:13:56.240 –> 00:13:59.200
your username is for that account where

00:13:59.200 –> 00:14:02.080
you’re logged in. If you’re not

00:14:02.080 –> 00:14:04.800
logged in, then it will ask you to click

00:14:04.800 –> 00:14:07.040
on a button so that you can then log in

00:14:08.000 –> 00:14:09.440
and play that quiz.

00:14:10.640 –> 00:14:12.720
Branching logic. Click on Configure

00:14:12.720 –> 00:14:15.520
results. And let’s

00:14:15.520 –> 00:14:18.160
go to that question. So we’re right at

00:14:18.160 –> 00:14:21.040
the beginning here and setting the

00:14:21.200 –> 00:14:23.400
branching type to data layer. And this

00:14:23.400 –> 00:14:25.600
time we choose the logged in status as

00:14:25.680 –> 00:14:28.240
the variable that makes this branching

00:14:28.240 –> 00:14:30.400
logic dependent. So

00:14:30.720 –> 00:14:33.520
now we want it to equal

00:14:34.720 –> 00:14:37.360
and I’ve set it up so that it equals

00:14:37.520 –> 00:14:39.920
one if I’m logged in and

00:14:40.960 –> 00:14:43.800
if not then zero and that

00:14:43.800 –> 00:14:46.640
means that I can now choose

00:14:46.800 –> 00:14:49.360
when this condition applies, i.e.

00:14:49.360 –> 00:14:51.200
when the person is logged in,

00:14:51.440 –> 00:14:53.560
they see that page you are logged in and

00:14:53.560 –> 00:14:55.640
they can proceed with the rest of the

00:14:55.640 –> 00:14:58.000
quiz. If you’re not logged in,

00:14:58.400 –> 00:15:00.680
then you will see that text block that

00:15:00.680 –> 00:15:03.160
tells you that, and then you could either

00:15:03.840 –> 00:15:06.720
input a form that allows

00:15:06.720 –> 00:15:08.720
the participant to log in before then

00:15:08.800 –> 00:15:11.560
playing the quiz, or here I’m

00:15:11.920 –> 00:15:14.520
showing them a result page that

00:15:14.520 –> 00:15:16.400
tells them they’ve missed out on the quiz

00:15:16.480 –> 00:15:18.600
and there’s then a CTA button that takes

00:15:18.600 –> 00:15:21.360
them to that form to log in. I’ll show

00:15:21.360 –> 00:15:24.160
you that here

00:15:25.600 –> 00:15:28.520
and then that takes them via a CTA to the

00:15:28.520 –> 00:15:30.760
login. So let’s have a look at what that

00:15:30.760 –> 00:15:33.520
would look like on your website again. So

00:15:33.520 –> 00:15:35.840
here I click on start

00:15:36.640 –> 00:15:38.720
and I’m logged in so I can start the quiz

00:15:39.120 –> 00:15:41.880
and if I’m not logged in – I’ll just show

00:15:42.000 –> 00:15:43.200
you here –

00:15:46.400 –> 00:15:47.920
so now I get sent to this login page

00:15:47.920 –> 00:15:50.880
here. I can put in my login details here

00:15:51.080 –> 00:15:53.160
and now I’m taken straight to the quiz.

00:15:53.160 –> 00:15:55.440
So whichever way you set it up you’ve got

00:15:55.440 –> 00:15:58.160
that login wall in between

00:15:58.240 –> 00:16:01.200
your users and some of your content.

00:16:01.520 –> 00:16:02.840
If you have any questions feel free to

00:16:02.880 –> 00:16:05.480
ask us or go on to any of the help

00:16:05.480 –> 00:16:07.720
guides for branching logic and I’ll see

00:16:07.720 –> 00:16:10.000
you in another video for a different sort

00:16:10.080 –> 00:16:11.200
of branching logic.