►
From YouTube: 2023-01-10 Product Analytics Sync
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everyone
and
welcome
to
the
January
10th
product
analytics
I'm,
going
to
go
ahead
and
share
my
screen.
A
A
A
B
I'm
sort
of
trying
to
build
a
thing
that
works
here,
the
biggest
issue
this
time
last
week
was
trying
to
untangle
what
click
house
wouldn't
wouldn't
let
us
do
it
turns
out.
Clickcast
has
a
bunch
of
built-in
functions
that
like
allows
you
to
build
funnels,
which
is
really
cool,
so
I've
been
trying
to
feel
my
way
around
those
not
understand
what
we
can
and
can't
do
with
them,
and
I'll
have
a
video
on
them,
filtered,
hopefully
less
today
showing
what
what's
been
built
so
far.
A
All
right,
we
have
nothing
in
design
and
looking
at
funding
breakdown,
we
have
the
onboarding
API
to
retrieve
the
state
of
the
project,
analytics
stack,
which
is
an
issue
because
it
pushed
out
of
the
internal
preview,
but
for
the
customer
review.
So
that's
currently
on
the
same
same
goes
for
the
column,
chart,
rendering
widget
and.
A
C
A
All
right,
I,
see
party
I,
think
I'm
supposed
to
close
this
out.
Sorry,
so.
B
A
C
Thank
you
to
find
that
to
me
if
you
like,
I'm,
going
to
take
a
look
at
that.
D
Yeah
that,
regarding
that
issue,
that
may
be
only
the
validation
that
what
we
are
doing
is
is
correct,
so
it
might
not
involve
any
any
dead
work,
but
but
yeah
I'll
think
up
with
Rob.
Regarding
that
I
think.
A
As
far
as
what
is
ready
for
development,
we
have
active
agency
privacy
member
by
default,
which
has
no
sign
in
maybe
it's
a
few
different
JS
SDK
items
here.
I
think,
ideally,
would
want
like
intelligence
like
that,
but
we
could
take
a
look
at
it
as
far
as
stretch
items
Milestone.
A
A
All
right
well,
we'll
just
go
ahead
and
skip
that
done.
We've
got
a
couple
of
other
follow-up
issues
as
well:
lazy
loading,
the
project
story,
designer
component,
as
well
as
retrieving
The,
Body,
Balance,
router,
acri,
backend
raw,
but
the
product
analytics
require
designer
laser
mode.
C
I'm
not
sure
if
I'll
have
enough
time
to
get
to
that
with
the
other
things,
I've
got
with
the
other
follow-up
I'm
dealing
with
Jan's,
not
back
till
next
week.
Axel.
Do
you
have
time
to
pick
that
one
other
follow-up.
A
Oh
as
far
as
the
product
analog
starter
base,
CRI
Rod
is
there
anything
you'd
like
to
bought
here.
C
Is
going
to
be
super
small,
it's
and
straightforward,
it's
just
that
it's
hard
coded
at
the
minute
and
we
can
retrieve
it
from
the
back
and
make
it
far
more
Dynamic
and
future
safe.
So
small
piece
of
work.
A
Got
it
and
we've
also
got
the
dashboards
audience
Behavior,
which
is
emerged
that
so
I
as
well
as
a
big
Sam
and
which
are
others
will
be
playing
with
it
in
our
local
environments.
I
know,
we've
discussed
for
you
a
list
of
follow-ups
to
add
as
part
of
our
working
session,
for
that,
but
we'll
be
I'll
just
be
a
challenge
without
any
building
some
issues
coming
out
of
that
it's
all
polished
yeah,
and
then
we
have
a
message
anything
else.
Anyone
wants
to
bring
up
for
these
dashboards.
A
Right
this
ties
into
a
gender
item
I
have,
but
one
thing
about
calling
out
is
that
we
got
these
products.
A
Unfortunately,
we
suffered
a
little
bit
of
pressure.
I'll
speak
to
later
on
we're
on
a
server,
but
I
want
to
restore
that
it's
possible.
A
In
addition
to
that,
there's
the
issue
for
the
Sasuke
lab
instance
of
that
because
of
the
previous
issue,
the
next
submission,
so
no
progress
there.
We
have
further
encrypting
the
connection
details,
integration
right
here,
yeah.
B
I'm
still
aiming
to
get
this
done
for
the
Milestone,
but
just
not
with
all
the
funnel
analysis,
stuff
up
and
head
down
in
that
and
I've
not
looked
at
this
yet.
A
And
then,
apart
from
that,
we
have
two
issues
in
review.
We
have
traffic
mode
to
be
for
onboarding
as
far
away.
If
it's
that
setup
for
you,
foreign.
D
Yeah,
the
reviews
came
slowly
for
this
one,
but
we
are
already
waiting
for
the
last
maintainer
approval.
He
I
already
have
got
a
feedback
from
that
and
I
applied
it.
The
only
thing
that's
that
is
missing
is
to
update
a
couple
of
suspects,
but
yeah
no
I'm
pretty
excited
that
this
is
close
to
Mars.
Now.
C
Yeah
first
thanks
to
Axel
and
Jan
for
picking
this
up
while
I
was
on
holiday
and
driving
this
forward.
This
had
a
few
minor
response
feedback
from
the
maintainer
which
I've
responded
to
today.
C
Yannick
is
in
an
EU
time
zone.
So
my
guess
is
he'll
probably
get
back
to
me
tomorrow
on
that
and
hopefully
you'll
get
merged.
A
D
Yeah
no
I
I
just
wanted
to
give
a
small
pink
to
some
that
this
solved.
The
issue
that
you
mentioned
on
slack
so
yeah
yeah,
that's
that
was
a
good
Improvement
there.
Thank
you
for
the
feedback
song.
E
All
right
so
I
wanted
to
talk
a
little
bit
about
dog
fooding
for
product
analytics
and
a
shift
in
direction.
We're
going
to
take
as
opposed
to
what
we
had
originally
for
the
gitlab
org
project,
the
the
more
Dennis
and
I
dug
into
it.
We
were
starting
to
figure
out,
there's
going
to
be
a
lot
of
work
to
do
specifically
around
one
trust,
bringing
that
into
gitlab
the
application
we
already
have
that
in
the
marketing
website,
but
it's
not
in
the
product
proper.
E
So
we
would
have
to
bring
that
in
to
do
the
original
dog
fooding
plan
we
had.
We,
we
took
a
step
back
and
thought
about.
You
know
really.
The
the
goal
of
our
dog
food
is
to
get
product
analytics
in
a
real
application.
Being
gitlab.com
with
higher
load
show
that
we
can
take
larger
scale,
but
this
effort
was
really
going
to
require
us
to
become
experts
in
one
trust
and
a
lot
of
the
cookie
consent,
which
is
not
really
the
core
area
of
focus
for
our
group.
E
E
In
our
hands
in
terms
of
being
able
to
execute
it,
so
what
we
want
to
do
instead
is
have
a
specific
list
of
folks
that
have
explicitly
opted
in
to
product
analytics
tracking
for
the
gitlab
org
gitlab
project,
and
this
way
we'll
still
get
that
larger
application
scale,
because
everyone
uses
gitlab.com
as
part
of
their
daily
work,
but
because
we're
asking
people
to
explicitly
opt
in,
we
don't
need
to
go
through
all
of
the
same
steps.
We
would
with
a
one
trust
and
a
cookie
consent
model.
E
We
talked
with
legal
about
this
a
number
of
times
and
they're,
okay
with
the
approach
and
the
things
that
they
need
and
that
we'll
need
to
do
to
move
this
forward
is
in
the
issue
that
I've
linked
there
we'll
start
using
that
as
our
single
source
of
Truth,
for
who
is
explicitly
opted
into
this
process.
That
issue
is
going
to
have
steps
for
if
you
want
to
withdraw
consent,
how
you
can
do
that
and
what
needs
to
be
done
once
that
happens.
E
This
is
completely
optional,
but
if
you'd
like
to
get
product
analytics
tracking
on
your
gitlab
or
get
lab
product
activity,
please
go
ahead
and
add
your
name
and
add
a
check
mark
there
again.
If
you
want
to
withdraw
that
consent
at
any
point,
there's
instructions
on
the
issue,
but
it
basically
boils
down
to
leave
a
comment
stating
that
and
then
we'll
remove
the
tracking,
and
so
this
should
allow
us
to
get
dog
food
on
the
gitlab
org
project.
Much
more
quickly
than
our
original
plan
start
getting
some
of
that
feedback
from
an
application.
A
Thanks
Sam
I
just
wanted
to
give
a
little
bit
of
an
update,
what's
happening,
structure,
wise
I,
think
I
last,
but
without
setting
up
back
like
automated
Back
Store
for
a
variety
of
things,
including
our
registered
base,
because
data
and
such
like
things
like
that,
that's
some
of
the
necessary
steps
that
we
will
need
to
have
checked
off
as
far
as
our
production
ready
distributions
we're
actually
able
to
get
this
out
to
customers
a
more
production
fashion.
A
Apart
from
that,
as
I
mentioned
before,
we
got
a
lab.com
shortly
thereafter,
but
this
has
happened
multiple
times,
Gypsy
battle
services
to
rebuild
itself
and
basically
wipe
that
data
and
so
I'm
working
to
restore
that
right.
Now,
just
so,
we
continue
to
collect
events
on
that,
but
I'm
also
trying
to
set
up
persistence.
Basically,
that's
what
I'm
currently
focused
on
pretty
important,
especially
as
yes,
we're
interpreting.
You
know
it's
not
as
critical,
but
as
soon
as
we
get
customers
so
pretty
issue.
A
A
Sorry
just
trying
to
understand
this
question
so
it
as
long
as
the
redis,
so
so
there's
a
couple
pieces,
basically
there's
The
Collector
and
then
there's
a
Reddit
server
and
so
the
collector,
whenever
it
receives
an
event,
checks
with
the
Reddit
server
to
say,
hey
I,
have
this
ID
is
application,
ID,
that's
being
sent
it's
JavaScript
SDK
and
where
does
it
go
and
that's
where
the
Reddit
server
then
tells
they
click
the
Jitsu
server
where
to
store
that?
That's
why
we
have
that
checked
out
configuration?
A
So
that's
the
only
thing.
That's
the
only
Link
in
terms
of
collecting
data
there
are.
There
are
other
identifiers,
like
the
Jitsu
project,
ID
that
we
use
to
actually
like
query
and
then
set
up
the
configuration.
But
as
long
as
we
have
the
IDS
and
that's
so
that's
like
right
now,
I'm
trying
to
do
it
properly
in
terms
of
restoring
the
entire
redis,
like
big
data
set,
but
worst
case
scenario.
All
I
need
is
the
IDS
which
we
already
have.
A
Those
are
publicly
available
since
we're
admitting
those
if
JavaScript
events
as
long
as
we
have
those
and
they
go
to
the
right
tables,
then
that's
that's
all
we
need
that
answer
your
question.
E
Yeah
it
did
things
because
what
I
was
trying
to
figure
out
was,
if
like,
if
I
as
a
user,
would
have
to
update
my
application
code
to
report
to
a
new
location
versus
yeah.
Things
are
down,
but
you
know
my
app
just
has
to
wait
a
little
bit
and
try
later
yeah.
A
So,
as
far
as
like
customer
interaction,
there's
no
action
needed
on
their
part
once
we
get
like
so
basically,
once
the
application
IDs
are
restored,
then
we
collect
the
events
will
just
continue
going
to
where
they
are,
and
then
there
may.
A
What
one
thing
I
am
trying
to
figure
out
is
how
to
restore
the
Gypsy
project
ID
so
that
we
don't
have
to
re-initialize
or
reconnect,
for
example,
staging
and
production
git
lab
instances
with
the
analytics
stack
but
I
guess
in
an
absolute
worst
case
scenario,
you
would
just
have
to
reintegrate
that
with
a
new
project
ID.
A
So
this
this
is
all
very
useful
experience,
because
both
need
this
documented
Infinity
runbook
for
infrastructure,
where
they
eventually
come
to
manage
this
for
us,
but
just
to
kind
of
give
you
an
overview
that
there's
no
customer
interaction
at
this
point.
For
now.
A
On
a
more
social
note,
basti
from
product
intelligence
has
sent
out
invites
and
surveys
for
a
team
day
tomorrow
for
the
11th
I
would
encourage
those
who
are
interested
in
bonding
with
your
fellow
section
members
to
to
attend.
If
you
can,
I
personally
will
not
be
able
to
attend
it,
but
for
Michelle
have
a
good
time,
and
if
there's
nothing
else
to
attempt,
you
have
to
be
executed.
F
Cool
thanks
a
lot
to
Dennis
and
please
attend
tomorrow
and
I
know
that
Pastor
is
already
putting
together
as
many
social
activities
as
he
can
so
I
just
wanted
to
bring
the
topic
up.
That
went
through
a
couple
of
issues
and
summarize
everything
that
was
going
on
around
the
whole
topic.
F
Where
do
we
put
a
menu
item
which
started
at
this
this
discussion
two
months
ago,
and
there
was
some
conclusion
during
the
last
weeks,
which
is
the
first
point
so
that
we
are
going
to
have
and
start
basically
with
a
menu
item
which
is
called
dashboards
under
analytics
and
maybe
Sam
and
Dennis,
as
you
had.
The
meeting
can
add
some
more
info,
slash
content
to
that
one.
E
Yeah
so
I
think
the
the
left
sidebar
issue
is
linked
there,
which
has
it
in
the
issue
description
now
a
visualization
to
be
more
explicit
about
where
we
want
to
go
with
this
and
really
what
this
came
down
to
is
us
getting
aligned
with
optimized
group
and
our
analytics
section
direction
as
analytic
that
analytics
tab
is
going
to
be
the
single
Source,
where
dashboarding
interaction
with
data
is
going
to
live
in
gitlab
the
product.
E
More
specifically,
our
dashboards
will
be
added
to
a
new
dashboard
screen,
rather
than
say,
specifically,
product
analytics
or
product
over
the
long
term.
The
existing
Options
under
that
analytics
tab,
so
value
stream,
CI
CD
Etc
will
become
individual
dashboards
that
also
live
under
the
dashboard
screen.
E
In
the
short
term,
though,
our
product
analytics
dashboards
will
live
in
that
new
dashboard
screen
optimize
and
other
teams
will
add
to
that
over
time
and
remove
the
existing
ones
in
that
issue.
Description
as
well,
there's
a
aspirational
vision
of
what
that
will
look
like
long
term,
specifically
with
all
the
dashboards,
condensed
we'll
likely
have
a
new
screen
just
for
the
funnel
Journeys
and
funnel
analysis,
because
that's
a
relatively
more
complicated
workflow
than
just
visualizing
data.
E
We'll
also
have
a
screen
there
for
experimentation
again,
because
that's
more
complex
than
just
visualizing
data
in
terms
of
setting
up
the
experiments,
what
changes,
what
doesn't
cohort
selection,
all
sorts
of
knobs
to
turn
and
finally,
we'll
have
a
configure
configuration
screen
in
both
the
short
term
and
the
long-term
Vision.
That's
where
things
like
setting
up
the
Jitsu
click
house,
Cube
stack
will
go.
E
A
I
guess
from
more
of
a
Act
in
terms
of
like
that
centralized
dashboard
view,
it
seems
like
in
our
case,
since
we
already
have
a
dashboard
index
view.
We
would
probably
use
that
as
our
c
since
we
already
have.
A
Then
everyone
else
is
going
to
folded
to
that.
So,
from
a
more
tactical
point
of
view,
I
think
you
know
it's,
it's
not
much
more
effort
to
get
to
that
state.
I
think
everyone
else
can
add
their
dashboards
to
and
as
you'll
see
from
the
issue
description
as
well,
Sam's
put
together
some
mocks
like
what
is
what
are
the
existing
dashboards
there
for
CI,
CD
and
evaluation,
and
things
like
that
would
eventually
be
kind
of
static
lasers,
we'll
figure
out
the
proper
way
to
add
those
to
the
National
list.
F
Yeah,
which
also
means
that,
in
reality,
dashboards
are
not
owned
anymore
by
product
analytics
and
and
we
will
be
basically
opening
it
up
and
we
need
to
find
also
which
helps
because
mate
is
the
assigned
ux
designer
for
optimize,
but
he's
more
and
more
becoming
an
RDX
design,
of
course,
for
dashboards.
But
this
will
mean
also
that
you
can
add
any
sort
of
visualization
query
component
that
exists
in
gitlab
to
any
sort
of
dashboard,
which
means,
especially
if
you
look
through
the
huge
ask
for
these
customers.
What
are
linked
there
is.
F
There
are
tons
of
asks.
This
is
the
number
one
asked
feature
at
the
moment
ARR
connected
to,
so
this
is
definitely
something
where
I
will
also
open
up
communication
lines
to
security,
especially
because
this
is
also
a
very
much
asked
topic,
so
that
basically
executes,
but
also
teams
can
build
very
easily
dashboards
on
their
product
features
to
better
understand.
Okay,
how
many
people
are
using
this?
F
How
are
my
Dora
metrics
on
those
and
how
many
secure
topics
do
I
have
and
get
everything
there
in
one
go,
so
this
is
definitely
being
opening
up
a
lot
of
possibilities
and
a
lot
of
things
overall
connected
to
this
huge
ask
is
definitely
that
we
want
to
push
for
this
as
as
fast
as
possible
timeline
wise
with
optimize,
especially
to
get
this
in
the
hands
of
customers
they're,
adding
dashboards
Mr.
The
first
one
is
in
the
final
review
at
the
moment,
which
is
really
about
that.
F
You
can
move
boxes,
that
you
can
resize
them
and
that
we
have
basically
the
code
that
is
created
out
of
it.
Ezekiel
from
optimize
is
also
already
working
on
the
Dora
metrics
and
more
components
so
that
you
can
add
them
to
dashboards,
which
is
the
nice
thing,
as
we
have
new
components
in
reality,
you
can
we
tested
it
already
out.
F
F
He
has
already
done
the
first
Mr
for
project
pointers
as
I
call
them
at
the
moment,
so
that
you
can
basically
have
because
everything
that
they
want
to
do
is
on
a
group
level,
and
what
we
want
to
do
is
run
on
a
project
level.
So
I
ask
them
for
a
favor
and
said:
hey,
can
you
if
you
have
done
this
just
for
groups?
Can
you
please
do
this
also
for
projects
so
that
you
can
basically
configure
another
project
with
a
repo
where
the
dashboard
files
then
will
be
stored.
F
Yeah
looking
for
feedback,
especially
at
the
moment,
with
regards
on
how
we
should
add
components
to
the
schemas
I
think
this
is
one
of
the
important
topics
so
I
think
Sam
also
made
a
great
suggestion
of
how
to
add
this
in
a
nice
way.
So
please
take
a
look
at
that
one.
So
we
can
collect
this
and
and
basically
get
this
shipped
as
soon
as
possible
to
Ezekiel
that
he
can
really
start
adding
that
stuff.
F
That's
it
and
then
it
creates
all
the
metrics
and
I
believe
that,
to
some
extent
that
our
funnels
will
work
quite
the
same
way
and
so
on
yeah
and
as
Danny
said,
we
need
to
rework
and
and
add
the
menu
item.
And
that's
the
main
thing.
I
think
that
we
need
to
change
is
really
work.
F
The
whole
gate
that
we
have
currently
in
front
of
the
dash
sports,
but
we
need
to
take
a
look
that
we
basically
make
out
of
product
analytics
dashboards
dashboards
in
general
as
a
route
as
soon
as
possible,
yeah
and
take
it
from
there
but
exciting,
because
this
means
that
really
two
teams
are
working
along
the
same
way
and
and
the
possibilities
are
really
nice.
So.
B
Funnels
I'll
keep
it
brief,
because
we're
nearly
at
the
end
of
time
just
wanted
to
link
into
the
Epic,
because
I
think
only
a
couple
of
us
have
seen
so
far
where
I
basically
done
what
was
the
contents
of
my
brain
while
I've
been
trying
to
understand?
How
can
you
click
how
to
generate
funnels?
You
can
see
some
pretty
pictures
and
some
nice
graphs
there
and
there's
one
outstanding
problem,
which
is
kind
of
stopping
me
from
getting
much
further.
B
So
if
anyone
has
any
thoughts
on
that,
please
please
do
input
otherwise
I'm
hoping,
then,
if
we
can
set
something
up
and
maybe
rub
a
duck
that
or
Rob
or
whoever's
available,
but
yeah,
the
the
short
version
is,
we
should
be
able
to
Define
funnels
in
files
in
projects
and
then
have
Cube
dynamically
generate
the
funnels
for
us,
which
should
be
accessible
via
the
standard
Cube
API
yeah.
It's
been
a
long
time
coming,
but
it's
it's
starting
to
take
shape.
A
Well,
if
you
have
any
we're
all
on
slack
we're
on
the
issues,
it's
been
hospitality
and
we'll
see
everyone
at
a
later
meeting
and
I'll
see
you
later
this
week,
have
fun
on
Tuesday
and
take
care.