►
From YouTube: 2022-11-29 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
what
day
is
it
November,
29th
product
analytics
sync?
Would
anyone
like
to
review
the
billboard.
A
What
year
is
it
also
yeah
cool?
Then
I
will
go
ahead
and
fire
up
the
board,
and
then
we
can
take
a
look
at
what
we've
got
here.
Max
you've
created
a
number
of
different
issues.
Here
you
want
to
cover
these
really
quickly
or.
B
Actually
upgradables
but
yeah
yeah
yeah,
one
of
them
was
created
like
10
minutes
ago,
but
first
one
is
investigation
of
pre-aggregation
in
anonymized
user
ID.
So
that's
me
trying
to
actually
understand
what
prelocation
is
in
Cube.
B
B
So
that's
cool
I've
been
messing
around
with
various
Ruby's
groups
this
morning
and
now
have
a
just
about
stable
account
installation
with
a
couple
of
million
records
which
makes
like
testing
this
stuff
a
bit
more
interesting,
so
yeah.
That's
what
I've
been
working
on
I'm,
not
both
of
those
issues.
A
Awesome
yeah,
like
you
mentioned
I,
just
created
that
one
less
than
10
minutes
ago,
just
pointing
out
the
work
I
will
need
to
do
to
actually
connect
event,
data
two
sessions
and
then
defining
what
is
a
session
I've
linked
to
Cube's
documentation
there,
which
basically
takes
apart
segments,
analytics
SDK
and
defines
it
as
any
activity
inactivity
period
of
over
30
minutes
between
user
actions,
and
so
basically
we'll
want
to
use
that
to
Define
how
we
want
to
Define
sessions.
B
A
Awesome
cool,
then
we
have
the
issue
for
the
track
usage
with
new
tracker
on
the
internal
handbook.
This
is
not
showing
us,
oh
no,
it's
still
worth
blocked.
Tim
I,
don't
know
if
this
is
a
good
idea
to
just
jump
to
your
point
in
the
agenda
topic
already
or
do
you
want
to
just
wait
until
later
after.
C
A
Good,
then
we
have
a
number
of
onboarding
issues.
I
think
that's
believed
to
be
waiting
on
The
View,
app
creation,
so
nothing
being
done
there
since
they're
blocked
cool
anything
with
the
issue.
E
A
Cool
then
we're
ready
for
development
still
shows
it's
blocked,
but
dashboard
list
of
dashboards.
Is
this
actually
ready
for
development
or
is
actually
still
blocked?
Is
that
what
that
issue
means
or
I'm
about
to
open
up
a
confidential
one.
E
F
E
A
G
Yeah
yeah
I'm,
looking
forward
getting
reviews
on
that
today,
so
so
yeah
and
thank
you
again
Rob
for
for
the
groundwork
there
and
yeah
not
much
to
to
tell
that
I'm
also
looking
forward
to
jump
into
the
onboarding
issues
afterwards,.
D
Yeah
so
I
just
started
with
that.
Most
of
my
day
was
spent
on
reviews
and
yesterday
on
fixing
my
GDK,
so
I
haven't
made
much
progress
there,
but
hopefully,
next
week,
I'll
be
able
to
give
a
nice
demo
for
default.
Awesome.
A
As
far
as
the
stack
integration
with
staging
and
production
I
haven't
received,
I
haven't
checked
my
pings
today,
but
I
haven't
received
a
ton
of
responses
on
my
latest
very
long
form.
Clarification
of
all
the
things
going
on
so
I
think.
That's
also
a
good
lead
into
the
eventual
number
nine
topic
and
the
agenda
so
I'll
just
save
that
for
the
discussion
there
in
terms
of
how
we
can
move
a
little
quicker
on
this,
but.
A
So
it's
a
little
bit
of
ping
pong
with
multiple
balls,
I
guess
on
the
table,
if
that
makes
sense,
yeah
so
we'll
get
into
that,
because
I
think,
especially
where
we're
at
in
the
season
and
the
quarter
and
generally
speaking
there
there.
We
can't
speed
this
up
and
it's
not
we'll
get
into
it
and
later
in
the
agenda.
All
right.
A
Cool
we've
got
creating
the
onboarding
view
app
Rob.
E
Yep
Zoom
review
great
initial
review
on
that
took
me
a
little
while
just
feature
specs
but
not
working
for
me
and
the
GDK.
My
gtk
broke
this
morning
fun
times
so
yeah
I
need
to
respond
to
his
initial
feedback
and
then
I
want
to
make
sure
that
I
get
it
out
to
an
external
maintainer,
just
to
make
sure
that
the
architecture
makes
sense
on
a
more
than
just
our
group
level.
E
A
Sounds
good
that'll
unblock
a
lot,
a
lot
of
issues
there
and
move
forward
with
the
onboarding.
So
that's
awesome
as
far
as
close
issues.
Our
last
bookmark
was
separation
of
dashboard
and
widgets
and
separate
files.
So
that
means
we
have
about
seven
newly
closed
issues
which
is
great
to
see
and
actually
have
a
couple
of
these
anything
you
want
to
cover.
B
Nothing
huge
I
think
I've
covered
most
of
it
in
a
slot
grip
to
be
honest,
but
now
we
can
create
product
analytics
Stacks
by
graphql,
apis
We've
Spoken,
the
Jitsu
key
in
the
public,
API
and
yeah-
that's
about
it.
B
G
So
we
added
a
new
section
on
the
documentation
and
we
also
went
through
a
few
a
few
suggestions
from
our
clinical
writer
and
we
also
have
a
follow-up
to
add
more
information
regarding
the
stack
we
are
using
on
the
documentation
as
well.
Hopefully,
I
can
I
can
contribute
to
that
this
Milestone
as
well,
so
so
yeah
it
was.
It
was
a
good
progress
and
also
we
have
a
couple
of
follow-ups.
D
No
I
mean
I
demo.
That's
last
week.
Sorry
I,
don't
think
it's
necessary
to
say
too
much
or
demote
again,
but
yeah.
It
was
kind
of
like
sorry
that
it
took
so
long,
but
it
was
kind
of
like
the
gift
that
kept
on
giving
at
the
end.
There
was
also
like
a
bunch
of
merge
conflicts
that
popped
in
and
random
weirdness
with
the
dependencies
but
yeah
it's
finally
merged.
No.
A
Need
to
apologize,
it's
part
of
the
fun
here,
so
cool
all
right,
I
think
that
wraps
up
the
Board
review,
then,
unless
anyone
has
anything
else,
they'd
like
to
add
I,
have
a
couple
of
read-only
items
that
people
can
check
out.
Tim
your
point
about
the
separate
infrastructure.com
update.
C
Yes,
that
was
a
part
is
the
whole
infrastructure.
Review
is
taking
longer
and
longer.
My
idea
was,
if
we
have
would
have
everything
already
to
activate
the
tracking
to
right
into
the
tracker
and
basically
get
already
data
so
that
we
basically
separate
the
connecting
to.com,
which
the
main
parts
of
the
production
Readiness
review
and
the
part
of
activating
the
tracker
would
that
make
sense?
Would
that
be
possible
foreign.
A
Theoretically,
all
we
need
to
do
is
connect,
send
the
app
ID
to
or
create
a
new
table,
and
then
I
guess
we
can
really
just
use
like
any
instance
and
set
up
the
table
and
then
set
excuse
me
connect
the
internal
handbook
to
our
existing
analytics
stack.
So
that's
part
of
like
how
we
can
expedite
us
getting
the
internal
handbook
tracker
going
so
I
think
we
can
separate
that
out.
In
my
opinion,
I
I
would
ultimately
like
to
have
a
production
integration
done
and
have
it
set
up
correctly.
A
But
it's
not
exactly
blocking
us
getting
this
internal
tracker
or
getting
the
instrumentation
set
up
on
the
internal
handbook.
F
Like
the
idea
of
separating
the
two,
because
once
we
start
getting
data
being
sent
from
all
of
the
users
of
the
internal
handbook,
Beyond
just
our
set
of
people
that
opted
in
to
run
the
extension
I
mean
that's
going
to
give
us
a
ton
of
value
in
terms
of
getting
a
more
Rich
data
set
to
start
working
and
doing
modeling.
On
top
of
it
also
helps
us
show
progress
to
the
org
around
hey.
Look
at
all
the
great
stuff
product
analytics
group
is
doing.
F
Our
next
step
is
completing
this
infrastructure
piece
to
get
it
integrated
properly,
but
I
think,
since
we're
already
having
our
small
group
of
people
using
the
track
on
their
local
machines.
That
shows
that
we
can
make
some
progress
by
having
it
deployed
in
the
actual
handbook
itself,
even
if
the
infrastructure
piece
is
not
yet
completed
like
those
blocking
each
other.
To
me
necessarily.
A
Yeah,
it
just
depends
on
how
you
want
to
like
figure
out
like
if
we're
Implement.
Well,
it
doesn't
matter
I'm,
okay,
with
separating
it
up.
So
as
far
as
action
items,
what
I
will
do
is
yeah
I'll
just
set
up
a
table
and
and
a
new
key
in
the
in
the
cluster
itself,
and
then
we
can
update
that
merge
request
and
then
we
can
start
collecting
data
there
and
then,
in
the
meantime,
I'll
still
continue
to
play
a
ping
pong
with
the
infrastructure
review.
Does
that
sound
good
with
everyone.
A
It's
yellow
data,
this
the
issue
and
the
infrastructure
review
is
specifically
with
making
changes
to
gitlab.com
production.com
itself,
and
we've
already
had
the
legal
preview
approval
to
collect
data
on
the
internal
handbook.
So
if,
if
we're,
basically
what
I'm
probably
going
to
do
is
just
set
up
a
GitHub
instance
in
the
cluster
itself
or
like
in
in
our
sandbox
environment,
connect
that
rename
the
table
to
match
the
ID
and
use
that
app
ID
to
to
collect
data
for
the
internal
handbook,
so
we're
not
touching.com
at
all.
A
A
Excuse
me
the
conversations
that
are
happening
with
the
infrastructure
review,
but
that
at
least
gets
us
to
the
data
point
which
you
could
argue
we
could
have
done
that
weeks
ago,
but
we
were
trying
to
do
it
like
completely
properly,
but
at
this
point,
I,
don't
think
like
there's
I,
don't
believe,
there's
an
issue
having
doing
it
this
way,
because
we're
not
touching.com
at
all.
A
Right
now,
okay,
then
I'm
fine
with
that
yeah,
that's
just
where
we
wanted
it,
because
the
project
actually
lives
on.com
right
like
in
in
reality,
especially
when
we
have
the
dashboard
set
up
and
that's
why
we're
still
going
to
work
towards
it
is
that
we
can
then
actually
pull
the
dashboards
up
on
the
internal
handbook
as
we
build
them,
but
we're
still
not
even
there
yet
so,
like
I.
Think
that's
okay
for
us
to
do
this
now.
F
A
But
it
hasn't
been
made
clear
to
me
from
infrastructure
like
what
do
they
need
for
that
specific
step
of
just
connecting
to
this
internal,
only
stack
which
has
minimal
like
flash
radius
and
things
like
that.
So
yeah.
C
C
Then,
rather
do
this
and
it's
more
of
the
it's
the
two
weeks
out
or
three
weeks
out
yet
and
I
would
go
with
let's
track
if
it's
just
a
couple
of
days
left
and
I
think
this
will
be
anyhow
good
to
know
I'm
happy
to
write
a
comment
just
of
like
someone.
Please
give
me
an
18
ETA.
Maybe
that
helps
yeah.
A
So
granted
it's
a
holiday
season,
blah
blah,
but
at
the
very
end,
I
put
a
line
break
just
to
kind
of
like
say
like
hey.
What
else
do
we
need?
So
if
you
can
just
help
boost
that,
I
would
appreciate
that
for
sure
that
said,
there's
still
open
questions
that
I
have
to
answer
on
the
actual
Readiness
Mr.
But
yeah
there's
like
three
separate
issues
right
now
that
I'm
trying
to
field
questions
for
so.
A
Appreciated
all
right,
then,
as
far
as
the
action
item
then,
just
to
recap,
I
will
set
up
a
separate
instance,
because
we'll
definitely
need
that
at
some
point
to
review
it.
But
then
they
basically
get
the
stack
set
up
to
accept
events
from
the
internal
handbook.
We'll
update
that
merge,
request
and
start
collecting
data
this
week,
then
I
think
cool,
just
sharing
kind
of
a
work
in
progress,
thing,
I
started
kind
of
cleaning
up
or
reorganizing
the
dashboard
epic.
A
As
far
as
like
what
we
wanted
to
find
for
the
audience
and
behavior
there's
not
a
whole
lot
there.
So
I
see
you
all
clicking
there
and
I
just
really
relocated
a
bunch
of
the
description
from
the
Epic.
A
What
I
really
need
to
spend
some
time
on
is
thinking
about
the
behavior
dashboard,
because
the
kind
of
what
we're
showing
in
the
vision,
proof
of
concept
I,
don't
know
we
basically
have
to
better
Define
what
we
want
out
of
these
dashboards
and
what
what
exactly
we
want
to
show
on
it.
We're
investigating
things
like
sessions
and
then
events
and
things
like
that.
But
you
know,
on
the
same
hand
where
audience
is
showing
browsers
or
resolutions
or
things
like
that.
A
The
behavioral
one
doesn't
excuse
me
show
as
much
in
terms
of
like
top
events
or
things
like
that.
So
we
just
the
same
thing:
we've
been
doing
with
everything
else
with
onboarding.
We
just
want
to
make
sure
we
really
Define
the
scope
and
requirements
there.
That
will
probably
require
its
own
working
session
after
sessions,
but
definitely
open
to
any
feedback
in
terms
of
things
that
you
would
expect
expect
to
see
from
those
dashboards
with
yeah
everyone's
experience
with
that
so
far,
but
I
just
wanted
to
highlight
that.
D
C
See
what
can
I
show
you
today,
as
it
was
Thanksgiving
week
and
I
love
Thanksgiving,
because
there
is
so
much
quietness
and
you
can
get
stuffed
up.
So
I
was
curious
as
I
I'm,
always
quite.
D
C
About
things
that
we
load
that
thing
or
go
from
here,
so
that's
our
dashboard
list.
As
you
know
it,
you
can
go
into
the
overview
and
I
tried
out
what
we
already
had
in
the
PC.
So
we
have
now
an
edit
button.
So
what
we
can
do
is
we
can
resize
them.
We
can
take
them,
we
can
move
them
and
it's
already
creating
the
code.
D
C
C
C
Step
there
you
go
browser
and
user
browsers,
so
that's
my
new
widget
I
can
click
add
to
dashboard
and
Sims
11.
As
we
say
in
German,
we
have
the
new
widget
added,
so
we
can
now
basically
resize
that
one
and
add
it
over
here.
This
is
doing
everything
right
now
in
memory
as
we
don't
have
an
endpoint
to
save
a
specific
widget
and
then
we
would
basically
hand
over
just
the
ID
of
that
new
widget
file,
visualization
file
to
that
dashboard
to
edit
there,
but
basically
yeah
that
works
in
that
sense.
C
So
what
happened
during
this
week
is
also
that
I
had
my
first
two
Mrs
out
of
this
working
Mr
that
I
I
use
basically
I
cut
the
first
two
Mrs
out.
The
back
end
is
already
merged
things
mix
for
the
help
there.
So
this
is
adding.
Currently,
the
new
proxy
calls
for
the
cube
dry
run
endpoint
and
the
cube
meter
endpoint.
C
So
this
gives
us
all
the
endpoints
that
that
are
actually
available
from
Cube
and
they
make
it
available
for
the
widget
designer
so
that
we
know
what
we
can
query
there
and
we
have
also
the
setup
for
the
widget
designer
itself
as
an
MR
that
was
also
merged
yesterday
and
now
with
the
line
chart.
So
this
is
already
a
range
that
is
rebased
from
Jan's
line
chart
and
it's
using
that
one
and
as
soon
as
we
have
a
data
table,
we
can
use
the
two
and,
let's
assume,
as
I,
have
a
single
stat.
C
I
will
add
the
two.
So
my
next
topic
will
be
really
cutting
the
next
Mr
of
most
probably
already
the
first
step
of
having
these
measure
selectors
with
the
selectors
that
are
actually
available
from
combined
with
the
first
Dimension
selectors
and
simply
creating
currently
the
nas
that
it
stands,
for.
We
don't
have
data
on
this
and
basically
cut
that
out
and
create
issues
that
we
that
we
get
at
this
data
so
that
we
can
edit
later
and
maybe
just
leave
out
the
filters
and
also
here
in
the
widget
designer.
C
Very
cool,
thank
you,
yeah!
No,
it's
it's
really
tempting
to
move
forward
with
that
stuff,
because
yeah,
all
those
bits
and
pieces
come
into
place
now
and
I
can
definitely
see
that
we
are
pushing
out,
because
everything
else
also
works.
The
filters
work
now
the
date
range
Works,
so
we
can
create
already
more
complex,
Dash
widgets,
even
and
push
that
over
to
the
dashboards
and
yeah
find
a
way
to
save
them.
C
Then
this
I
believe
one
of
the
bigger
next
steps
and
as
we
are
adding
then
more
and
more
complexity,
because
in
reality,
what
we
need
now
here
is
this
is
the
data
part,
but
what
on
the
right
side,
I
want
to
have
like
the
the
options
for
a
graph,
so
for
the
for
the
line
chart,
for
example,
that
you
are
able
to
select
which
which
data
is
on
the
x-axis
and
what?
What
is
on
the
y-axis
and
and
stuff
like
that,
so
this
widget
designer
can
go
on
I
believe
for
the
next
12
months.
F
Yeah,
exactly
designing
charting,
that's
a
that's
a
whole
product
in
and
of
itself
right,
yes,
in
inside
of
the
code
option,
do
we
already
well,
we
already
have
options
to
Define.
What's
on
the
X
or
the
y-axis
or
other
graph?
Yes,.
C
Okay,
exactly
because
otherwise
I
thought
I
figured
out
that
the
line
chart
doesn't
even
render
anything
if
it
doesn't
have
the
options.
So
this
is
one
of
the
next
steps
that
we
really
have
the
option
to
also
figure
out
how
the
ux
is
working
with
having
data
on
the
left,
side
and
options
on
the
right
side
and
things
like
that,
but
and
also
find
a
way
that
we
can
see.
Okay,
a
line
chart
test
these
types
of
options
so
that
we
make
this
also
configurable.
C
Otherwise
we
will
end
up
with
a
hundred
different
sub
control
thingies
around
the
widget
designer
which
make
it
a
super
heavy
to
change
anything.
So
I
think
this
is
really
going
a
little
bit
into
the
whole
no
code,
land
of
having
editors
that
are
configurable
and
yeah.
A
Yeah
that'll
be
it's
fun
to
navigate
because
we'll
want
to
make
sure
those
patterns
are
established,
especially
when
I
get
into
like
editing
the
dashboards
in
place
as
well.
So
we'll
make
sure
we
want
to
be
consistent,
not
just
add
a
raw
controls
for
each
little
option,
but
it's
exciting
for
sure
and
as
we're
preparing
the
single
stat
in
the
table
and
now
we're
looking
into
how
we
get
all
the
data
prepared
in
terms
of
like
getting
sessions
available
and
then
eventually
getting
it
into
page
areas.
A
Things
like
that
we'll
definitely
be
able
to
start
piecing
everything
together.
So
it's
super
exciting.
Yes,.
F
A
A
I
would
imagine
it
could
potentially
expand
from
that,
but
they
haven't
had
I
think
supposedly
this
week's
supposed
to
be
like
the
first
meeting,
but
actually
I'm,
not
even
sure
when
it's
happening
it
already
had
happened,
but
yeah
their
goal
is
a
little
bit
more
finally
scoped
for
now,
but
I'm
sure
when
they
see
our
stuff.
That
might
change,
because
we're
definitely
in
newer
territory
as
far
as
gitlab
is
a
concerns.
As
far
as
dashboards
go.
E
Yeah
I
was
only
going
to
say
that
for
the
controls
for
different
charts
and
stuff,
we
can
always
use
the
power
of
our
schema
to
Define
what
options
are
available
for
each
data
source
and
line
chart
type
of
chart
type
and
then
use
that
in
the
front
end
as
a
Json
schema
to
decide
what
controls
to
show
up
yeah.
A
C
Very
cool
I
was
also
thinking
up
about
having
a
small
helper
script
so
that,
right
now
we
are
creating
those
two
Json
arrays,
basically
with
the
with
the
links
to
the
jsons
in
the
static
one,
and
maybe
we
simply
create
an
import
to
a
file
that
is
then
Auto
generated
from
a
directory
and
the
subfolder
so
that
we
simply
have
a
script.
We
drop
the
jsons,
we
edit
the
jsons,
we
run
the
script
and
it
produces
a
new
Js
file
with
exactly
those
arrays
so
that
we
don't
need
to
mess
around
inside
of
the
files.
B
C
Simply
hit
code,
take
that
code
put
it
in
the
Json
in
the
directory
and
hit
save
from
there
and
then,
if
we
have
a
script,
and
it
makes
it
also
easier
that
they
show
up
immediately
again
into
in
the
product
so
that
that
was
also
another
fault,
because
that
shouldn't
be
too
hard
to
have
like
a
util
script.
C
A
C
C
A
Maybe
maybe
an
issue
would
help
just
to
understand
the
goal
there,
because
I'm
perhaps
missing
the
link
between
having
Json
files
in
there
versus
having
yaml
in
there,
because
I
I
understood
yaml
to
kind
of
be
the
final
format
for
it
to
exist
in
the
dragon
dashboard
directory.
A
Okay
yeah,
maybe
we.
F
Can
write
questions
yeah,
yeah
I
walk
through
it.
That
would
be
helpful
for
me.
I'm
I
think
I'm
following
it,
but
I'm
not
completely
positive.
B
A
All
right,
thanks
for
the
demo,
Tim
yeah
I,
think
that's
the
end
of
the
agenda.
Did
anyone
have
any
other
final
topics,
questions
or
concerns.
A
B
You
were
able
to
make
the
meeting
at
half
for
your
time,
just
because
I
know
at
the
end
of
our
block
now.
A
A
We'll
record
it
anyway,
so
you
know
cool.
It
was
good
to
see
everyone.
Let
me
know
if
there's
anything
else,
you
need
otherwise
have
a
good
rest
of
your
week
and
take
care.