►
From YouTube: 2022-12-20 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
December
20th
2022
project,
analytics
Inc,
probably
the
last
one
for
the
year,
if
I'm
not
mistaken,
because
I
think
everyone
will
most
likely
be
off
next
week
for
obvious
reasons.
So
yeah
we
can
go
ahead
and
get
started
with
the
Board
review.
I
will
go
ahead
and
share
my
screen
and
hope
that
the
internet
will,
you
know,
play
nice
so
we'll
see
for
the
Board
review.
A
We
might
have
a
couple
issues
missing,
but
hopefully
we
can
kind
of
touch
on
them
as
we
go
along.
We
have
the
15
7
Milestone
planning
issue.
The
15-81
is
not
there
yet
so
yeah
we'll
I'll
link
that
in
the
agenda
we
can
take
a
look
at
that.
A
B
Yeah
so
yeah
funnel
analysis
has
been
my
life
for
the
past.
48
Hours
really
interesting.
The
funnels
themselves
aren't
too
complicated.
They
seem
to
mostly
work
calculating
the
percentage
of
completed
funnels
is
trickier
than
the
number
of
completed
funnels
in
absolute
terms,
but
the
the
real
interesting
bit
comes
when
obviously,
users
are
going
to
Define
their
own
funnels,
whereas
we
can
Define,
you
know,
total
number
of
sessions
or
sessions
per
user
almost
have
to
be
customized
there.
B
So
you
know
people
have
to
be
able
to
say
well,
we
want
to
go
to
PJ,
then
page
B,
then
page
C
or
you
know,
do
a
certain
number
of
things.
We
have
to
make
that
fairly
customizable.
So
I've
mentioned
it
later
on
in
the
agenda,
but
there's
Cube
has
support
for
dynamic
schemas
loaded
by
external
apis,
so
I
think
there
should
be
a
nice
thing.
A
A
We
have
this
blocked
issue
to
go
back
to
the
tracking
view,
which
I
believe
is
part
of
what
Axel's
been
working
on.
So
I
think
we
can
skip
that
for
now.
A
We
have
adding
support
for
pre-aggregations
regarding
users,
Anonymous
ID,
which
is
assigned
to
myself,
but
I-
think
we've
actually
already
gotten
this
sorted
out
Max.
Where
am
I
mistaken
here,
yeah.
B
A
Hold
on
sorry
there
we
go
they're
ready
for
development.
We
do
not
have
anything
I
think
there
is
one
from
Axel
about
the
single
stat
to
actually
pick
the
right
value,
but
we
can,
unless
yeah
you
can
speak
to
that
or
otherwise
we
can
go
to
in-depth
yeah.
C
I
can
I
can
only
speak
about
in-depth,
okay,
excellent
I
made
up
I
think
yesterday
for
the
front
end
kickoff,
so
the
tracking
codes
view
he
has
in
progress,
I
think
if
he
was
planning
on
like
getting
that
in
review
today,
but
that's
probably
not
gonna
happen
with
them
being
out
of
office.
C
As
for
the
next
one
waiting
for
the
stack
set
up
for
you,
I've
assigned
myself
to
this
issue,
Rob
asked
for
either
myself
Axel
to
take
this
on
since
I'm,
not
the
dri
currently
on
any
issue
I'm
working
on
this
today,
so
hopefully
they'll
all
be
in
review
by
the
end
of
the
day
and
yeah.
That's
it.
A
Great
cool
I
do
need
to
create
some
additional
issues
for
the
dashboard
here.
Tim
I
believe
you
had
said
yesterday
that
you
have
emerged.
Requests
for
these
dashboards.
Is
that
correct.
A
Yeah
I
think
we'll
want
to
break
this
up
to
see,
if
there's
anything
to
do
for
me
to
the
front
under
the
back
end,
to
get
it
to
the
I'm,
not
sure
if
it's
been
rearranged
yet
or.
D
D
A
A
Than
later
today,
but
for
these
issues
specifically
evaluating,
what's
currently
there
and
getting
that
to
the
to
match
the
mock-up,
if
you
will
than
any
other
tweaks
to
follow
up
with
that,
but
I
have
to
take
a
look
to
see
if
that's
changed
since
our
session
on
Friday.
But
I.
Think
I
just
want
to
leave
that
open
to
make
sure
that
someone
can
evaluate
it
against
what
we've
defined.
D
So
I
believe
the
only
thing
that
was
missing
was
is
that
issues
was
the
time
on
page
and
I
would
create
a
follow-up
issue.
Out
of
this.
To
be
honest,
because
if
we
would
switch
to
snow
plow
or
if
we
take
another
look,
we
can
add
this
at
a
later
Point
so
that
we
can
close
the
first
two
and
say
the
dashboards
are
done
and
revalidated
with
the
issues.
A
Okay,
have
they
also
been
because
I
know
when
the
way
we
arranged
it
in
the
working
session
wasn't
matching
the
mock-ups,
so
I
yeah,
so
I
would
assume.
We
would
want
to
rearrange
that
right.
So
that's
why
I
want
to
leave
the
issues
open.
A
Okay,
but
yeah
I
just
wanted
to
call
that
out
other
than
that
we
have
some
additional
front
end
I,
just
read
it
around
the
JS
SDK
to
see
if
someone
can
maybe
get
around
that
I
have
the
next
two
issues
in
depth:
I
need
to
rewrite
part
of
the
instructions
for
future
flags.
For
the
change
request
issue
we
found
out
with
the
additional.
A
We
need
an
additional
feature
flag
to
separate
the
admin
settings
for
every,
so
I
will
be
updating
the
feature
slides
for
staging
to
verify,
everything's
still,
okay,
there
and
then
give
John
Jarvis
the
go
ahead
to
follow
the
rest
of
the
instructions
for
production
so
that
we
can
get
the
internal
handbook
project
completely
integrated
beyond
that.
I
have
not
made
any
progress
on
the
gitlab
instance.
A
One
issue
that
I
need
to
add
to
the
board
is
the
automation
of
backing
up
both
the
clickhouse
data,
as
well
as
the
redis
database
I've
been
doing
that
in
a
way.
That's
not
running
on
my
local
machine
but
happening
on
gcp
itself,
so
I'll
be
creating
an
issue
to
kind
of
detail
that
I
might
have
mentioned
last
week.
A
That
I
was
working
on
the
automation
there,
which
is
functionally
working
but
needs
to
be
operationalize
a
little
bit
better
and
then
for
the
last
issue
for
in
Dev,
we
have
further
encrypting
connection
details
with
the
analytics
stack
integration
max
anything
you
want
to
call
it
here.
B
Yeah
this
is
taking
annoyingly
a
long
time,
apparently
duplicating
one
application.
Setting
to
another
application.
Setting
is
more
difficult
than
we
had
anticipated,
I'm
still
working
on
it
I'm
concerned.
It
might
actually
flip
this
Milestone,
but
it's
not
a
showstopper
for
anything.
So
it's
not
the
end
of
the
world
but
yeah.
It's
very
strange.
It's
because
we
store
encrypted
variables
as
binaries
and
we
store
non-encrypted
variables
with
strings.
B
So
it's
not
a
case
of
writing
an
SQL
object
statement
and
if
you
try
and
do
an
active
record
rails,
caching
gets
in
the
way
and
stops
you
from
doing
it.
So
this
has
been
a
weirdly,
difficult
problem
to
unpick.
A
A
All
right,
then,
we
have
a
couple
more
issues
in
verification,
yeah,
I,
think
one
of
these
are
heroes.
C
A
Sounds
good
and
I'm
just
going
to
double
check
the
bookmark
for
closed
issues
looks
like
we
don't
have
one
all
right
well,
we'll
have
to
I
think
we
stopped
with
the
new
tracker
on
General
handbook,
so
we
can
take
a
look
at
the
initial
empty
state
for
when
product
analytics
is
set
up.
But
this
these
two
are
for
from
Rob,
so
I
think
we've
just
got
three
issues
from
Max
and
yawn.
Then
we
can
start
I.
Think
pre
aggregation.
A
We
already
close
this,
so
it's
fine
Implement
system
analytics
more
of
the
same,
but
I
don't
know
max.
If
there's
anything
else,
you'd
like
to
call
out.
B
C
I
mean
a
list
of
dashboards,
is
just
updating
the
designs
or
the
look
and
feel
of
the
list
2
to
match
our
latest
designs
and
then
for
Rob's
initial,
empty
States.
That's
currently
what
I'm
using
to
so
it's
when
you
don't
have
any
product
analytics
set
up
on
your
project.
You
view
that
page,
the
MRI
that
I'm
working
on
that
robbed
it
most
of
it
already
is
to
add
a
button
to
that
that
you
click
and
that
sorts
the
initialization
process
and
then
we're
going
to
build
the
next
steps
off
to
that.
A
B
So
I
just
wanted
to
raise
this.
So
in
my
investigations
about
how
we're
going
to
implement
funnels
I
discovered,
the
cube
has
a
feature
called
Dynamic
schema
creation
which
I've
linked
to,
but
I'll
just
share
my
screen
now,
and
this
essentially
allows
you
to
call
an
API
which
returns
a
schema
that
you
can
then
use
as
opposed
to
defining
it.
B
Super
funnels
is
perfect
because
it
means
that
we
can
allow
gitlab
users
to
Define
funnels
and
then
we
can
funnel
them
through
to
keep
to
be
used,
which
is
excellent,
but
also
this
opens
up
a
load,
more
interesting
possibilities
in
terms
of
defining
measurements
and
so
measures
and
dimensions
that
can
be
used
by
particular
projects.
We
can
enable
and
disable
them
via
feature
Flags
or
we
can
enable
them
and
disable
them
via
licenses
as
well.
B
So
if
we
want
to
add
certain
bits
of
the
schema
that
only
appear
for
Ultima
or
premium-
and
we
can
we'd
also
have
control
over
that,
it
also
answers
the
question
about
how
we're
going
to
promote
schema
changes
from
dev
kit
to
gitlab
production.
We
may
not
need
to.
We
could
just
put
it
through
our
usual
code
review
process,
so
yeah
I
can't
believe
I
hadn't
noticed
this
before,
but
it
definitely
opens
up
a
lot
of
interesting
possibilities.
B
My
first
stop
will
be
to
try
and
get
it
working
with
funnels,
just
to
prove
that
it
can
be
done
and
then
in
the
New
Year.
Perhaps
if
it
is
something
we
want
to
go
down,
then
we
can
look
to
migrate.
The
existing
measurements
we've
got
into
into
this.
D
B
B
D
No,
it
would
be
nice
because
so
that
you
know
the
context,
why
I'm
asking
I'm
thinking
of
bringing
the
idea
of
cube
also
to
optimize
and
the
value
stream
analytics,
because
if
we
have
then
that
the
main
target
they
are
working
now
on
is
having
a
clickhouse
replica
of
the
gitlab
database,
which
would
mean
that
would
allows
to
do
also
very
fast
counts.
Against
that
part,
they
have
now
very
static,
analytics
components,
and
the
idea
would
be
to
give
them
something
like
the
widget
designer,
along
the
way
where
you
could
say.
D
A
It
we
did
I
freeze
our
Max
freeze,
okay,
okay,
you're
back.
B
A
A
A
So
I
think,
given
the
resources
we
have
and
what
we've
been
able
to
do
with
very,
very,
very
vague
issues
in
ethics
to
start
and
maybe
hopefully
less
vague
requirements
now
you
know
I
think
we've
made
some
really
good
progress
and
I'm
excited
to
see
what
we'll
do
next
year,
especially
with
the
investment
Focus
for
the
next
fiscal
year.
So
just
want
to
say
thank
you
to
those
that
are
here.
C
D
Exactly
what
Dennis
said
so
yeah,
thanks
also
from
my
side,
no
I,
think
we
have
made
great
progress
and
have
shown
that
we
can
make
really
good
steps
in
the
right
direction.
I
think
the
session
on
Monday
was
also
great,
seeing
product
intelligence,
also
joining
the
whole
effort
and
bringing
India
a
lot
of
tracking
knowledge
and
yeah.
So
that's
great
to
see
good
good,
good,
good,
good,
good
final
topics.
D
We
are
young
first
of
all,
thanks
a
lot
for
keeping
up
with
me
on
my
huge
Mr
I
know
it's
way
too
big
and
it's
taking
way
too
long.
So
thanks
a
lot,
a
lot
for
you
for
our
reviews,
I
hope
that
we
are
through
very
soon
and
get
this
to
the
ground
and
from
there
on
it
will
be
much
much
smaller.
Luckily,
so
then
I
pushed
for
getting
the
boring
solution
thumbs
up
beforehand.
Now
we
just
need
it
on
the
issue
so
that
we.
D
Could
be
that
we
have
everything
developed
and
everything
ready
to
look
to
be
looked
at,
but
we
don't
have
a
menu
item,
because
we
are
the
whole
discussion
on
where
product
analytics
should
go
is
completely
stalled.
D
So
at
least
I
have
some
thumbs
up
from
product
to
Simply.
Get
us
a
dashboard
menu
point
at
the
moment
under
analytics
for
the
first
iteration.
It
will
be
anyhow
a
feature
flag,
I
said
again,
so
I
hope
we
can
get
this
pushed
through.
So
if
we
would
come
up
with
a
release,
even
this
week,
I
will
try
to
get
us.
The
issue
go
ahead
today
and
then
we
can
create
ozone
Mr
for
this,
so
that
we
have
at
least
menu
for
our
feature,
which
is
yeah.
A
B
That
they
are
happy
with.
Then
there
was
another.
D
Proposal
that
they
are
not
happy
with,
and
so
I
said,
okay,
let's
at
least
push
for
some
solution
that
we
can
move
forward
even
the
feature
flag.
They
are
not
interested
I
think
they
were
burned
by
this
to
some
extent,
which
can
be
but
yeah
I'm,
pushing
on
all
lens
that
we
get
in
our
own
product,
analytics
group
or-
and
that's
my
next
discussion
point
that
was
brought
up
by
multiple
people,
especially
in
product,
is
on
one
hand.
D
Optimize
is
going
to
start
now
how
to
store
dashboards
than
on
a
group
level,
so
they
are
adding
to
groups
now
this
dashboard
project
pointer
where
we
are
going
to
save
the
dashboards
at
a
later
Point
Ezekiel,
is
basically
ready
to
help
me
on
the
dashboard,
editing
and
saving,
so
they
will
be
taking
over
on
the
generic
component.
So
we
should
be
getting
this
back
and
nicely
after
we
have
done
the
editing
and
saving.
D
D
That's
exactly
what
Ezekiel
got
merged
on
Monday,
where
they
can
basically
have
all
the
statistics
on
value
stream
analytics
for
one
project
as
a
component,
and
we
can
simply
wrap
this
up
and
say:
okay,
you
can
add
this
component
as
many
times
as
you
want,
and
what
we
need
for
this
is
that
you
can
then
select
in
the
dashboard
editor,
basically
curb
widgets,
a
different
project
or
a
different.
C
D
And
then
they
do
all
their
Frankie
graphql
stuff
in
the
background
against
their
current
data,
which
would
then
allow
them
to
have
executive
dashboards.
One
of
the
most
requested
features
at
the
moment
from
Paid
customers
and
what
also
came
up
in
a
lot
of
those
is
that
the
paying
customers,
and
especially
Executives
in
that
context,
we're
saying
that
they
would
love
to
have
dashboards
where
they
can.
A
A
D
So
the
idea-
or
at
least
the
discussion
point
at
the
moment
is
that
was
brought
up
is
why
not
have
simply
dashboards
and
they
can
hold
product
analytics
stuff.
They
can
hold
vegetable
analytics
stuff,
they
can
hold
I,
don't
know
what
so
team
members
and
so
on,
so
that
you
have
a
vast
majority
of
components
and
I
wanted
to
basically
bring
this
up
to
you
and
would
love
to
hear
what
you
think
about
that
that
possible
Direction,
it's
nothing
except
yet
it's
just
coming
up
so
and
I
have
no
opinion.
A
Yeah
I
don't
know
that
I
have
a
long
form
social
trades
written
version
of
this
yet,
but
this
has
come
up
in
the
ux.
This
piano
ux
discussion
for
product
analytics
for
a
bit
I,
don't
I'm,
not
a
fan
of
it,
because
I
think
there's
more
that
we
want
to
build
and
a
lot
that
belongs
together
for
product
analytics
where
I
feel
like
going
back
to
the
original
thought
of
like
not
having
our
own
menu
item
will
just
compound
the
ux
debt
we
have
currently
with
how
analytics
is
currently
organized.
A
We've
outlined
in
on
I'll
link
the
Epic
to
the
agenda
of
the
different
menu
items
we
expect
to
have
at
least
within
the
next
year,
including
experimentation,
funnel
analysis
configuration
specifically
where
I
think
good
experience
say:
hey
some
of
our
dashboards
are
in
this
dashboards
area,
but
others
are
in
our
some
other
place.
A
Perhaps,
and
then
configuration
happens
somewhere
else
as
well
as
like
funnel
workflow
like
designing
or
funnel
designing,
so
it
I'm
not
sure
that
I
feel
like
it
makes
sense
for
us
to
be
split
across
multiple
areas,
especially
with
yeah
having
different
entry
points.
Just
it's
a
boring
solution,
but
I
feel
like
it
complicates
a
problem
that
we're
really
struggling
to
deal
with
as
across
the
organization.
D
D
What
we
also
will
need
at
some
point,
with
the
session
we
play
and
session
recording
is
that
you
can
click
on
any
sort
of
analytics,
dashboard
and
say:
okay,
I
want
to
see
everyone
who
falls
under
this
bar,
for
example,
everyone
who
is
using
German
as
a
browser
language.
What
can
I
figure
out
about
them?
What
are
their
sessions?
What
have
they
viewed
so
that
you
can
basically
drill
down?
This
is
also
something
I.
This
is,
will
be
most
probably
custom
built
and
not
the
dashboard
in
that
sense.
A
Because
my
I
guess
for
me
to
really
have
thoughts
on
it,
I'd
be
curious
to
see
like
an
issue
really
defining
what
dashboards
are
going
to
go
in
this
dashboard
section
because,
as
part
of
the
deaf
we're
working
group
as
well,
we've
identified
over
30
different
types
of
dashboards.
So
the
question
then
would
be:
are
all
30
of
those
dashboards
going
to
be
in
this
dashboard
area?
Or
are
we
going
to
have
dashboards
and
some
menu
items?
Can
then
no?
A
The
new
dashboards
are
now
in
this
dashboard
menu
item
so
that
I
could
just
yeah
I
feel
like
if
we're
already
gonna
deal
with
where
all
these
things
are
going,
then
we
should
go
back
to
like
the
long-term
solution
of
separating
things
out
by
context
or
topic,
otherwise
we're
just
moving
things
around,
even
though
we
weren't
happy
with
the
original
solution.
But
now
we're
just
going
to
stuff
all
the
dashboards
in
one
area:
I,
just
yeah,
I
guess
I,
don't
have
a
complete
picture
to
really
have
well.
I.
D
Yeah,
here's
a
high
improved
a
little
bit
of
a
summary
that
that's
also
what
they
came
up
in
product
in
general,
I'm,
also
not
I,
think
it
would
be
also
weird
for
users
to
have
this
custom
constraint
of
putting
stuff
together,
because
what
I
definitely
could
see
also
along
the
way,
is
at
some
point
that
we
as
a
team
have
not
if
we
go
into
gitlab
and
not
have
this
completely
useless
list
of
subgroups
and
sub-projects,
maybe
on
the
groups
page
of
product
analytics,
but
rather
have
an
overview
that
we
have
put
together
so
that
we
see
how
many
Mrs
have
we
done
in
the
last
couple
of
days.
D
A
Yeah,
I
guess
and
Sam
and
I
were
talking
about
this,
we'll
have
to
get
in
a
meeting
next
year
and
see
what
it
seems
like.
We
just
need
to
get
everyone
in
the
same
Zoom
room
at
this
point.
It's
because
it
seems
like
separate
conversations
are
happening
and
things
like
that,
and
hopefully
we
can
maybe
put
together
a
working
session
to
reach
something
that
we're.
We
can
all
be
at
least
somewhat
happy
with
yeah.
B
A
Then
it's
just
the
four
of
us
left,
but
I
think
this
will
be
the
last
thing
for
the
year
so
good
to
see
everyone
ping
ping
well
reach
out.
If
there's
any
help,
we
need
for
the
remaining
few
days
for
the
year
that
we're
working
but
other
than
that
have
a
happy
holidays
and
a
Happy
New
Year.