►
From YouTube: Acquisition Team Demo: Admin notification messages
Description
A demo of the first version of our targeted messages feature to help admins gather information to help them configure their instance in the best possible way. https://gitlab.com/groups/gitlab-org/growth/-/epics/13
A
This
meeting,
okay,
nice
so
I,
will
give
you
a
quick
introduction
about
broadcast
messages
and
what
we
have
done
before
yeah,
so
sharing
my
screen
right
now
and
broadcast
messages
are
messages
that
the
admin
of
good
lab
instances
can
set
for
all
users.
So
usually,
this
looks
like
this,
like
there's
a
big
header
on
the
top
of
good
lab,
and
you
can
define
a
message
if
just
copied
something
here
where
you
say
like
hey.
This
is
a
survey
thanks
for
exploring
our
issues.
A
A
So
it
looks
like
this
and
it'll
be
rendered
on
a
top
button
right
and
what
we
also
have
of
this
new
features.
Instead,
we
can
add
links.
This
is
already
what's
already
possible,
so
take
sorry
and
not
just
the
link,
but
you
can
also
design
like
we
have
this
new
lines
and
we
can
also
add
classes.
So
it,
for
example,
can
make
a
button
class,
and
so
user
actually
sees
a
button
here,
and
we
can
also
do
some
starting.
A
Look
nicer
and
yeah
it's
at
a
blank
here
and
we
can
then
link
user
to
something,
and
what
we
also
have
done
is
that
you
can
target
these
messages
messages
based
on
the
current
ul.
So,
for
example,
if
you
want
to
do
something
with
issues
we
can
say,
we
have
a
wild
card
that
everything
where
something
isn't
on
front
of
the
you
L.
A
A
A
B
Not
no
questions.
This
is
super
awesome.
It's
gonna
be
super
helpful
to
get
insights
from
users
just
anywhere
inside
the
application,
and
so
this,
coupled
with
something
that
the
expansion
team
is
working
on,
where
they
basically
have
the
these
pages
that
once
you
get
through
a
workflow,
we
say
like
congratulations.
You
just
set
up
your
first
repo
or
whatever
it
is,
and
at
that
point
we
can
survey
users
for
their
experience
or
their.
You
know,
promoter
score
or
anything
like
that.
B
A
Yeah,
we
also
have
one
issue:
that's
coming
up,
which
is
adding
variables
from
the
user,
so
we
can
have
a
link
and
at
the
user
ID
or
user
email
already
for
user
feedback,
and
if
this
wildcards,
we
can
also
target
URLs
pretty
good.
So
it
could
even
like
have
a
separate
notification
if
you
do
work
on
big
labs,
where
we
say
like
here.
A
thank
you
for
I'm
doing
work,
al
getler
for
the
first
time
or
submitting
this
much
requests
and
I'm
like
targeting
extra
repositories
in
UL.
If
you
wanted
to
so.
C
B
I
think
like
this,
this
is
really
just
the
obviously
minimum
viable
change
and
so
for
now,
we'd
link
to
something
like
Survey
Monkey
or
you
know
some
external
source,
where
we
could
create
a
survey
and
collect
the
information
from
there.
But
the
idea
is
to
have
this
be
fully
self-contained
right.
So
Nicholas
was
talking
about
adding
variables
so
that
we
could,
you
know,
get
the
email
address
and
add
it
to
a
link
or
whatever
the
idea
there
is.
B
You
know
we
want
to
be
able
to
control
the
a
not
message
as
much
as
possible
and
the
links
inside
of
it
so
that
we
can
send
the
survey
results
to
our
own
page
and
collect
the
results
on
our
own
page,
and
so
it
can
be
again
fully
self-contained
and
in
work
we're
generating
the
survey
we're
collecting
the
the
data.
So
that's
the
I
think
the
vision
is
is
that
we
don't
need
to
use
an
external
survey
tool
to
actually
get
the
information
that
we
need.
A
A
Point
so
there
are
two
types
like
this
notification
message:
I
showed,
which
is
on
the
button
right.
We
only
have
one
of
them
available.
This
is
always
the
last
one
that
gets
shown
and
for
broadcast
messages.
These
are
the
one
on
the
top.
You
can
have
multiple,
but,
like
it
just
looks
ugly.
If
you
have
multiple
so.
B
A
B
C
A
Know
we
kind
of
multiple
of
this.
This
would
actually
show
up
now.
Hopefully
this
is
not
on
the
other
other
one
exactly,
and
this
will
drop
now,
because
it's
for
rules,
everything
it's
the
latest
one
and
it
is
not
targeted
to
any
path.
If
this
was
also
target
to
any
path,
you
can
off
multi
one
of
different
pages,
yeah.