►
A
Hey
everyone:
this
is
our
sprint
release,
video
for
the
conversion
team
for
digital
experience.
I
am
gonna
we'll
just
kind
of
popcorn
around,
but
I'll
start
with
jess
put
you
in
the
spot.
B
Yeah
I
this
sprint.
I
closed
out
the
y
ultimate
ny
premium
pages
and
ish
closed
the
commit
events
template
it's
kind
of
like
one
of
those
ongoing
things
will
change
as
we
as
they
pop
up
I'm
blanking
on
anything
else.
I
did
so.
Hopefully,
that's
it
I'll
pop
it
over
to
dennis.
C
Oh
okay,
I
was
not
expecting
that
ga4
update.
So
from
a
legal
point.
I
got
noticed
yesterday
from
eugene
about
at
first.
I
thought
I
was
going
to
be
closing
it
off
for
the
entire
eu,
but
turns
out
it's
only
four
countries
now,
which
is
a
good
compromise:
italy,
austria,
norway
and
france,
so
we'll
lose
some
data,
but
I'm
hoping
that
the
machine
learning
algorithm
in
ga4
will
be
advanced
enough
where
it
can
kind
of
fill
in
the
gap,
but
we'll
see
in
terms
of
implementation.
C
I
we
updated
the
gtag
consent
code
and
in
order
for
me
to
test
it
out
fully,
I
made
a
new
issue.
Let
me
share
this
one:
it's
basically
blocking
tag
manager
from
loading
freely.
The
user
has
to
accept
this
category
number
two
which
is
for
performance.
C
However,
you
know
we
have
multiple
categories
like
advertisement
and
functional,
so
we
should
remove
that
and
I
already
have
the
rules
set
on
each
tag.
So,
for
example,
this
is
a
bing
tag
and
it
will
only
fire
if
the
user
consents
to
advertising
cookies.
So
you
know
we
can
remove
that
logic
and
yeah.
C
So,
just
let
me
know
this
one:
the
sas
trial
flow
so
tyler
handed
this
one
off
to
javi
it'll,
just
kind
of
like
sit
in
the
back
burner
for
a
while
when
javi
has
time,
he'll
kind
of
work
through
that
which
is
basically
tracking
if
people
accept
the
terms
or
if
they
land
on
the
welcome
page,
etc.
C
The
cookie
policy
on
the
partner
site.
I
think
we
did
that.
I
think
I
saw
a
couple
of
cookies
that
weren't
supposed
to
show
up
when
I
denied
content
consent.
I
think
jameson
was
supposed
to
rerun
onetrust
to
rescan
the
website
and
he'll.
C
Let
us
know
when
that
is
complete,
and
then
I
just
have
two
ad
hoc
reports
here
for
keeping
the
resource
page
and
then
cta
clicks
for
the
growth
team,
which
will
be
done
by
probably
friday
realistically
and
then,
aside
from
that,
I've
just
been
working
on
the
group
analytics
meetings
and
yeah,
I
will
popcorn
to.
C
D
Hey
thanks
two,
I
guess
smaller
things.
Margareth
was
out
for
a
few
days
this
sprint.
So
I
helped
a
little
bit
on
some
outstanding,
mrs
that
she
had
open.
There
was
an
issue
for
on
the.
Why
ultimate
page,
I
think
it
was.
There
was
a
security
risk
mitigation
link
that
was
going
to
a
page
that
no
longer
existed
so
fix
that
link
to
go
somewhere
else
to
a
page
that
did
exist,
but
primarily
working
on
the
commit
page.
D
I'm
just
trying
to
get
all
I
could
done
kind
of
following
just
as
like
work
in
progress
sigma.
So
that
was
fun.
I'm
glad
things
didn't
change
too
much,
but
got
a
lot
accomplished.
D
I
think
we
may
be
in
a
good
spot
depending
on
how
content
comes
in
and
just
little
tweaks
you
have
to
make.
I
think,
we'll
be
in
a
good
spot
to
hand
over
for
review
monday
morning
on
schedule,
but
yeah.
Hopefully
I
can
show
that
off
in
the
next
iterations
demo,
but
I'll
pass
it
over
to
gabby.
E
Yeah
so
this
print.
For
me,
I
finished
the
typography
updates
with
justice,
help
that's
going
out
with
the
slippers
update
and
I've
worked
on
the
white
premium
page.
So
my
premium
page-
it's
mostly
done
done
component
based,
but
it
needs
the
sidebar.
That's
also
coming
out
with
the
new
slippers.
So
I'm
waiting
on
that
to
make
it
available
for
review
since
the
typography
and
icons
have
changed.
I
need
that
to
be
able
to
look
at
their
reality
and
that
one
grew
a
little
bit
because
of
content.
E
So
this
page
before
used
to
pull
from
a
jml
file,
that's
called
features
that
was
in
the
dot,
dot,
dot
dot
repository
and
I
talked
to
a
bunch
of
people
to
figure
out.
What
should
we
do?
E
Where
should
we
pull
the
information,
because
this
file
was
previously
moved
to
our
buyer
experience
ripple,
but
it
was
segmented
into
files
into
smaller
files
that
were
stage
base,
which
is
not
how
the
ultimate
premium
page
organizes
stuff,
and
we
got
a
comment
from
the
owner
of
the
page
that
said
that
they,
this
is
a
page
that
they
update,
often
the
data
on
the
features
and
that
the
one
we
already
have
moved
is
probably
already
what
is.
E
It
called,
not
updated
it's
left
behind
and
that
this
is
a
much
broader
conversation
because
they
linked
me.
I
talked
to
nathan
because
he
was
involved
with
this
file
before
and
it's
been
used
by
several
other
teams
and
there
was
an
idea
of
segmenting
it
before,
but
it
got
scratched
because
they
said
it
was
gonna
mess.
E
I
think
some
automations,
but
that
in
summary,
it
got
really
really
big
and
I
got
told
that
I
should
stop
it
as
it
is,
and
just
talk
to
in
the
retro
about
what
we're
gonna
do
with
this
file,
because
it's
it
became
a
very
big
issue
that
we
need
to
figure
out
who's,
gonna
update
that
or
if
we're
gonna
handle
something.
E
That's
not
perfectly
updated
all
the
time
and
it
seems
to
be
a
lot
of
work
and
if
we're
gonna
move
it
or
not,
move
it,
because
I
need
to
add
more
information
and
our
files
have
already
been
updated
as
well.
So
they're
not
matching
out
so
this
group
significantly-
and
I
guess
we're
gonna
talk
about
it
at
the
retro
and
we're
going
to
figure
out
later
how
to
separate
this
from
my
issue.
So
yeah,
that's
where
I'm
at
with
popcorn
to
a
visit.
F
Okay,
so
two
sprints,
I
finally
finished
the
some
test,
fixes
that
a
little
a
very
small
task,
then
one
of
the
materials
tasks
was
the
scroll
button,
which
was
a
not
big
task,
but
it
it
means
a
lot
of
new
things
for
me
because
it
was
a
slippers,
slippers
component,
but
I
need
to
I
needed
to
prove
to
preview
that
component
with
that
that
are
working
good
in
the
in
the
boyer's
experience
because
the
functionality,
so
it's
not
a
very
independent
component.
F
F
So
I
don't
need
to
upload
all
a
push
push
the
commit
stat.
It
will
be
a
very,
very
lot
of
stuff
other
redirect
and
some
redirection
issue.
That
sounds
easy,
but
at
the
end
I
I
try
to
discover
the
better
the
best
solution.
I
I
implement
some
routine
server
middleware
that
will
that
it's
in
my
death
in
my
death,
my
dev
environment,
works
very
good,
but
I
discovered
that
in
the
stage
state
static
target
of
the
nox
doesn't
work.
F
So
at
the
end,
I
will
need
to
implement
a
very
basic
component-based
redirection
to
the
page,
the
it's
a
bad
stop,
because
it
means
that
the
component
will
a
lot
information
and,
I
think,
will
not
use
it
and
I
will
help
w3
with
all
the
white
white
premium
pitch
and
the
data
manipulation
that
it's
look
a
lot.
It
looked
very
very
complicated
because
that
segmentation,
but
that's
why
we
are
here
to
figure
to
figure
out
how
to
do
the
best
best
approach.
A
I
can
just
jump
in.
I
was
gonna
speak
for
tyler.
I
know
tyler
is
out
today.
He
I
think
he
got
the
ga4
content
security
policy
up
this
sprint.
Remember
correctly,
dennis
he
helped
javi
like
transition,
some
of
his
issues
over
to
javi
to
get
into
the
product
and
some
of
the
other
environments
as
well,
and
then
I'll
jump
in
and
yeah
like,
like
dennis
said,
we
got
the
one
trust
script
on
the
ir
site.
A
We
got
also,
they
had
them
add
in
the
privacy
policy
and
cookie
links
the
footer
for
the
ir
site
with
help
from
jess
on
the
just
some
design
make
sure
it
was
correct
per
our
for
our
brand.
So
those
should
be
good
and
then
dennis
you
have
to.
If
they
come
back
that
they're,
I
don't
think
they
we'll
need
to
do
anything
on
the
irs
site.
A
But
if
there
is
some
like
questions
about
like
how
things
are
set
up
that
we
need,
I
need
to
reach
out
to
them.
Just
let
me
know
we
can
kind
of
work
through
that
and
I
think
that's
about
it.
Does
it
have
anything
else.