10 Predictor settings
Let’s take a look at general Riddle-wide and specific predictor settings. We will:
- look at the various score separators
- contrast the different winner/loser layouts
- enable in-block share buttons
- create open and close dates
- limit entries, e.g. per IP address
- discuss branding and monetization options
Transcript:
00:00:04.640 –> 00:00:06.240
Hi there, welcome back. With your
00:00:06.240 –> 00:00:08.480
predictor content and structure ready,
00:00:08.880 –> 00:00:11.520
let’s now look at the settings for a
00:00:11.520 –> 00:00:13.760
predictor. To do this, click on the
00:00:13.760 –> 00:00:14.400
Settings tab.
00:00:16.720 –> 00:00:18.800
And we have some predictor-specific
00:00:18.800 –> 00:00:21.680
settings here. The first
00:00:21.680 –> 00:00:24.480
one is that you can choose what
00:00:24.480 –> 00:00:26.240
sort of separator there is between the
00:00:26.240 –> 00:00:28.640
two teams. So by
00:00:28.640 –> 00:00:31.440
default it’s versus, but you
00:00:31.440 –> 00:00:33.080
might want something different,
00:00:33.080 –> 00:00:36.000
especially if it’s not a sporting
00:00:36.000 –> 00:00:38.160
event. Perhaps there’s something else
00:00:38.160 –> 00:00:40.240
that you would prefer, whether it’s a
00:00:40.240 –> 00:00:42.840
dash, the X, or
00:00:42.840 –> 00:00:45.680
whatever. You
00:00:45.680 –> 00:00:47.840
can’t see that coming up here because
00:00:48.000 –> 00:00:50.640
I’ve put in final scores, meaning that I
00:00:50.640 –> 00:00:53.080
can’t vote anymore. I’ll just switch
00:00:53.080 –> 00:00:55.520
those off so that you can see what I’m
00:00:55.520 –> 00:00:56.880
doing there more easily.
00:01:02.080 –> 00:01:04.160
Okay, so now we can see this versus here,
00:01:04.720 –> 00:01:06.920
and if I changed it to a slash, for
00:01:06.920 –> 00:01:08.560
example, you’d see that here.
00:01:10.000 –> 00:01:12.880
Okay. Next thing is
00:01:12.960 –> 00:01:14.640
this default of bringing the winner
00:01:14.640 –> 00:01:17.200
forward. That means that if I choose, for
00:01:17.200 –> 00:01:19.000
example, England to be the winner and
00:01:19.000 –> 00:01:21.680
save score, that card will come
00:01:21.680 –> 00:01:24.120
forward. And by default, the
00:01:24.120 –> 00:01:27.040
loser is that I’vepredicted is
00:01:27.040 –> 00:01:29.760
also faded out using this
00:01:30.960 –> 00:01:33.440
setting here. If I disable
00:01:33.440 –> 00:01:35.200
those and
00:01:36.720 –> 00:01:39.200
refresh, and
00:01:39.200 –> 00:01:40.640
now let’s
00:01:42.000 –> 00:01:44.720
choose Italy this time, save score, you
00:01:44.720 –> 00:01:47.280
can see that the cards stay exactly the
00:01:47.280 –> 00:01:49.200
same. Neither of them comes forward, and
00:01:49.200 –> 00:01:51.680
neither of them becomes faded.
00:01:52.880 –> 00:01:55.680
So that’s those settings there. I
00:01:55.680 –> 00:01:58.560
like that visualization of the winner
00:01:58.800 –> 00:02:00.520
that I chose coming forward, so I’m going
00:02:00.520 –> 00:02:03.320
to leave that in with the the loser faded
00:02:03.320 –> 00:02:05.280
out in the background. Then,
00:02:06.680 –> 00:02:08.160
of course, by default we always have
00:02:08.160 –> 00:02:10.680
these share buttons on any result page in
00:02:10.680 –> 00:02:13.600
a Riddle, but you can also have them,
00:02:13.600 –> 00:02:15.840
and they’re there by default in within a
00:02:15.840 –> 00:02:18.560
predictor block itself. This means that
00:02:18.560 –> 00:02:21.440
your participants can share directly from
00:02:21.440 –> 00:02:23.840
within the block itself, rather than only
00:02:23.840 –> 00:02:26.320
from the result page with these
00:02:26.800 –> 00:02:29.480
buttons down here. Of course, you can
00:02:29.480 –> 00:02:31.440
disable them and they’ll then be gone
00:02:31.440 –> 00:02:33.960
there and will only appear on the result
00:02:33.960 –> 00:02:34.400
page.
00:02:36.160 –> 00:02:38.640
Okay, the other settings
00:02:38.960 –> 00:02:41.640
here are the same as for any other
00:02:41.640 –> 00:02:43.120
Riddle, but there are a couple of things
00:02:43.120 –> 00:02:45.640
I want to draw your attention to. Number
00:02:45.640 –> 00:02:48.480
one is the opening dates. Of
00:02:48.480 –> 00:02:50.880
course, if you’ve got a specific
00:02:51.360 –> 00:02:52.920
match going on, then you’ll want to close
00:02:52.920 –> 00:02:55.440
it just before the game
00:02:55.440 –> 00:02:58.240
starts. Perhaps it’s a completely
00:02:58.240 –> 00:03:00.240
different period, perhaps it’s
00:03:00.240 –> 00:03:01.920
off-season, and you want to just keep it
00:03:01.920 –> 00:03:04.080
open for that off-season period before
00:03:04.080 –> 00:03:06.080
the new season starts. Whatever the use
00:03:06.080 –> 00:03:08.800
case is, here are where you’ve got your
00:03:08.880 –> 00:03:11.680
opening and closing dates.
00:03:13.600 –> 00:03:16.480
So here, for example, I’ve closed it,
00:03:16.480 –> 00:03:19.360
and now the predictor can’t be
00:03:19.360 –> 00:03:22.160
played anymore. So that’s something you
00:03:22.160 –> 00:03:22.880
can set up.
00:03:24.960 –> 00:03:26.640
Here, for example, I’ve opened it again
00:03:26.640 –> 00:03:29.120
for the next week. We also
00:03:29.120 –> 00:03:31.920
recommend enabling Remember Users via
00:03:31.920 –> 00:03:34.520
Cookies. This is here. And what that
00:03:34.520 –> 00:03:37.040
means is that if you’ve got several
00:03:37.040 –> 00:03:39.920
different Riddles in that same season or
00:03:40.720 –> 00:03:43.440
within a specific time frame,That
00:03:43.840 –> 00:03:46.520
your users don’t have to enter their name
00:03:46.520 –> 00:03:49.440
and email address each time they play.
00:03:49.760 –> 00:03:52.560
They can enter it once and then give
00:03:52.560 –> 00:03:54.640
their consent to that data being stored
00:03:54.640 –> 00:03:57.400
in their in their local storage. and
00:03:57.400 –> 00:03:59.480
then they won’t have to input that every
00:03:59.480 –> 00:04:02.320
single time, saving time for them
00:04:02.320 –> 00:04:05.040
and increasing participation rates. So
00:04:05.040 –> 00:04:06.880
I’ll just show you that would then look
00:04:06.880 –> 00:04:09.200
like this. I’ve saved my score,
00:04:09.680 –> 00:04:12.400
and then here I have to enter my details,
00:04:12.440 –> 00:04:15.400
and then I can enable this autofill for
00:04:15.400 –> 00:04:17.840
next time, and then that will be the case
00:04:17.840 –> 00:04:20.800
next time. I won’t have to input
00:04:20.800 –> 00:04:23.320
my data because it’s been saved on my
00:04:23.320 –> 00:04:24.560
local storage.
00:04:26.720 –> 00:04:29.080
One last thing I want to look at is
00:04:29.080 –> 00:04:32.040
security, and you
00:04:32.240 –> 00:04:34.600
might want to make sure that people can’t
00:04:34.600 –> 00:04:36.200
play again, and there are a few different
00:04:36.200 –> 00:04:38.960
ways you can do this. One is
00:04:38.960 –> 00:04:41.840
by enabling one vote per
00:04:41.840 –> 00:04:44.720
browser, or also
00:04:44.720 –> 00:04:47.040
per lead identifier, meaning that the
00:04:47.680 –> 00:04:49.040
name and email address they’ve put in
00:04:49.040 –> 00:04:51.040
won’t be allowed to play again.
00:04:51.840 –> 00:04:53.680
So these are some different things that
00:04:53.680 –> 00:04:56.560
that we recommend and of course you can
00:04:56.560 –> 00:04:57.880
set up all of the other
00:04:59.120 –> 00:05:01.360
categories andIn the settings as well,
00:05:01.600 –> 00:05:03.440
especially branding and monetization are
00:05:03.440 –> 00:05:06.240
probably interesting for you as a brand.
00:05:06.880 –> 00:05:08.000
If you have any other questions, feel
00:05:08.000 –> 00:05:10.480
free to ask us and I’ll see you in
00:05:10.480 –> 00:05:11.120
another clip.