►
From YouTube: 2023-01-03 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
B
A
We
have
the
first
issue
here,
I
wonder
if
we
should
go
through
the
open
issues.
First,
what.
B
Do
you
think
Dennis
yeah
we
can
cover
those
okay,
I
can
speak
to
them
since
they're
unassigned,
so
filters
for
dashboards.
B
The
date
range
is
one
of
the
first
dashboard
level
controls
we
want
to
add
to
our
dashboards
and
so
being
able
to
do
the
query
overrides
and
override
what
the
widgets
themselves
and
the
panels
whatever
we
do
end
up,
calling
them
to
be
able
to
determine
a
date
range
for
the
entire
dashboard
so
that
one's
definitely
wanting
to
be
targeted
for
this
Milestone,
just
to
kind
of
be
the
first
step
for
a
number
of
other
filters
at
that
level.
B
But
we'll
see
where
we're
at
with
in
terms
of
capacity
for
that,
but
until
then
I
think
it's
still
in
solution
validation.
So
we
just
have
to
make
sure
that
we
can
properly
estimate
it
and
get
it
assigned.
B
B
You
and
then
we've
got
the
implementation
plan
for
product
analytics
export
this
one's
more
for
for
Max
to
explore
at
some
point,
but
he's
busy
with
funnel
analysis
so
which
I
is
the
next
one
so
nicely.
C
Get
into
that
one
I
mentioned
later
on
the
agenda,
but
I've
been
sort
of
a
while
time
was
out
at
the
end
of
December
before
I
finished
sort
of
investigated.
How
that
might
work,
how
we
might
allow
users
to
Define
funnels
and
have
that
pulled
dynamically
into
Cube?
Make
some
nice
progress
from
an
architectural
point
of
view,
I'm
quite
happy
from
a
in
the
weeds,
SQL
query:
point
of
view:
there's
some
large
Kinks
that
need
to
be
ironed
out,
which
I
think
would
be
putting
mildly.
C
But
in
terms
of
a
fundamental
point
of
view,
I
think
that
looks
good.
The
thing
I'm
missing
now
is
is
what
the
issue
suggest
is.
The
needs
I
could
build
something
cool,
but
if
it
doesn't
fit
what
we're
actually
expecting
to
see
from
a
customer
point
of
view,
then
it's
kind
of
worthless,
so
I'm
hoping
over
the
next
week
or
so
to
maybe
Hammer
that
with
Sam,
possibly
and
understand
what
the
actual
problem
to
be
solved
is.
D
Yeah
that'd
be
good.
Do
we
have
like
questions
written
down
in
an
issue
already
Max
from
when
I
was
out
that
I'll
see
in
my
pings
or.
C
D
Okay,
cool
yeah,
I'll,
I'm,
pretty
sure
I
wrote
some
of
that
down
in
a
either
an
epic
or
an
issue,
so
I'll
see
if
I
can
find
that
and
if
that's
not
sufficient,
we
can
always
hop
on
a
call
or
do
something
async
as
well
sounds.
A
Well
then,
the
next
one
we
have
is
add
a
button
to
go
back
to
the
tracking
view
from
the
dashboard
listing.
This
is
blocked
by
I.
Think
Axel's
issue
to
actually
add
the
tracking
view.
Once
we
have
that,
then
we
can
add
that
button
and
then
then,
as
you
have
the
next
Block
Run
I,
don't
know
if
there's
anything
to
say
about
ad
support
for
pre-aggregation
around
users,
Anonymous
ID,
yeah,.
C
A
A
Okay,
cool
I
mean
it
is
from
a
year
ago.
So
it's
a
long
time
that
was
my
day
joke
for
the
year
cool
in
development.
We
have
internal
preview
audience
for
the
audience.
Dashboard
I
think
this
is
just
this
has
pretty
much
been
built
out,
but
I
think
this
is
just
about
the
Polish
and
making
sure
that
everything's
done
for
this.
If
I
understand
correctly.
B
Yeah
I
I,
don't
I
believe
we
might
want
to
I.
Think
Tim
wanted
to
close
this
out
and
then
create
follows
for
this,
but
I'll
just
double
check
on
that.
I
don't
know
actually
where,
if,
if
the
merger
Quest
has
already
been
merged
as
well
but
I
do
know,
Behavior
still
has
a
couple
more
steps
in
order
to
actually
reach
to
achieve
all
the
visualizations
that
we
wanted
for
the
behavior
dashboard,
but
that
without
jumping
too
far
ahead,
I
think
audience
is
off.
A
I'm
gonna
assign
this
one
to
Tim
since
he's
the
main
person.
That's
working
as
well
should
I
sign
it
to
you.
B
Yeah
we're
missing
a
couple
things
for
the
single
stat
I.
Think
it's
a
I
can't
remember
exactly
what
it
is,
the
custom
events
and
that's
part
of
because
we
aren't
tracking
any
custom
events
in
any
of
our
instrumentation.
Currently
so
we'll
we'll
have
to
work
on
that.
C
B
C
B
Yeah
that'll
be
part
of
the
schema
for
that
or
I
guess
we
would
add
new
actions
in
the
filter
based
off
of
what's
not
a
page
view
but
I
think
that's
a
question
we'll
have
to
figure
out,
or
at
least
for
this
version
of
the
schema,
so
I
guess
the
answer
to
your
question
is
yes,
we
will
likely
have
to
update
the
schema
okay.
B
So
this
one
is
the
stack
integration,
unfortunately,
I
felt
ill
for
the
holiday,
so
I
wasn't
able
to
complete
the
feature
flag
activation.
B
This
is
the
integration
of
the
internal
handbook
repository
with
our
analytics
stack.
We
got
through
staging
and
then
we
found
out
that
the
feature
flags
were
a
little
bit
mixed
up,
and
so
we
sorted
that
out-
and
we
just
have
to
I
just
have
to
reactivate
them
properly
for
staging
make
sure
everything's
still
okay
and
then
we
can
get
I
can
give
the
go
ahead
to
John
Jarvis,
to
finish
the
steps
for
production
production,
and
we
should
be
good
to
go
there.
B
That
said,
we
already
are
collecting
events,
so
this
is
more
for
once
we
finally
do
get
the
dashboards
merged
into
if
they're,
if
they're
not
already
merged,
then
we
can
start
viewing
them
for
the
internal
dashboard
project.
So
hopefully
that
will
get
resolved
in
the
next
day
or
so.
A
Okay,
yeah.
B
This
one
yeah
yeah
this
one's
just
a
demo
git
lab
instance,
which
I
would
it's
definitely
a
lower
priority
right
now
for
me,
so
I
have
the
instance
installed,
but
I
still
have
to
do
some
networking
fun
just
to
make
sure
it's
like
available
for
us
to
actually
use,
but
nothing
has
really
moved
here
in
the
past
few
weeks,.
C
Yeah
I've
not
touched
this
since
I
started
back
this
morning.
I
will
get
to
it
in
this
Milestone.
It's
not
a
massive
priority.
I
spare
anyone
we're
the
only
customers
of
this
feature
anyway,
right
now
and
so
I'll
get
to
it.
But
it's
not
a
huge
priority.
A
Cool
then,
the
two
items
in
review
here
are
from
Axel.
I
can
speak
to
these.
The
tracking
codes
view
is
pretty
much
built,
but
how
it
connects
to
the
main
application
is
something
that
I
spoke
to,
Axel,
that
we
need
to
change
so
he's
working
on
a
follow-up
to
basically
change
just
how
we
handle
transitioning
to
the
new
pages
and
how
we
like
save
the
state
in
the
front
ends
the
other
one.
I
think
this
is
in
maintain
review.
A
A
So
this
seems
to
be
running
along
smoothly.
This
is
kind
of
tied
to
the
first
issue
here,
the
tracking
codes
for
you.
So
this
is
what
I'm
working
on
that
I
took
over
from
Rob
is
the
first
initial
page
that
you
see
it's
that
empty
state.
That
says
you
don't
have
any
product
analytics
set
up
on
this
project.
A
There's
a
setup
button.
It
does
some
loading
it
fires
off
the
back
and
call
to
actually
create
the
whole
tracking
in
Jutsu
and
then
reports
back
once
it's
done.
So
the
next
step
is
once
the
follow-up,
and
the
first
issue
here
is
done
where
I
can
then
set
an
event
to
transition
to
that
page.
So
a
long
way
of
saying
it's
in
review,
it's
almost
done
and
yeah
it's
going.
Well,
then
we
can
look
at
closed
issues.
A
I,
don't
know
if
there's
going
to
be
any
for
this
Milestone,
but
I
can
look,
there's
a
bookmark
dashboard
list
of
issues.
So
this
one
here
from
Axel
is
the
only
close
issue
that
we
have
for
now.
It
is
fix
the
method
to
get
rid
to
get
grid,
attributes
on
Pi
dashboards,
I'm,
not
actually
sure
what
this
was.
Oh,
it
was
a
Fallout
for
me.
D
Yeah
so
I
went
to
signal
boost
the
merge
request
that
I
put
in
probably
the
last
week
before
I
had
it
on
vacation.
We
didn't
really
get
a
chance
to
talk
about
it,
but
it's
linked
in
the
agenda
and
it's
about
the
the
cross
stage.
Data
vision
and
what
this
page
is
really
trying
to
articulate
is
a
vision
around
how
the
analytics
section
should
really
become
the
single
source
of
Truth
for
anyone,
that's
trying
to
send
data
into
gitlab
as
well
as
consume,
gitlab
related
data
from
gitlab.
D
This
is
so
that
folks,
don't
necessarily
build
the
exact
same
thing
multiple
times
in
different
functional
groups
or
as
customers,
just
because
they're
unaware
of
what
other
functional
groups
have
done.
There
there's
quite
a
bit
there.
So
so,
please
take
a
read
through
it.
When
you
get
a
chance,
I
would
love
to
have
questions
feedback
discussion
as
well
as
edits
to
it.
If
we
want
to
make
some
changes,
it's
happy
to.
If
there's
any
sync
comments
now
or
we
can
talk
asynchronously
once
once,
you've
had
a
chance
to
read
through
it.
C
Yeah
I
think
I've
kind
of
already
spoken
about
this,
but
there's
a
link
to
the
screencast
I
mentioned
a
minute
ago
about
how
I
will
see
funnels
could
work
and
how
we
would
create
Dynamic,
keep
schemas
and
feel
free
to
have
a
watch
and
ask
any
questions.
You've
got
I'm
going
to
try
and
sort
of
expand
on
it
slightly
today
and
tomorrow.
So
much
further.
We
get.
D
Cool
cool
yeah,
my
question
just
to
vocalize
it
for
the
recording
was
in
the
demo
Max
you
were
showing
that
there's
a
time
to
convert,
parameter
and
I
was
curious.
If
that's
for
the
entirety
of
the
funnel
or
the
time
between
different
steps.
C
Yeah,
so
that's
the
entirety
of
the
funnel,
so
someone
can
compose
their
session
and
come
back
and
complete
the
funnel
later.
If
we
want
to
add
time
between
steps,
so
it's
definitely
something
we
could
do.
It
may
be
beyond
my
SQL
query
skills
right
now,
but
it's
well
within
the
balance
of
possibility.
I
think.
D
Cool
yeah
I
think
that's
probably
good
for
for
now,
if
we
get
feedback
that
we
need
something
a
little
more
granular,
we
can
address
that
later.
Yeah.
B
Cool
and
I
think
I
have
the
final
Point
just
like
one
more
question,
for
example,
but
just
for
like
the
group
in
general,
we
did
have
a
quarterly
goal
to
try
to
get
make
steps
towards
instrumenting
the
gitlab
project
for
gitlab
team
members
as
part
of
our
internal
preview.
So
We've
achieved
our
first
Milestone
there
with
the
internal
handbook,
but
then
we
want
to
go
a
little
bit
further
out
there
I
believe
Sam.
B
You've
we've
worked
on
like
a
communication
plan
just
from
like
a
general
sense
in
terms
of
like
getting
more
external
with
our
announcements,
and
things
like
that.
I
just
wanted
to
follow
up
on
that
and
if,
if
you
need,
if
it's
not
taking
time
to
refresh
yourself
on
that,
then
that's
totally
fine.
But
I
was
curious.
If
we
have
any
more
like
drafts
that
we
need
to
review
or
start
looking
at
for
specific
to
this
part
of
the
rollout.
D
Right
so
my
think,
thinking
for
the
people
that
work
at
get
lab,
so
internal
get
lab
folks,
we
can
follow
a
pretty
similar
path
to
what
we
did
for
the
internal
handbook.
It's
really
what
we
want
to
and
need
to
do
for
external
people
that
use
the
gitlab
project.
D
So
what
I
was
thinking
about
before
was
some
sort
of
blog
to
communicate.
Basically,
what
we
had
in
the
internal
slack
message,
but
as
a
blog,
post
and
I
believe
we
also
need
to
work
with
legal
on
our.
Was
it
one
trust
to
get
the
the
cookie
consent
or
something
around
there?
Updated
I
haven't
spent
any
time
on
that
recently,
though,
so
not
not
sure
what
we
would
need
to
do.
There
specifically
yeah.
B
I
think
we
can
kind
of
have
so
whether
it's
run,
trust
or
not.
I
do
believe.
That's
the
the
long-term
goal
is
that
we
can
bring
that
into
the
product
itself
since
we're
using
that
outside
of
the
product,
but
some
type
of
consent
in
or
opt
in
and
out
mechanism,
at
least
for
the
team
members
and
then
whatever
that
will
look
like
for
external
users
as
well.
B
It
can
be
developed
while
we
figure
out
what
our
communication
plan
is
going
to
be,
but
it
sounds
like
for
at
least
for
the
team
members
as
part
of
this
rollout,
we'll
just
continue
to
follow
what
we're
doing.
What
we
did
previously
did.
I
understand
that
correctly.
D
That
would
be
yeah,
that'd,
be
my
expectation.
Unless
we
hear
different
from
legal
because
do
we
have
the
ability
to
segment
say
you
are
Sam
and
you
work
at
git
lab
so
we'll
track
you
versus
you're
anonymous.
We
won't
look
at
you
or
you're,
a
community
contributor
we're
not
going
to
look
at
you,
I,
don't
remember
if
we
have
that
ability,
no.
C
C
I
mean
that
that
would
absolutely
work
as
a
first
step.
It
would
then
affect
anything
that
any
of
us
did
on
any
project
within
gitlab,
as
opposed
to
just
the
gitlab
project,
but
but
okay
with
that
I
don't
know
what
other
legal
issues
there
are.
B
Though
I
mean,
as
far
as
I
can
remember,
I
mean
yeah,
we'll
still
have
to
double
check,
and
we
should
anyways
kind
of
double
sync
up
with
legal
on
on
this
part
of
the
rollout
but
I
think
similar
reasons
for
the
internal
handbook,
mixed
in
with
the
consent
model
that
we
have
to
still
to
be
determined,
but
also
the
small
group.
It
should
be
relatively
okay.
C
B
B
B
Cool
well,
it's
good
to
see
everyone
happy
New,
Year,
happy
2023
.
and
if
there's
nothing
else,
then
we'll
see
you
in
the
next
haul.
Talk
soon
see
ya.
Take
care,
bye,.