►
From YouTube: 2023-03-13 Analytics Section Meeting
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
All
right,
hello,
everyone
and
welcome
to
the
analytics
section
sync
on
the
13th
of
March
I,
think
I
have
the
first
topic
and
I
just
wanted
to
give
everyone
a
short
update
around
the
current
state
of
the
Jitsu
to
snowplow
conversion,
because
I
think
not.
A
Everyone
is
kind
of
following
along
there
for
some
of
you
who
are
new
to
the
sections
of
this
whole
topic
might
be
kind
of
new,
and
so
I
wanted
to
just
make
sure
that
everyone
kind
of
knows
where
we're
at
right
now
and
also
what
input
is
still
needed.
So
we
generally
want
to
switch
from
Jitsu
to
snowplow
as
the
underlying
technology
for
our
for
the
product
analytics
sector
collect
the
events.
A
We
already
have
the
initial
snowplow
setup
merged
into
the
dev
kit.
So
if
you
want
to
try
it
out
or
something
you
can
go
to
the
analytics
dev
kit,
there's
part
of
the
readme,
where
you
can
see
how
you
can
set
it
up
in
addition
to
Jitsu.
So
it
runs
in
addition
to
it.
It
shouldn't
kind
of
impact.
Your
data
to
work
with
your
analytics
stack
in
any
way.
You
can
just
see
it
running
in
addition
to
the
to
the
current
pipeline.
A
I
also
created
a
short
video
intro
to
snowplow,
to
give
a
short
intro
on
how
it
works
and
yeah
try
to
give
a
bit
of
an
overview,
there's
probably
still
a
lot
of
things
open,
since
it's
can
do
quite
a
lot
of
things.
So
if
you
have
more
questions
or
need
for
further
introductions,
then
let
me
know.
A
And
then
we
have
the
gitlab
JavaScript
SDK.
So
the
thing
that's
currently
also
implemented,
I
think
on
the
internal
handbook,
that's
kind
of
close
to
being
merge
ready.
We
need
to
hold
off
on
the
merge
right
now
because,
as
soon
as
we
would
would
merge
it
in,
it
would
automatically
update
currently
on
the
in
the
handbook-
and
we
don't
have
the
cluster
on
the
other
side,
ready
to
handle
the
snowplow
events,
so
that
would
kind
of
break
the
whole
flow.
A
So
what
we
I
think
and
thanks
to
Rob
for
bringing
that
up
again,
I.
What
we're
probably
going
to
do
is
add
versioning
to
the
gitlab
SDK
first,
so
that
we
can
have
a
old
version
with
the
with
the
Jitsu
integration
running
on
the
handbook,
already
start
merging
in
a
new
version
with
a
snowplow
and
then
just
switch
the
the
handbook
independently
of
of
continuing
to
work
in
the
repository,
so
that
you
have
because
currently
the
the
kitlab
SDK
is
not
versioned.
A
A
What
what
we
can,
where
we
can
decide
to
use
certain
things
or
not,
I
think
what
Max
I
think
already
pointed
out,
which
is
kind
of
kind
of
funny,
is
that
snowplow
still
has
columns,
for
example,
for
whether
a
real
player
is
enabled
or
not
or
Flash,
is
active
or
not
on
a
certain
browser,
and
so
those.
A
Yeah
so
begins
to
make
some
decision
decisions
around
that
and
then
also
around
kind
of
how
we
want
to
handle
API
keys
and
app
IDs
and
abuse
protection
in
the
beginning,
because
snowplow
also
doesn't
really
provide
something
out
of
the
box
there,
and
both
issues
are
open.
You
can
add
your
opinion
there.
A
We
can
continue
discussing
there
if
we
don't
come
to
a
conclusion,
I
added
a
a
sync
meeting
for
Thursday
afternoon,
European
Time
and
invited
so
far
the
people
that
were
so
far
involved
in
the
discussions
so
that
we
can
make
a
decision
and-
and
then
like
move
on
from
that
point,
because
this
is
kind
of
a
blocker
to
continuing
to
work.
B
So
that
will
be
then
the
next
step
to
create
the
cube
schemas
and
based
on
that,
we
can
then
also
prepare
all
the
kitlab
analytics
front-end
stuff
so
that
we
use
the
new
field
names.
We
use
the
new
schema
there
for
the
existing
dashboards
that
we
are
rolling
out
and
also
for
the
visualization
designer
and
basically
can
prepare
a
switch
over
that
as
soon
as
we
are
reporting
data
over
there.
B
Then,
in
the
next
couple
of
days
we
basically
emerge
and
have
our
Mr
ready
to
basically
cut
over
to
the
new
data
source.
Then
in
our
internal
handbook
project
and
we
can
go
from
there.
D
Yeah
I'm
trying
to
think
how
that
works
on
the
back
end
because,
yes,
we
need
snowplow
in
the
cluster
environment,
but
then,
as
well
like
we'll,
have
to
update
the
internal
handbook
with
the
new
version
of
the
SDK
to
start
sending
new
events
over
to
snowplow,
we
would
have
the
dashboards
would
still
report
on
the
Jitsu
tables,
but
then
we
would
upgrade
the
cluster
so
that
the
schema
is
updated
on
the
cube
and
and
I'm
saying
this
out
dot.
D
So
I
can
record
write
it
down
on
the
issue
later
on
the
recording
but
anyways,
we
would
upgrade
the
cluster
to
switch
over
from
the
Jitsu
to
the
snowplow
schema,
and
then
we
would
push
the
update
to
the
visualization
designer,
if
needed
at
all
or
any
of
the
front
end
views
which
shouldn't
be
the
case
actually
yeah.
D
B
We
just
need
to
update
the
the
affiliate
names
of
all
the
measurements
in
the
existing
dashboards
yeah
and
in
the
visualization
designer
the
ones
that
are
basically
created
for
those
is
really
a
very
minimal,
and
then,
after
that,
we
can
take
a
look
to
to
incorporate
all
the
nice
things
we
get
through
the
plugins
and
enrichers
in.
D
Just
wanted
to
make
sure
I
had
the
right
order
of
operations
to
make
sure
we
don't
switch
something
earlier
than
or
before.
Something
should
happen
at
the
same
time
too,
just
so
I
I
also
don't
forget
somewhere
in
that
switch
over.
We
need
to
fit
in
where
we
bring
the
old
data
into
the
new
one
and
we'll
have
a
better
idea
of
how
to
do
that
when
we
make
the
decision
by
Thursday
on
what
schema
like
what
attributes
we're
going
to
use,
or
we
can
just
completely
digit.
B
E
C
I'm,
assuming
that
every
column
that
Cube
has
other
Jitsu
has
there's
a
pretty
much
analogous
Dimension
or
column
in
snowplow,
we'll
be
making
sure
that
in
the
custom
queries
we've
got
in
cube
right
now,
so
it's
specifically
session
analysis
and
funnel
analysis
that
we're
making
use
of
the
correct
new
columns
and
to
make
sure
that
we've
got
that
right,
I've,
not
logged
into
it
in
details,
just
flagging
it
up
now
is
the
only
thing
I
can
think
of
that's
going
to
potentially
cause
this
difficulty.
D
D
C
C
A
Well
thanks:
everyone
I
just
want
to
again
point
out
what
I
think
Tim
mentioned
very
briefly
beforehand:
here's
these
plugins
and
enrichers
for
snowplow,
so
there's
also
two
open
issues
around
that
and
kind
of
which
ones
we
want
to
use
in
the
in
the
future.
So
just
so,
everyone
knows
that
plugins
is
whatever
you
add
to
the
actual
SDK.
So
what's
getting
collected
with
the
with
the
user,
for
example,
error
tracking
data
performance
time
and
data
and
riches
are
things
that
snowplow
ads
kind
of
in
the
pipeline
later
on.
A
So,
for
example,
on
based
on
the
user
agent
string,
you
might
kind
of
try
to
figure
out
which
device
it
actually
is
or
based
on
the
IP
address.
Do
you
locate
a
user
and
we
have
open
issues
around
those,
so
I
think
those
are
also
free
for
discussions
around
which
ones
we
should
building
by
default,
which
enriches
and
plugins
or
which
ones
we
might
just
want
to
kind
of
support
optionally
in
the
future,
but
I
think
both
of
those
are
not
as
time
critical
as
configuring
out
the
schema.
First.