►
A
D
E
D
Cool
yeah,
so
I
I
cannot
work
on
that,
so
we
should
remove
that
from
this
iteration
and
then
the
next
one
is
so
there's
additional.
We
like
missed
some
events
for
some
of
the
trial
flow.
So
that's,
I
think
what
that
data
layer
event
is.
So
what
will
probably
happen
is
I'll?
Do
the
namespace
id
stuff
it'll
end
up
in
review
while
waiting
for
that
to
get
reviewed?
D
F
Yeah,
what's
on
here
is
there
was
an
issue
to
remove
some
solutions
pages,
but
I
grabbed
that
on
friday
and
that's
closed
already,
there's
one
on
here
for
the
what
is
git
lab
to
y
git
lab
redirect
and
then
the
pricing
calculator
issue.
I
have
a
few
questions
on
that.
I'm
wrapping
that
up
and
I
think
it's
in
a
good
spot
to
be
reviewed,
but
who
all
needs
to
review
something
like
that.
Just
from
experience
at
my
previous
company,
like
calculators,
are
something
so
many
people
want
to
review
before
it.
F
D
C
D
If
you
I,
I
would
even
just
to
like
keep
it
super
simple
sort
of
like
tagging.
A
bunch
of
people
in
reviews
like
do
samia
and
jess
and
be
like
you
know,
is
this
right
just
does
this
look
good
and
then
samia
should?
It
know
like
if
there's
like
legal
concerns,
we'll
probably
tag
in
the
appropriate
people.
F
Yes,
I
was
gonna,
do
that
and
one
final
question
on
that
I
keep
seeing
for
context,
isn't
an
issue
for
next
iteration
to
finally
add
that
to
the
actual
pages
and
migrating
those
old
calculator
pages
to
our
new
repo.
I
keep
saying
mentioned
to
the
pricing
page
or
there's
a
pricing
calculator
which
seems
very
different
than
the
roi
calculator.
Am
I
also
supposed
to
make
a
pricing
calculator
or
is
that.
G
I
don't
have
a
ton
of
experience
with
animation,
so
I
don't
want
to
underestimate
how
long
it
will
take
me
I'll,
be
mainly
working
on
that
and
then
I
have
these
other
two
issues,
which
are
the
slipper
cards
component,
which
I
talked
to
nathan
and
jess
a
bit
about
them
that
it
was
not
completely
clear
what
I
should
be
doing
with
those,
and
it
was
decided
that
it
needs
more
refinement
as
an
issue.
So
I
don't
know
if
I
should
let
them
go
or
set
them
somewhere.
So
people
know
that
they
need
info.
G
B
You
can
maybe
change
the
deck
status
to
refinement,
but
keep
them
under
you.
If
you
want
for
right
now,
so
then
we
can
and
then,
if
we
decide
that
we're
going
to,
let
them
go
from
you
and
someone
else
can
pick
them
up.
Then
we
can
just
reassign
them
down
the
road,
but
I
can
remove
the
this
iteration
from
these
or
you
can
as
well.
E
Okay,
so
for
me,
ga4
is
waiting
on
marketing
ops
to
enable
google
consent
mode
in
one
trust.
In
the
meantime,
I
can
start
on
the
ecommerce
data
layer
and
maybe
I'll
tag
tyler
or
someone
else
who
knows
the
gitlab.com
code
base
to
implement
the
data
layers.
Let's
see
and
then
edition
of
namespace
yeah,
that
one's
on
tyler,
the
next
one
over
is
zoom
info
they're
having
the
legal
discussion
today
with
adobe
and
so
I'll
probably
find
out.
If
we
can
move
forward
with
that
piece,
but
yeah,
it's
not
too
bad.
E
It's
just
tedious,
because
there's
a
lot
of
forms,
post
redesign
analysis
is
done.
We're
gonna
talk
about
it
on
wednesday's
call
yeah.
I
think
wednesday
data
studio
discrepancy
that
one
is
done.
They
were
just
wondering
why
there's
why
the
numbers
don't
match
up
between
their
dashboard
and
the
one
that
I
made,
and
I
did
a
bit
of
a
write-up
so
I'll,
just
close
it
out
once
they
reply.
B
You
can
have
them
send
the
code
to
me,
I'm
kind
of
now
primary
contact
with
them,
because
once
I
get
the
code
there's
a
couple
other
line
items
to
like
add
our
privacy
policy
yeah
there
so
like
I'm
gonna,
send
them
one
big
thing
of
like
here's
code
put
this
in
and
then
add
these
couple
links
to
the
footer,
so
just
send
it
to
me.
Okay,
do
you
know
who
it
is
by
the
way
the
irs
or
the
who
runs
it?
Yeah.
B
B
It's
something
for
removing
something
from
the
home
page
about
an
old
tenno
announcement
that
was
updating
things
on
the
homepage,
but
it's
it's.
I
think
it's
gonna
be
a
small
thing.
I'll
get
an
issue
for
this,
and
obviously
I
might
I
don't
know
if
I'll
tag,
one
of
you
in
it
right
away
or
just
you
guys
can
pick
it
up
if
you
have
time,
but
it
looks
like
it's
just
removing
something
from
an
old
template:
that's
not
being
used,
but
it's
causing.