►
Description
In this video, GitLab marketing's Digital Experience team is learning about how we use Marketo on the about.gitlab website.
We start with a big picture overview of what Marketo does and eventually get into implementation details with code paths.
Agenda doc: https://docs.google.com/document/d/1xi-VeTJDNqg3lj9TkYzzPsXV74hi9SvjWAlnq8iDbBU/edit#
Handbook page: https://about.gitlab.com/handbook/marketing/marketing-operations/marketo/
A
A
You
know
it's
a
marketing,
automation,
tool
that
people
may
or
may
not
have
a
lot
of
experience
with,
and
so
we're
going
to
be
doing
a
little
bit
of
a
knowledge
share
for
the
rest
of
our
front-end
developer
team
here
and
full
stack
as
well,
and
you
know
anyone
else
who
wants
to
learn.
So,
let's
get
started
first
off.
Who
are
our
company
partners
for
marketo?
A
So
you
know
in
the
digital
experience
team
we
may
be
asked
to
update
a
form
or
something
and
or
or
create
a
form,
and
you
know
that
may
not
be
the
right
route,
but
marketing
ops
is
the
team
that
we
work
with,
in
particular,
amy
waller
who's
in
charge
of
the
marketo
tool.
You
know
is
basically
who
we
ask
for
a
lot
of
these
kind
of
questions.
A
You
know
she
she's
knowledgeable
at
the
tool
and
the
you
know
how
to
implement
it.
Sort
of
side
of
things
and
we're
kind
of
more
the
you
know,
how
do
we
javascript
and
you
know,
css
and
put
the
form
on
a
page
sort
of
side
of
things
so
yeah
and
in
terms
of
who
on
our
team,
has
experience
with
it.
I
do
brandon
tyler
has
mentioned.
He
has
experience
with
it,
although
not
at
get
lab
yet
and
every
instance
is
different,
as
he
mentioned,
and
so
yeah.
A
What
is
marketo
marketo
is
a
marketing
automation
platform,
and
you
know
similar
tools
are
hubspot
or
pardot
or
eloqua,
and
what
that
means
is
basically,
these
are
tools
where
you
put
a
form
on
the
page,
and
you
know
someone
fills
out
the
form
and
you
can
automatically
reply
with
an
email.
That's
got
resources
or
something
like
that
is
one
aspect
of
it.
Another
aspect
is
basically,
if
you
are
sending
an
email,
you
know
to
follow
up
on
an
action
that
someone
took.
It
doesn't
have
to
be
a
forum
right.
A
It
can
be
a
sign
up
for
your
website
and
welcoming
new
members,
or
it
can
be
a
you
know
something
else
like
we
met
at
convention
center.
Here's
an
email
that
you
know
goes
over
how
to
use
our
stuff
or
or
any
number
of
things
really.
So
the
point
is
it's
lead
gen,
it's
a
lead
tool,
marketing
automation,
so
you
know.
Let's
say
your
subscription
is
about
to
expire.
They
can
send
you
an
email
stuff
like
that.
So
how
do
we
use
git
lab
or
how
does
git
lab
use
marketo?
A
A
You
know
all
these
tools
that
we
use
that
basically
prepare
sales
to
be
able
to
contact
people
who
need
information
about
gitlab,
and
so
you
know
how
do
we
do
that
actions
that
people
take
on
the
website
will
have
a
score
attached
to
them.
So
you
know,
let's
say
they
viewed
a
sponsored
webcast
that
gets
them
20
points
and
puts
them
into
a
bucket
in
the
marketo
back-end
system.
A
A
A
So
that's
how
kind
of
the
lead
qualifying
works
and
scoring
from
the
marketo
side
of
things,
and
it's
all
documented
on
those
handbook
pages
and
yeah
so
now
kind
of
on,
oh
and
before
I
go
any
further.
I
forgot
to
talk
about
this
earlier
as
well
at
the
top
of
the
the
agenda
dock.
Here
I
linked
a
page
that
is
an
epic
in
git
lab
that
basically
goes
over.
A
A
A
You
know
sign
up
forms
demo
page,
you
know
things
that
are
of
high
importance
and
then
it
also
goes
over
the
different
kinds
of
forms
right,
so
let's
say
you
change
shared
code.
That
impacts
one
form
you
want
to
make
sure
you
didn't
break
another
form.
It's
got
kind
of
an
example
of
a
lot
of
the
different
forms
that
we
have
on
the
about
website.
A
So
where
do
we
go
from
here?
How
do
we
use
marketo?
So
one
example
is
a
lead
generation
form
I
talked
about
it
earlier.
You
know
basically
you're
on
the
demo
page
and
you
want
to
sign
up
for
something
you
know
you
fill
out
this
form
on
the
right
hand,
side
and
that's
a
form,
that's
generated
by
marketo,
and
you
know
it's
got
all
these
different
fields,
and
these
are
all
created
within
the
marketo
interface
itself,
and
you
know
then,
once
the
you
know,
it's
got
error
states
and
all
that
good
stuff.
A
A
A
You
know
thank
you
for
signing
up
your
free
trial
and
you
notice
the
page
scrolled
into
motion.
That's
the
the
form
scroll,
the
success
message,
scrolled
into
view,
so
that's
something
we
do
with
javascript
on
our
side.
So
yeah,
that's
that's
kind
of
examples
of
where
we
use
it
and
now
another
thing
to
be
aware
of.
If
you
are
in
a
region
that
is
impacted
by
cookie
consent,
laws
is
basically
what
happens
when
you
go
to
a
page
that
has
a
marketo
form.
A
A
Please
wait,
and
it
never
finishes
so
just
be
aware
that
cookie
consent
forms
can
impact
this,
and
the
reason
for
that
is
because
until
we
have
consent
to
set
cookies,
we
cannot
set
cookies
and
they're
legally
and
therefore
the
cookie
consent
platform
intercepts
before
marketo.
So
until
you've
accepted
you
can't
process
the
form.
So
that's
that's
kind
of
why
there's
this
weird
state
and
we're
looking
to
see
how
we
can
fix
that
long
term.
It's
obviously
not
an
ideal
user
experience,
but
it's
just
something
to
be
aware
of
as
we're
working
in
marketo.
A
So
there
we
could
do
that.
The
reason
we
haven't
done
that
basically
this
was
a
quick
fix.
We
would
love
to
refine
the
user
experience
and,
if
you
put
a
pop-up
on
the
page
before
someone
fills
out,
the
form,
I
think,
is
the
idea
that
therefore
they
don't
want
to
fill
out
the
form
because
they
don't
want
to
consent
to
cookies,
and
so
like
it's,
it's
kind
of
the
user.
Investment
right,
like
I've,
already
started
to
fill
out
the
form.
A
A
B
A
A
A
C
A
C
Oh
cookiebot
gives
us
act
like
we
don't
have
to
do
that.
Custom
like
we
get
some
hooks
back
from
cookiebot
that
we
could
customize
with
that.
I
think
the
other
thing
here
for
consideration
just
that
we'd
have
to
work
with
is
like
I
haven't
seen
how
we
do
our
marketo
forums,
but
like
the
marketo
forums
I
have
embedded
in
websites,
are
like
they're
individualized.
So
like
there's,
not
we
like.
We
can't
write
like
a
like
one
handler
that
affects
all
of
the
form
submission
processes
they
want
to
get
their
custom
ones.
C
So,
like
it's
just
it's
one
of
those
things
where
it's
like,
we
certainly
could,
but
there's
probably
a
lot
of
far-reaching
implications
of
making
it
like
it's
a
it's
a
bigger
task
than
just
the
technical
solve
it's
like
find
where
to
do
it.
Why
to
do
it
make
sure
it
doesn't
impact
existing
assumptions
that
each
one
of
these
individual
forms
makes.
A
Yeah,
so
part
of
it
is
that
the
forms
aren't
something
that
we
have
static
on
our
side.
They
are
dynamically
generated
on
the
marketo
side
by
program
managers
who
say,
I
need
a
form
to
sign
people
up
to
this
event
or
something
like
that,
and
so
the
code
will
be
a
little
different
every
time.
So
we
don't
have
control
over
the
html
that
marketo
returns.
To
my
knowledge,
we
don't
have
control
over
their
css
or
javascript.
We
can
hook
into
their
events.
A
You
know
like
clicking,
submit
and
stuff
like
that,
and
we
can
hook
into
cookie
bot's
events.
That
say
you
know
basically
cookie
bot
consent
has
not
been
given.
We
can
try
and
attach
listeners
to
those
buttons,
and
we
may
have
some
level
of
success.
I
don't
know
but
anyway,
so
so
that's
just
to
give
an
example.
You
know
here's
the
javascript
that
we
have
running
shared
for
the
marketos
forums
on
some
of
these,
and
you
know
you
can
say
you
know,
here's
some
set
options
for
the
market
forms.
A
Here's
where
you
load
the
form
onto
the
and
append
it
to
the
page.
Basically,
you
take,
you
know,
you
say:
hey
marketo,
give
me
this
form
and
they
say:
okay.
Here,
I'm
going
to
insert
it
into
the
div
specified,
and
then
you
have
an
on
success
event,
which
basically
says
once
the
button
has
been
pushed
and
the
form
is
successfully
submitted.
Do
all
these
other
callbacks,
which
is
where
we
have
our
google
analytics
data
layer
push,
and
you
know
on
some
other
forms-
demand
demand
base.
A
Okay,
so
here
we
go
so
some
of
the
demand
based
actions
and
other
things
like
that.
So
but
this
is
a
long
way
of
saying
to
sami's
point
that
is
not
an
optimal
user
experience,
it's
something
we
could
refine
and
you
know
if
we
we
had
the
resources
to
do
that,
and
you
know
it
would
be
great
to
get
a
better
user
experience
going
for
that.
A
So
where
was
I
so
yeah
and
then
another
thing
you
know
I
mentioned
the
you
know
message
here:
having
trouble
viewing
or
submitting
this
form,
there
is
a
javascript
that
controls
how
to
generate
this
message.
It
differs
between
you
know,
submitting
this
form,
and
this
is
this
is
a
cookie
bot
attached
thing.
This
is
not
a
marketo
attached
thing.
This
is
just
something
that
we've
created
over
time.
That
says
you
know
cookie
bot
is
impacting
the
action
you're
trying
to
do
so.
A
It
can
be
attached
to
the
search
fields
in
the
header
of
the
about
website.
You
know
up
here
basically
or
on
the
handbook
or
blog
search
it
can
be
attached
to.
You
know
you're
about
to
watch
a
video,
but
you
can't
do
it
because
the
youtube
cookies
are
blocked
or
something
like
that
so
yeah,
that's
that's
just
another
thing
to
be
aware
of.
Is
this
cdxr's
javascript
awesome
and
go
ahead?
A
Cool
yeah,
and
so
another
thing
I
just
wanted
to
mention
is
the
importance
of
regression
testing
on
these
forms.
I
know
I
brought
it
up
earlier,
but
if
you
update
one
of
these
javascripts,
it's
really
important
to
go
over
the
important
workflows.
We
don't
want
to
break
the
pricing
page.
We
don't
want
to
break
demo,
we
don't
want
to
break.
You
know,
contact
sales,
these
kinds
of
things.
A
D
A
D
And
if
we're
doing
manual
testing
like
I
saw
you
writing
like
test
data
like
test
test,
one,
two,
three,
four,
five,
six,
seven,
I
don't
want
to
be
like
messing
with
sales
numbers
or
like
submitting
a
ton
of
forms
with
dummy
data.
So
is
there
a
typical
convention
that
we
use
for
the
state
and
the
email
and
whatever.
A
As
far
as
I'm
aware,
there
is
not,
I
have
asked
about
it
in
the
past,
and
I
have
been
told
that
you
know
certain
cleanup
scripts
or
you
know
bad
data
will
be
flagged
and
stuff
like
that.
So
theoretically
it
should
be
fine.
You
know
if,
if
we
go
back
to
that
lead
scoring
sort
of
work
or
yeah,
there's
a
flowchart
here
on
the
handbook
page
that
got
basically
goes
over.
A
You
know
how
the
market
is
scoring
works
and
so
there's
you
know,
here's
the
raw
data
it
goes
to
and
it
becomes
an
inquiry.
You
know
they
have
an
email
address
attached.
It
goes
to
the
qualified
lead
system
and
you
know
basically,
if
it's
bad
data,
it's
just
gonna,
go
here
and
then
get
set
to
zero
and
then
or
or
over
here,
to
bad
data,
and
then
you
know
remove
from
the
system
and
there
are
certain
things
that
automatically
get
checked
for
so.
But
that
is
a
good
question.
A
I
know
at
my
previous
company.
We
did
not
have
that
sort
of
a
setup,
and
so
you
know
it
was
important
to
kind
of
have
a
certain
thing
appended
to
the
end
of
an
email
address
that
you
were
trying
to
do.
That
says:
hey
I'm
doing
this
on
dev
and
test
not
on
production
or
whatnot,
so
yeah,
some
other
things
to
be
aware
of
are
basically
you
know
I
already
mentioned.
If
you
select
united
states,
another
drop
down
appears
kind
of
similar
things
can
appear.
A
So
if
you
select
ukraine,
I
don't
know
if
this
is
still
true,
but
basically
there's
this
extra
check
box.
That
says
I
do
not
live
in
the
crimea
region.
You
know,
because
of
all
the
geopolitical
sort
of
I'm
trying
to
think
of
the
term,
but
basically
you
know
trade
restrictions
and
that
kind
of
thing,
so
there
are
little
subtleties
like
that.
The
other
thing
is,
you
know,
sometimes
we'll
get
from
ux
teams
or
whoever
else.
A
I
don't
want
someone
to
have
to
select
these
check
boxes
manually
like
I
want
it
pre-selected
or
something
like
that.
Legally,
we
can't
do
that
because
of
privacy
laws.
You
know
in
certain
regions
such
as
gdpr,
california's,
ccpa
and
other
countries
have
similar
things,
so
it's
off
by
default.
Legally,
it
has
to
to
do
that
sort
of
thing.
If
you
ever
have
any
questions
about
that
feel
free
to
reach
out
to
amy.
A
You
know
who
are
the
stakeholders
in
the
marketo
system?
A
lot
of
it
is
done
for
demand
generation.
You
know,
let
me
zoom
in
here.
This
page
is
kind
of
zoomed
out
see
so
you
know
under
demand
generation
on
the
org
chart.
Here
you
see
marketing
programs,
so
jackie-
and
you
know
some
of
the
others
here.
Agnes
and
zach.
A
Do
a
lot
of
work
in
landing
pages?
That's
not
on
the
about.getlab
itself,
it's
from
in
the
marketo
system.
They
can
generate
landing
pages
and
we'll
go
over
that
in
a
minute
and
then
also
newt
here
is
really
great,
with
email
sends.
So
you
know
basically
how
we
get
our
newsletters
out
to
people
it's
built
in
marketo.
Marketo,
isn't
just
you
know,
gathering
those
things
it's
acting
gathering
the
leads
from
forums
or
wherever
it's
acting
on
them
too.
A
So
we
aren't
directly
involved
in
the
digital
experience
team
with
those,
but
we
will
sometimes
get
requests
for
assistance
like
hey
you're,
good
with
you
know,
front
end
html.
Can
you
help
me
out
with
this
email?
Or
you
know
we
need
a
graphic
or
something
or
on
the
landing
page
itself.
You
know
I
helped
jackie
create
landing
pages
in
marketo
so
that
they
could
create
their
own
pages
when
they
needed
it
without
having
to
go
through
the
about.gitlab
interface,
and
so
some
of
that
is
in
this.
A
This
is
an
example
of
what
one
of
those
pages
might
look
like
that's
generated
in
marketo.
It's
not
done
on
the
about
git
lab
website.
You
can
see
the
the
subdomain
page.gitlab
up
there
and
you
know
it
looks
pretty
similar.
It's
it's
styled
how
about
docket
lab
has
been
styled.
Historically,
there
are
options
on
this
page
to
basically,
you
know,
add
more
info
on
the
left.
Here.
They
can
go
in
and
use
a
wysiwyg
to
customize
the
messaging.
A
They
can
customize
the
form
itself
using
marketo.
They
can
add
images
up
here,
different
things.
So
it's
it's
a
highly
customizable
landing
page
system.
So
that's
just
something
to
be
aware
of
that.
We
did
build
that
for
them
and
we
may
get
questions
from
time
to
time
asking
can
we
work
on
it.
This
is
where
I've
kept
the
code.
It
there
wasn't
a
repository
for
it
before
it
was
just
you
log
into
the
marketo
interface
and
start
typing,
which
not
ideal.
A
A
Someone
has
to
type
in
a
you
know:
a
string
and
the
string's
default
value
is
highlight
white
and
the
id
that
that
string
is
attached
to
down
here
in
the
html
is
flex
one
color.
So
if
we
look
for
flex
one
color,
you
can
see
that
it's
down
here
and
there's
this
kind
of
bracketed
syntax
that
marketo
uses
flex.
One
color,
you
know
dollar
sign
bracket
variable,
so
that's
that's
kind
of
how
they
store
theirs.
A
C
C
You
could
use
for
that
right
so
like
if
you're
working
on
this
like
and
you
make
changes
here
in
the
repo
and
then
you
go
to
like
copy
paste
it
up
into
marketo,
like
you
may
have
a
couple
more
steps
left
if
marketo
is
like
hey
like
we
want
this
or
like
we
expected
this
value
so
like
you're,
not
quite
done
until
it's
like
past
the
linting
in
the
marketo
instance
itself,
which
is
just
like
an
extra
step
to
keep
in
mind.
If
you
end
up,
if
you're
like
doing
a
whole
bunch
of
it.
A
For
sure
very
true
and
the
the
editor
will
fortunately
tell
you
when
you
try
and
save
it
that
oh
some
is
wrong.
Usually
so
it's
it's
not
a
a
huge
deal,
but
it's
like
he's
like
he
said
just
something
to
be
aware
of
that.
You
know
it's
there's
more
to
it
than
just
copy
paste.
So
anyway,
let's
see
where
blah
blah
blah
okay.
So
who
else
are
stakeholders
for
marketo
systems?
The
product
growth
group
led
by
gila,
has
in
the
past.
A
Basically
anything
you
do
after
you
say,
click
on
a
registration
process.
You
know
it
takes
you
to
into
get
lab's
actual
sign
up
system,
it's
not
on
the
about.getlab
website.
It's
on
the
product
side
of
things,
that's
where
they
come
in
and
marketo
is
tied
into.
I
believe
some
of
these
sign
up
flows,
or
at
least
something
that
syncs
with
marketo.
So
sometimes
product
team
will
have
a
question
for
us
or
they
may
want
to
know
like
hey.
A
A
We're
focused
on
inbound,
leads
and
they're
focused
on
the
whole
nurture
process
of
a
buyer's
journey
after
they've
signed
up.
You
know
how
do
they
use
the
product?
What
you
know,
how
do
we
keep
them
retention?
So
it's
it's
acquisition
retention
and
you
know
that
sort
of
things.
It's
not
just
getting
leads.
So
that's
why
there
was
a
bit
of
separation
there,
but
yeah
sometimes
I'll
ask
us
questions
about.
A
You
know
what
we've
been
working
on
for
those
sorts
of
things,
yeah
so,
and
here's
kind
of
an
insight
on
the
org
chart.
I
linked
to
you,
know:
hela's,
the
director
of
product
growth
and
some
of
the
other
team
members
that
have
been
working
with
us
in
the
past
jensen
and
sam
and
mike
in
particular,
but
yes,
so
yeah
that
that's
kind
of
an
insight
into
things
we've
covered
so
far
who
the
stakeholders
are,
who
else
uses
marketo?
A
You
know
privacy,
related
laws
scoring
leads
and
where
you
might
find
a
marketo
form
on
the
about
website
and
yeah.
I
just
wanted
to
recap
that,
before
kind
of
moving
on
to
the
next
subject
of
programming
forms
for
marketo,
so
another
resource
I
linked
here
is
you
know?
Basically,
if
you
look
at
the
code,
you'll
see,
let's
see
blah
blah
blah.
I
haven't
looked
at
this
code
in
a
while,
so
apologies
first
off
this
is
the
file
that
I'm
looking
at
now
is
called
form
to
resource.
A
Basically,
this
is
used
by
a
lot
of
different
pages,
and
so
at
the
top
you'll
see
ruby
variables
that
get
filled
in
that
you
know
are
basically
later
placed
into
the
javascript
in
multiple
spots,
so
you'll
notice
at
the
top
here
there's
if
defined
webcast.
If
webcast
has
recording
you
know-
and
it's
not
just
webcast
right
but
webcast
is
one
particular
form
of
it,
so
other
things
that
we
other
types
of
categorizations
that
we
do
on
our
end,
that
says
you
have
viewed
a
webcast.
You
have
expressed
interest
in
the
demo.
A
You
have
started
a
trial.
You
know
this
is
a
white
paper
for
public
sector,
or
you
know
that
kind
of
thing.
So,
when
you
go
down
to
look
at
the
data
layer,
push
here
event
and
it
basically
says
the
type
of
form,
so
it's
important
to
know
that
that's
there
so
that
we
can
sort
leads
into
the
right
bucket
and
score
them
appropriately.
A
A
But
let's
see
here
an
example
of
a
page
where
that
form
is
used,
so
you'll
see,
form
type
or,
let's
see,
form
id
form,
type
webcasts
and
some
of
the
other
variables
that
get
passed
into
the
form,
so
that's
defined
in
the
front
matter-
and
you
know
this
is
kind
of
old
code
that
I
haven't
looked
at
in
a
while.
Obviously,
when
we
move
towards
a
cms-based
system
for
the
entire
website,
a
lot
of
the
stuff
might
change.
This
is
kind
of
how
it's
working
right.
Now,
let's.
A
Yeah,
so
that
is
a
good
question.
The
form
id
comes
from
whatever
marketing
partner
is
asking
us
to
put
a
form
on
the
page,
so
they'll
say
hey.
I
created
this
form
in
marketo,
it's
got
an
id
number
of
1592
or
something
like
that,
and
usually
they
don't
vary
a
lot
because
they
want
to
reuse
resources
as
well.
So
you
know
10
different
pages
might
be
using
the
same
form
and
what
the
id
impacts
is.
It
says:
hey
marketo:
where
did
that?
Google
doc
there
we
go
hey
marketo.
A
A
Cool,
so
how
are
my
kiddo
forms
applied
to
the
page?
So
this
is
basically
it's
not
as
self-evident
as
one
would
hope
right.
It
never
is.
Let
me
walk
and
talk
here
at
the
same
time,
so
you
can
see
that
the
page
starts
off.
The
form.
Isn't
there
so
what's
happening
is
javascript
is
fetched
from
the
marketo
system.
So
that's
way
down
here
where
it
says
you
know
basically
load
form,
and
then
it
gives
you
our
instance.
A
It
gives
you
our
instance
id
you
know
it
asks
you
what
domain
you're
loading
to
what
the
form
id
is
and
then
it
says,
put
the
you
know.
All
this
basically
says
put
the
form
on
the
page
and
so
the
the
pages
and
gets
the
form
appended
to
it
and
then
something
some
other
things
that
happen.
Html
is
appended
to
the
page
using
javascript
we
don't
control
their
html,
css
or
javascript,
but
what
we
then
do
is
we
run
javascript
that
resets
their
css.
Basically
they
append
it
to
the
page.
A
A
C
Okay,
just
pause,
you
would
you
mind
scrolling
up
a
few
lines
here
there
on
line
77
marketo
forms
two.
This
is
like
gotten
me
in
the
past.
That's
like
a
it's.
An
object
in
the
global
window,
object
that
gets
loaded
by
marketo
and
I
think
it's
the
you've
got
a
script
tag.
An
inline
script
tag
above
right.
Yes,.
C
So
like,
if
you
so
like
that
inline
script
tag
is
what
makes
marketo
forms
two
available
in
the
window
so
like.
If
one
of
two
things
has
like
gone
wrong
for
me
in
the
past
either
I
didn't
realize
I
needed
that,
and
so
I
didn't
include
the
script
tag
and
I
didn't
have
it
or
because
it's
an
inline
script
tag.
Sometimes
you
get
bit
by
like
specific.
Like
course,
rules
or
I
know
you've
got
stuff
in
the
agenda
for
this,
but
like
this
is
a
place
where
things
can
go
wrong.
C
A
A
What
was
that?
Oh?
So
I
was
talking
about
the
javascript
that
resets
their
css.
The
other
thing
to
know
that's
unfortunate
about
marketo.
Well,
I
mean
it
is
what
it
is.
It's
not
necessarily
unfortunate,
but
is,
if
you
look
at
the
how
their
html
is
structured
by
default,
marketo
farm
row,
marketo
field,
descriptor,
marketo
field,
wrap
label,
it's
highly
nested.
The
classes
are
automatically
generated,
so
you
can't
necessarily
style
on
them
very
easily.
A
There
aren't
necessarily
class
names.
So
let's
say
I
wanted
to
style
on
the
work
email
address
field.
How
would
I
do
that?
I
want
to
style
on
the
thing.
That's
surrounding
it.
Let's
say
because
I
want
to
include
the
label.
There
isn't
a
class
right,
it's
just
marketo
field
descriptor
and
with
css
you
can't
travel
up
the
dom.
You
can
only
style
on
an
object
specifically.
A
I
think
somewhere,
but
basically
it
takes
some
of
the
html
values
that
aren't
class
names,
travels
up
the
dom
and
applies
it
to
a
higher
level
object
that
then
you
can
target
with
styles.
So,
let's
see
I
said,
label
so
blah
blah
blah
label
get
the
well
anyway.
I
don't
need
to
go
into
the
details.
You
can
read
the
code.
I
don't
remember
if
it's
working
or
not
at
this
point
because
things
change,
but
it's
good
to
know
that
there
are
gotchas
about
styling
it
basically
yeah.
A
Exactly
yeah,
sometimes
it's
easier
to
do
javascript
to
help
the
css
than
it
is
to
just
try
and
figure
out.
How
do
I
make
this
look
like
it's
supposed
to,
but
yeah
cool,
so
that's,
basically
the
how
we
get
from
html
to
a
style
form.
There
are
some
default
styles
coming
from
bootstrap
that
govern
forms,
and
it's
very
generic
stuff.
High
level.
You
know
display
inline
block
for
a
label.
That
kind
of
thing
then
there's
styles
for
forms
that
we've
inherited
over
time.
So
you
know
spaghetti
code
over
the
past.
A
You
know
six
years
or
whatever
that
I
came
here
and
it
was
already
there
it's
good
to
know
that
these
things
are
there
because
I'm
sure
moving
forward
as
we
adapt
our
slippers
design
system
and
try
and
make
these
forms
pretty.
You
got
to
know
where
the
styles
are
coming
from
that
we
can,
you
know,
detach
and
modify,
and
that
kind
of
thing
sometimes
there
over
the
years
I've
been
asked
to
create.
A
You
know
various
snowflake
kind
of
styles,
so
you
know
a
compact
version
of
the
form
that
maybe
doesn't
have
the
labels
on
it
or
or
maybe
you
know,
tries
to
do
the
the
label
gets
inserted
inside
of
the
text
input
rather
than
above
it.
That
kind
of
thing.
So
there's
one,
that's
called
form
compact,
there's
one
that's
called
form
to
resource
honestly.
I
don't
remember
what's
in
there
at
this
point,
just
because
I
think
it's
related
to
some
of
the
stuff
I
was.
A
It
looks
like
basically
making
sure
that
things
stretch
full
width
and
and
other
stuff
like
that
and
that's
got
button
shadows
and
then
there's
one.
That's
called
form
two
column
which
we
don't
really
use,
but
basically
you
can
imagine
if
this
form
takes
up
the
whole
page
with
you
know
it's
a
one
column
thing
and
then,
on
the
left
hand,
side
of
the
form
is
maybe
first
name
and
then
the
right
hand.
A
A
I
think
we
used
it
maybe
once
or
twice
and
it
didn't
last
because
of
if
we
go
back
and
look
at
the
you
know
page,
I
was
just
looking
at
actually
I'll
go
click
on
an
earlier
one.
So
if
we,
you
know,
look
at
this
example,
landing
pages
marketing
programs,
a
lot
of
the
times
loves
this
format
where
the
form
is
on
the
right.
In
a
second
column,
they
don't
want
the
form
to
take
up
the
full
width
and
have
the
story
either
above
or
below.
A
They
want
them
to
be
kind
of
you're
looking
at
both
at
the
same
time.
So
that's
kind
of
why
that
particular
format
isn't
tending
to
the
use
so
scrolling
down
to
the
javascript
code
and
where
it's
coming
from
you
know
I
already
mentioned
earlier
the
form
to
resource
file
and
just
for
some
background
on
the
naming,
I
was
a
little
new
at
gitlab
there.
But
if
you
go
to
the
resources
tab
on
our
website,
a
lot
of
these
have
attached
marketo
forms.
A
So
that's
kind
of
where
I
was
like
you
know:
here's
a
forum,
you
get
a
resource,
that's
that's
why
that
name
is
there
and
as
we're
looking
at
this,
I
just
want
to
mention
again.
You
know
we
have
callbacks
in
there
for
other
tools
like
demandbase
and
google
analytics
and
such
so
it's
important
to
know
those
are
there.
A
A
Some
of
the
variables
had
to
be
changed
because
the
way
marketo
works
it
attaches
to
an
id,
and
so,
if
you
have
more
than
one
form
on
the
page,
the
auto-generated,
ids
and
class
names
and
whatever
might
not
be
unique
enough,
so
you
put
two
forms
on
the
page:
you're
filling
out
the
second
one:
it's
not
working!
Why
not
it's,
because
the
events
were
attached
to
the
first
one,
only
and
so
there's
a
second
version
of
the
javascript,
and
this
is
copied
from.
A
I
don't
remember
where
exactly
I
want
to
say
it's
a
stack
overflow
post.
I
wish
I
had
oh
wait
here
we
go
adapted
from
and
basically,
if
you
go
visit,
this
you'll
see
that
you
know
this
person
said
this
is
how
you
get
multiple
marketo
forms
on
a
page.
Some
smart
person
many
years
ago
figured
this
out
for
the
rest
of
the
world
and
we're
ever
forever
thankful.
A
A
You
know
it's
it's
something
simple
like
this
seemingly
simple
right,
but
now
you
have
to
go
back
and
make
sure
every
form
on
the
site
works
such
that
there
can
be
two
marketo
forms
on
the
same
page
and
a
lot
of
these
things
that
I'm
mentioning
as
gotchas.
There
may
be
better
ways
to
do
it.
You
know,
for
example,
long
term.
A
We
would
like
to
use
their
api
to
submit
forms
certain
forms.
It's
a
brand
new
feature
that
they
just
implemented
and
I
think
it
might
still
be
in
beta.
It
might
not.
I
don't
remember
where
we
don't
have
to
use
this
javascript
based
workaround
to
go
fetch
it
from
them
to
put
it
on
our
page
right
like
we
can
use
their
api
directly.
A
C
I
think
also,
if
I
can
add
to
that,
because
it's
like
this
was
my
life
for
so
long,
and
I
just
like
see
the
all
the
similarities
from
my
last
job,
where
we
had
these
same,
like
wants
on
the
dev
team.
One
of
one
of
the
like,
like
marketo,
is
cool
because
it
like
really
provides
a
lot
of
like
out-of-the-box
utility
for
people
who
are
like
not
developers
to
move
quickly
on
form.
C
So
many
like
implications
and
considerations
about
it
that
it's
not
just
like
we're,
maintaining
some
library
and
like
what,
if
we
could
clean
up
our
library,
it's
like
yeah,
it's
all
the
good
things
about
marketo,
make
it
just
so
much
more
cross-functional
and
a
little
more
challenging
to
coordinate
between
teams
who
are
not
always
in
direct
communication.
So
I
just
like,
like
I
like.
C
A
All
very
good
points,
especially
about
the
velocity
and,
and
you
know
how
it
impacts.
Different
teams.
Marketo
is
great
at
what
it
does
when
you
don't,
when
you
want
it
to
do
something
that
it's
not
meant
to
do
as
with
all
tools,
it
becomes
harder.
So
a
couple
of
examples,
so
I
I
mentioned
earlier,
the
you
know
shared
javascript
code
that
a
lot
of
forums
do
use
on
our
website.
A
You
know
that
sorry,
that's
the
wrong
file
anyway,
form
to
resource
this
one.
However,
not
all
forms
on
our
website
use
it.
Why
is
that?
Well,
because
over
time
you
know,
there's
only
so
many
hours
in
a
day,
and
so
we
got
a
request
to
say,
update
the
resources
pages,
and
so
we
applied
the
javascript
there.
And
then
we
got
a
request
to
update
the
webcast
pages
and
we
applied
it
there
so
thing
there
are
still
several
pages
that
don't
use
that
because
we
never
got
the
request
to
update
them.
A
It
wasn't
in
our
sprint
or
whatever
to
update
them.
So
the
sales
page,
for
example,
has
some
extra
requirements,
so
it
doesn't
use
this
shared
javascript
code.
You
know
it's
just
here
on
the
page:
it
does
some
other
things
like
you
know.
Google
analytics
function
here
to
get
the
client
id
and
attract
and
tracking
id
and
report
those
back.
So
there
are
a
lot
of
pages
on
the
website
that
you
might
get
a
request
say:
hey.
Can
we
update
this
marketo
form
sure?
A
Oh
oops,
it's
not
using
the
shared
javascript.
So
now
I
got
to
go
edit
that
page
differently
from
all
the
others,
and
it
may
be
missing
functionality
that
is
in
this
other
javascript.
So
you
there,
the
answer
may
be:
hey,
I'm
going
to
apply
the
shared
javascript
or
the
answer
may
be
hey.
We
can't
do
x
unless
I
copy
paste
it
from
the
shared
javascript.
So
just
be
aware
that
there
are
snowflakes
out
there
on
the
about
site
that
use
different
code
paths.
A
Yeah
so
we've
already
gone
over,
you
know
kind
of
some
of
the
gotchas
when
programming
for
marketo
forms
in
our
about
website
repository,
one
of
them
is
localhost
right.
I'm
working
on
you
know
a
page.
Let's
say
that
I
locally
and
I'm
putting
a
marketo
form
on
it.
Yay
the
form
pops
up-
and
you
know
it's
it's
there.
A
Obviously
something's
working
right,
but
when
I
go
to
submit
the
form
because
of
you
know,
localhost
javascript
concerns,
and
you
know
cross-origin
resources
and
stuff
like
that,
where
it's
not
within
the
same
domain
as
gitlab.com,
you
know
you
go
to
submit
the
you,
can
fetch
the
form.
But
when
you
go
to
submit
the
form-
and
you
say
you
know-
you
filled
it
out
properly-
you
click
it
just
gets
stuck
on.
Please
wait
again
because
we're
the
marketo
system,
when
someone
clicks
that
button
is
expecting
to
send
it
somewhere.
A
A
A
A
Submit
the
thing
and
get
the
success
state
as
well
all
that's
happening
after
you
click.
You
know
I
can
you
know
you
fill
out
the
form
you
submit
it
goes
through
at
this
point.
What's
happening
is
there
is
a
display,
none
applied
to
certain
parts
of
the
page
and
display
block
applied
to
other
parts
of
the
page,
so
it's
a
show
hide
basically
in
javascript.
So
this
was
always
there
you,
you
click
the
form
it
submits
and
then
javascript
triggers
a
different
part
of
the
page.
A
To
show
up
it's
not
like
we're
saying,
hey
marketo.
Can
you
give
us
the
success
portion
of
the
page
right
like
the
success
portion
of
the
page?
Is
there
so
we
write
the
html
on
the
about
website.
We
write
the
styles
on
the
about
website.
It's
just
hidden
with
the
display,
none
until
it's
good
to
go,
which
is
done
via
callback
event
from
the
marketo
script
and
yeah.
So
that's
kind
of
it
for
now
for
the
recording
portion
of
this.
E
I
just
had
a
quick
question
sure
say:
like
a
request
comes
our
way
and
it
lands
on
my
lap.
I've
never
like
played
with
it
before
so.
Is
there
like
a
good
example
of
something?
That's
like
a
sim
like,
especially
because
we
have
like
snowflakes?
Is
there
like
a
place
where
I
should
be
looking
to
like
start
my
like
journey
of
trying
to
understand
it,
because
I
imagine
then
like
trying
to
jump
into
like
the
not
snowflakes
like
right
away
might
like
just
be
like
what
is
going
on.
You
know.
A
Yeah,
so
that
is
a
good
question.
I'll
I'll
have
to
ponder
that
for
a
minute
before
I
can.
You
know,
give
kind
of
a
good
example,
because
I
don't
want
to
give
you
the
wrong
example
of
a
good
example
and
then
you're
kind
of
like
what
did
I
do.
All
I
can
say
is
that
something
that
does
use
that
shared
resource
a
lot
of
the
gotchas
are
kind
of
already
figured
out.
A
Obviously
it's
more
daunting,
because
you
have
these
variables
that
you
don't
know
about,
but
because
it's
already
built
you
know
you
can
basically
pass
in
an
id
put
the
form
script
tag
on
the
page
and
it
should
work
and
you
know
you'll,
so
I
can
recommend
the
resources
pages.
As
a
you
know,
good
example
to
work
from,
but
at
the
same
time
I
don't
some
of
these
are
actually
in
the
the
marketo
system
itself.
It
looks
like
most
of
them
are
these
days.
A
I
guess
the
developer
survey
might
be
a
good
one
to
look
at.
It
uses
the
shared
code,
but
it's
not
like
super
complex
as
to
what
it's
trying
to
do,
and
it
has
examples
of
like
scroll
to
that
point
on
the
page
and
stuff
like
that.
It's
pretty
obvious
when
you're
working
on
it,
but
to
find
one
without
all
the
shared
code.
You
know
that's
a
snowflake
or
whatever,
like
the
sales
page.
A
Yes,
we
are,
and
so
that
is
loaded,
I
believe,
via
google
tag
manager.
Let
me
just
check
real
quick,
but
that's
part
of
why
cookies
are
required
to
use
marketo
is
because
munchkin
is
on
the
page.
It
needs
to
set
a
cookie
marco
marketo
says
this
form
is
going
to
use
munchkin,
and
so
the
two
are
kind
of
intertwined.
There's
an
issue
out
there
that
we
want
to
explore
removing
munchkin
from
certain
pages
so
that
we
don't
have
that
cookie
requirement.
A
Yep
yep,
it
looks
like
it's
loaded
in
our
script.
Handle
include
that
you
know
runs
at
the
end
of
every
page.
That
says:
hey
use,
jquery
and
bootstrap,
and
you
know
our
scripts
file
and
then
apply
some
marketo
munchkin
stuff.
So
I
don't
think
it
is
loaded
via
tag
manager.
I
may
have
misspoken
earlier,
but
yeah.
So
so
that's
that's
marketo.
In
a
nutshell,.
D
A
You
know
this
one
has
a
demand
base.
Not
all
of
them
have
demand
based,
not
all
of
them
being
demand-based.
Some
other
examples.
If
you're
looking
at
the
I
mentioned
earlier,
being
able
to
apply
class
names
to
the
form
elements,
that's
in
the
shared
javascript,
but
it's
not
going
to
be
in
the
snowflakes,
because
that's
something
we
added
extra.
A
A
So
this
is
a
callback
function
where
on
success
I
say,
run
this
function
and
so
then
you
can
go
back
and
you
know
have
the
confirm,
form
hidden
and
the
or
you
know
become
visible.
And
then
you
hide
the
marketo
form,
and
you
say
you
know
if
this
is
a
webcast.
Video
container
show
it
scroll
to
the
top.
So
it's
these
kind
of
shared
utilities
that
are
not
in
these
snowflake
events.
A
A
Oh
and
another
thing
about
demand
based
right
is
there's,
basically,
it
says,
load
demand
base,
but
it
doesn't
have
another
part
of
it
which
says
once
you've
filled
out
the
email
address,
go
ahead
and
append
that
to
the
url
and
that's
needed
by
certain
marketing
programs
that
you
know,
add
the
parameter
to
the
url,
and
it's
only
done
on
pages
with
the
shared
code.
I
believe-
and
it's
not
because
we
don't
want
to
do
it
everywhere,
it's
just
because
there's
snowflakes
and
they
don't
have
that
shared
javascript.
A
A
Any
other
questions
all
good
for
now
you
know.
Obviously
this
is
a
high
level
overview.
Y'all
haven't
worked
with
it
yet
so
I'm
sure
once
you
run
into
it,
you'll
have
questions
but
yeah
cool.
So
thanks
for
you
know,
participating
everyone.
It's
great
to
share
this
knowledge
and
we'll
have
this
recording
up
soon
later.