►
From YouTube: Align on SSOT for INQ & MQL tracking
Description
Meeting between Marketing Strategy & Performance and Sales Analytics to align on SSOT for INQ & MQL tracking.
A
Report
to
the
cloud
all
right,
so
I
organized
this
meeting
just
because
I
feel
like
we're
all
filling
mql
and
inquiry
numbers
and
it'll
be
really
good
to
align,
especially
since
you
know
we
are
we're
reporting
to
the
wider
arc
to
make
sure
we
are
all
pulling
from
the
same
source,
at
least
so,
where
possible,
or
get
as
close
to
as
possible
to
doing
that,
because
just
so
we
don't
create
confusion
or
anything
like
that,
because
a
lot
at
least
for
campaigns
team
we're
personally
referencing
a
lot
of
these
numbers
when
we
talk
to
sales
for
our
like
goaling
targeting
and
all
that,
so
if
we're
not
aligned
with
y'all
it'll,
be
we'll
probably
be
moving
to
the
wrong
direction
like
we
won't
even
know
so
yeah.
A
So
I
wanted
to
align
on
that.
I
did
put
something
on
the
agenda.
Just
clarifying
with
christine
like
is
this.
Is
that
the
source
I
mean
yeah?
Is
that
the
sslt
for
inquiries?
I'm?
I
see
you
at
mql,
actual
sport
for
toppo,
and
I
I
see
you
answered
it
christine
yeah.
B
And
agnes
sorry,
I
don't
know
like
that:
shouldn't
be
the
source
of
truth.
For
for
anything,
it
was
kind
of
a
one-off
analysis
of
like
we
had
a
q4
inquiry
drop,
so
we
were
trying.
It
was
like
an
extract
to
try
to
debug
that
for
a
cadence
call
and
our
source
of
truth
for
first
order,
inquiries
and
mql
should
be
the
td
weekly
marketing
dash.
So
that's
kind
of
what
we're
we're
working
off
of
in
case.
That's
helpful,
yeah
yeah.
A
That's
very
very
helpful,
just
because
I
know
don
quran
versus
it
in
his
his
slides
that
was
kind
of
like
building
off
the
marketing
plan,
which
is
why
I
was
like
okay
where's
christine
getting
these
numbers
just
so
that
I
know
like
okay.
This
is
what
is
referenced
for
planning,
got
it:
okay,
okay,
if
we
go
towards
like
we
should
also
probably
pull
from
that.
So
you
are
pulling
it
from
tv
weekly,
which
is
good
because
that's
also
kind
of
what
I'm
using
to
just
a
drill
down
version.
A
Just
because
I
need
the
second
region
to
pull
my
inquiry.
Mql
numbers.
I
do
see
that
a
bit
of
a
challenge,
but
I
think
it
might
be
because
of
just
the
segment
region.
You
know,
which
I
know
we're
handling
right
now
like.
If
I
once
I
start,
because
when
I
was
looking
at
that
source
and
how
doc
was
building
off
that
for
our
planning,
he
took
like
40
or
something
like
that
from
that
to
assigned
to
amer
enterprise,
and
this
is
specific
to
my
enterprise
and
I
think
it
gets
challenging.
A
Because
then,
that's
when
I
feel
like
there's
a
big
drop
off,
because
our
our
segment
region
fields
are
not,
I
think,
that's
you
know
what
we're
still
working
towards
right
like
getting
that
accurate.
So
that
might
be
why
I'm
seeing
what
way
lower
numbers
than
what
he's
seeing,
just
just
as
an
example,
for
example
like
for
all
of
q4,
I'm
seeing
like
around
500
mqls
for
my
amer
enterprise
region
and
so
like.
A
If
you
take
40,
even
40
of
you,
know
kind
of
like
whatever's
here,
because
I
think
he
uses
that
40
number
to
get
to
the
to
the
to
the
goal
like
40
out
of
what
we
have
would
be
like
more
like
a
thousand
from
your
first
order.
Mqls.
But
again,
I
think
that
might
be
just
because
of
the
segment
region.
B
A
lot
of
those
things
that
were
previously
allocated
to
segments
were
no
longer
allocated
because
they
moved
to
a
queue
function,
and
so
that's
like
the
issue
that
beth
has
been
working
on
just
trying
to
retroactively
like
go
in
and
make
that
change
so
that
we
can
actually
use
the
account
demographic.
B
I
think
we
spoke
on
the
issue
about
this,
but,
like
the
goal
is
to
see
if
we
can
move
to
the
account
demographic
fields,
instead
of
this
kind
of
hacky
user-based
system
that
we've
had
yeah,
that
uses
a
spreadsheet
which
is
like
you
know,
it's
just
not
scalable
or
sustainable.
So
that's
the
end
goal,
but
right
now,
like
I
think,
beth
is
like
mostly
through
fy23.
B
So
if
you're
looking
at
fy
22
numbers,
it's
gonna
look
much
lower
at
this
point
in
time,
because
of
that
like,
if
you
look
at
the
other
charts,
you'll
see,
there's
like
big
buckets
there.
That
haven't
actually
been
backfilled
with
the
change
that
that
beth
is
working
on.
A
B
It
should
be
closer,
but
I
need
to
actually
validate
that.
I
think
she
was
still
working
on
it.
I
don't
know
david
if
you
have
any
thoughts.
Let's
see.
Oh
her
last
update
was
two
weeks
ago.
So
let
me
follow
up
with
her
agnes
and
see
where
she
is
with
that.
Okay,
actually.
A
Yeah
cuz,
I
feel
like
that,
would
be,
I
think,
we're
all
aligned,
at
least
as
a
team
to
say.
Okay,
we're
gonna
use
account
demographics
as
the
region
segment
field,
moving
forward
and
the
td
weekly
marketing
as
the
single
source
of
tourists
for
inquiry.
Sam
mql,
I
feel
good.
You
know,
I
don't
know
if
anyone
else
here
feels
differently
or
if
anyone
else
is
using
a
different
source,
then
maybe
let
us
know
also
so
then
we
we
we
can
make
sure
to
all
kind
of
consider.
B
Right,
I
think
the
only
one,
the
only
other
one
is
that
there's
actually
mql
not
inquiry,
but
mql
numbers
in
the
td
sales
funnel
dashboards.
So
malia-
and
I
talked
about
this
earlier
this
week,
but
that's
actually
like
not
a
first
order.
View
of
mqls
is
just
mqls
and
the
team
is
working
on
trying
to
make
our
first
order
filter
that
robert
built
into
the
td
weekly
dashboard
available
across
so
like
other
dashboards,
can
be
filtered
for
the
same
view
of
first
order.
B
So
I
think
agnes,
that's,
like
the
only
other
one
that
I'm
aware
people
are
actively
like
and
actually
I'm
not
even
sure
how
actively
people
are
using
it.
But
it's
there
and
people
look
at
that
dashboard.
Quite
often,
so
that's
the
only
other
source
and
just
know
that
there's
a
known
discrepancy,
because
that's
not
first
order
and
we're
working
on
getting
those
to
align
when
we
apply
a
first
order
filter
emily.
I
don't
know
if
you
want
to
add
anything
to
that
or
if
that's
a
fair
summary
of
what
we
discussed.
Yeah.
D
B
A
I'm
not
I'm
again
like
I'm,
not
sure
yet
what
the
logic
behind
it
is.
As
long
as
I
feel
like
it's
accurate,
like
reflective
of
or
aligned
with
whatever
is
in
the
tv
weekly
marketing,
then
I
should
be
good,
but.
A
B
C
A
C
A
As
yeah
as
long
as
the
logic
itself
is
similar
outside
first
order,
yeah,
I'm
feeling
pretty
good
that
it.
C
A
C
A
Okay,
great
thank
you
for
clarifying
that
and
then
yeah.
So
I
think
if
we
can
at
least
even
narrow
down
to
those
two
dashboards,
I'm
happy
with
you
know
for
now
to
just
continue
that
down
that
path.
Amelia,
do
you
have
any
other
sources
that
you're
using
or
you
think
that
we
can
all
kind
of
like
align
with
issues
we.
E
Well,
I
don't
use
the
weekly
marketing
dashboards
because
I
don't
have
access
to
them.
Those
are
in
the
safe
intermediate
space
and
I
can't
see
the
sql
that's
used
to
make
those
dashboards,
so
only
marketing
uses
those
and
nobody
else
in
the
rest
of
the
company
uses.
Those
everybody
else
is
using
the
td
sales
funnel
dashboard.
E
E
B
Yeah
and
I
like
the
issue
for
that
under
de3,.
A
Thank
you
yeah,
so,
basically,
emilia
you're,
using
the
sales
funnel
target
versus
actuals
marketing,
is
using
the
td
weekly
marketing
just
to
sum
it
up
dashboards,
but
all
these
dashboards
I
have
similar,
except
for
the
first
order
for
now
right,
like
similar
back
okay,
great
this,
your
dashboard,
I
have
to
look
again
but
like
does
it
also
reference
segment
region
from
account
demographics?
At
this
point?
A
E
It's
using
a
combination
so
on
opportunities
you
have
to
use
the
user
segment
fields
and
then
on
leads.
You
need
to
use
the
account
demographics
fields.
So
all
the
filters
are
combination
filters.
So,
if
you're
on
an
mql
report,
it's
using
account
demographics.
If
you're
on
an
opportunity
report,
it's
using
user
segment.
E
B
For
opportunities
they
have
to
use
the
user
because
of
how
they
credit,
different
teams.
E
Yeah,
do
you
do
you
want
me
to
explain
what
the
differences
just
so
it
makes
makes
it
clear
so
account.
Demographics
fields
are
based
on
account
characteristics,
so
the
account
demographics
segment
is
based
on
the
employee
account
at
the
account
the
account
demographics,
geo
region
and
area
is
based
on
the
address
of
the
account.
So
that's
the
account
side,
and
then
the
user
side
is
all
about
the
salesforce
user
who
worked
on
the
opportunity.
E
So
that's
which
sales
team
is
going
to
get
credit
for
that
deal.
So
you
have
a
mirrored
fields,
because
our
sales
teams
are
also
organized
by
segment
geo
region
area,
but
they're
not
always
the
same,
because
we
sometimes
choose
to
have
a
sales
rep
work
on
an
account
that's
outside
of
their
geographical
territory,
like
we
named
them
certain
accounts
that
may
not
be
in
the
geographical
region
that
they
normally
work
on.
So
if,
for
example,
you
had
an
account
located
in
new
york,
but
we
have
our
southeast
rep
work
on
that
account.
D
E
But
if
we're
talking
about
which
sales
team
gets
credit,
they
don't
care
about
the
user
side
and
that's
why,
on
the
lead
side,
we're
using
account
demographics
on
the
opportunity
side,
we're
using
user
fields,
and
so,
when
you
filter
on
a
dashboard
that
goes
all
the
way
across.
It's
a
combination
filter
where,
if
the
report
is
on
leads,
it
looks
at
account
demographics.
If
the
report's
on
opportunities,
it
looks
at
user.
A
Where
can
I
see,
though,
the
the
leads
for
the
td,
because
I'm
looking
at
the
the
dashboard
that
was
linked
in
the
dock?
It
says
td
current
accounts
that
sales
punish
funnel
target
versus
actual
that's
only
opportunities
right.
A
Gotcha,
but
why
but
I
don't
see
the
account
demographics
filter.
Maybe
is
it
my
view?
You
know
it's.
E
E
B
Yeah-
and
I
think
part
of
the
problem
magnus
is
like-
maybe
you
haven't
seen
some
of
those
presentations
and
so
malia.
I
think
I
might
take
the
one
that
you
did
for
gtm
leadership,
because
okay
reported
and
then
agnes.
I
can
share
it
with
you.
Sorry
I
didn't
share
it
earlier.
Didn't
realize
this
was
was
a
point
of
confusion,
but
that
might
help
clear
up
some
of
those
differences,
because
it's
a
new
thing
for
fy23.
I
know.
E
B
Living
and
breathing
it,
but
I
think
it's
still
we're
still
trickling
the
knowledge
across
the
organization.
E
Yeah,
it's
gonna
take
a
while
the
for
fy
22.
All
we
had
was
the
user
side
fields.
We
didn't
the
account
side.
Fields
didn't
exist
so
for
fy23.
This
whole
combined
view
is
a
new
thing
and
when
we're
talking
about
like
our
current
account
set-
and
we
want
to
think
about
year
over
year,
so
we
need
to
look
at
like
this
year's
values
and
compare
to
last
year
and
last
year.
E
Maybe
we
didn't
have
that
particular
region
or
area,
so
you
have
to
kind
of
use
these
combinations
to
be
able
to
compare
like
okay.
This
year
we
have
this
new
area
or
new
region
called
samia
that
didn't
exist
last
year,
but
we
want
to
know
for
all
the
accounts
that
are
in
samia
now,
how
do
they
perform
last
year?
So
we
can
get
like
a
correct
year
over
year,
so
yeah
there's,
there's
certain
use
cases
where
you
need
kind
of
like
weird
combinations
of
the
two
fields,
but
for
marketing
in
general.
E
You
guys
are
on
the
lead
side
you
care
about
account.
Values
like
where
is
an
account
actually
located
and
the
user
values
are
more
applicable
for
sales
because
they're
over
on
opportunities
and
they
care
about
which
sales
team
is
working
on
it.
A
I
think
the
challenge-
it's
not
a
challenge,
but
I
guess
as
long
as
we're
in
line
on
that.
That's
fine,
because
when
we
do
conversion
rate,
like
as
a
campaign
manager
like
I'm
trying
to
find
out
like
how
do
these
leads
convert
from
you
know
the
segment
region
that
we
generated
to
the
sales
team
like
we
do
full
funnel
reporting
and
that
conversion
rate
no
matter
what
we
should.
We
still
have
to
kind
of,
like,
I
guess,
use
combinations
of
fields.
E
A
Cool,
I
think
really
that's
just
for
me.
Yes,
because
I'm
not
you
know,
living
and
breathing
it
every
day.
So
I'm
sure
that
presentation
will
help,
but
I
will
put
together,
maybe
just
a
general
issue
for
the
data
team
to
like
just
relabeling
it
instead
of
putting
user,
because
I
think
it
really
throws
me
off
when
I
look
at
it,
I
was
like
oh,
it's
a
user
feel
and
then,
when
I
look
at
the
countdown
I'm
like
oh.
D
B
Thanks
for
bringing
that
up
because
I
didn't
realize
it
was
confusing,
so
it
makes
sense
makes
a
lot
of
sense
why
it
would
be
confusing
it's
what
I'm
trying
to
say
and
and
malia
just
the
gtm
meeting
was
pretty
short
and
like
you.
Actually
it
wasn't
you
like
walking
through
it.
So
I
don't
know
if
you
have
like
a
better
recording
than
that
or
if
not
I'll,
just
use
that,
but.
E
Let
me
think
about
it.
I
think
I've
got.
Let's
see.
I
think
I
have
another
presentation.
I
did
for
a
a
field.
Ops
show
and
tell
that
might
be
helpful.
If
I
can
remember
what
it
was
called,
it
was
about,
like
the
account
demographics
fields,
and
it
was
when
we
were
creating
them
and
the
difference
between
the
account
side
and
the
user
side.
All
of
that
stuff
is
in
one
presentation.
Let
me
I'll
find
that
one
and
give
you
the
link
for
that
too.
Yeah.
B
I
I
linked
the
presentation
and
then,
if
there's
a
recording,
yeah
just
make
sure
that's
the
right
presentation.
Really.
I
just
okay
like
that.
We're
not
confusing
people.
C
E
See
they're
all
super
short,
oh
here
it
is
okay,
yeah!
Let
me
let
me
give
you
this
link
too.
It's
not
a
recording,
it's
just
a
presentation,
but
it's
only
a
five
minute
presentation.
So
there's
not
a
lot,
not
a
lot.
You
can
read
it
in
five
minutes,
but
I'm
happy
to
answer
any
questions.
If
you
think
of
anything.
A
Thank
you.
Thank
you
cool.
I
know
jackie
has
the
next
question
so
now
that
we
are
good
with
cyclone
region
and
also
just
general
sslt
for
mqls.
F
So
two
scenarios
where
craig
and
pile
agreed
on
this
too,
we
should
consider
them
first
order
and
still
like
approach
them
was
if
the
ultimate
parent
account
has
less
than
5k
and
spend
or
if
the
customer
churned
over
180
days
ago.
I
think
craig
said
he
wanted
to
take
this
up
with
and
with
some
other
edge
cases.
But
I
was
curious
if
that
has
come
up
and
I'm
really
like.
I
honestly.
This
was
more
of
an
aha
moment
for
me.
E
So
let
me
give
you
some
historical
context
on
this
one
too.
So,
on
the
180-day
rule,
thing
finance
put
in
a
bookings
policy
in
fy
22.
That
said,
if
they
turn
and
come
back
in
greater
than
180
days,
they
should
count
as
new
again
so
all
of
fy22.
That
was
the
policy,
but
no
one
ever
actually
built
that
out
in
salesforce.
E
So
there's
no
code.
That
does
that.
I
do
have
good
news
for
you,
though
I
just
came
from
a
meeting
where
we
were
talking
about
this
exact
thing
and
how
it's
been
more
than
a
year.
We
still
don't
have
the
right
answer.
This
is
a
big
problem.
E
We
have
a
solve
for
that
that
jim
peter
and
the
systems
team
is
working
on
right
now,
so
I
think
the
180
188
thing
will
be
solved
soon
and
what
it's
going
to
do
is
flip
it
back
to
first
order
available
once
it's
past
the
180
day
mark
the
other
thing
with
less
than
5k
spend
I
had
not
heard
of
before.
E
So
I
don't
think
anyone
is
working
on
a
change
for
that.
Have
you
talked
about
that
one
with
the
systems
team.
F
E
There's
other
inaccuracies
with
the
first
order
available
field
like
it
doesn't
fully
work
beyond
the
edge
cases
that
you
know
you
might
be
thinking
of
now.
There's
other
problems
with
it
like
it.
It
just
doesn't
work
all
the
time,
so
there
are
multiple
other
systems,
issues
that
have
also
been
open
for
a
long
time.
I
think
there's
three
issues
out
there
that
I
know
of
about.
First
order
available
one
of
the
problems
they
thought
they
had
solved
with
the
launch
of
order
type
2.3
in
february
and
then
in
march.
E
We
found
more
examples
where
it
was
not
fully
solved
so
they're
still
working
on
that
they're
aware
that
it's
not
working
and
hasn't
been
working
for
a
long
time.
E
F
So
if,
like
a
big
subset
of
people,
that
we're
actually
engaging
with
that
by
all
accounts
and
purposes,
is
a
first
order,
but
based
on
our
logic,
is
in
the
first
order,
they're
not
showing
up
in
the
data,
and
so
we
could
be
making
judgment,
calls
off
of
something
that's
really
more
like
half
baked
and
what
I'm
bringing
up
isn't
so
much
like
bugs
it's
more
like
business
rules,
and
so
it's
not
my
pay
grade,
it's
more
something
that
we've
just
been
bringing
to
light
in
different
different
parts
of
like
defining
the
key
account
list
and
something
I'm
also
thinking
about
is
if
we
truly
only
focused
on
accounts
that
were
first
order,
we
would
be
nurturing
a
lot
less
of
our
database.
F
So
we
know
that
we're
engaging
accounts
that
aren't
first
order
and
even
though
sales
thinks
oh
we're
not
focused
on
first
order.
We
technically
are
because
we're
not
like
pulling
them
back
from
being
in
certain
email
campaigns
like
they're
being
engaged
with
without,
like
us,
putting
budget
against
them
when
it
comes
to
budget
we're
very
specifically,
not
targeting
them.
If
we
were
to
flip
that
switch,
though
I
think
we'd
see
less
people
that
are
engaging
on
growth
opportunities
too
yep
yeah.
F
E
Yeah,
so
it's
a
field
on
the
account
and
it's
based
off
of
order
checks
on
opportunities,
so
the
fix
they're
going
to
do
is
going
to
be
on
opportunities.
E
So
I
expect
what's
going
to
happen
and
I
don't
have
like
the
full
understanding
of
how
everything
works,
but
I
think,
what's
going
to
happen,
is
they'll
put
in
their
fix
on
opportunities
and
then
it's
going
to
flow
all
the
way
through
to
leads,
and
so
things
that
used
to
have
the
box
checked.
It
might
come
unchecked
or
the
other
way
around,
depending
on
how
it
recalculates.
E
So
it
probably
would
be
prudent
for
you
to
know
before
that
happens.
Do
you
want
me
to
tag
you
on
that
issue?.
F
F
that
check
box,
like
those
changes
will
happen
at
a
certain
point
in
time
like
let's
say
next
month,
but
will
it
then,
when
we
pull
data
based
on
november
it'll
bring
that
in
because
now
it's
considered
first
order,
but
based
on
the
logic
for
fy22,
was
con.
It
was
considered
not
first
shorter,
because
the
180.
so.
E
Yeah,
I
think
you
only
so
on
the
account
you
only
have
the
current
value
like
is
a
first
order
available
right
now
right
this
minute
and
it
reruns
every
single
night.
So
for
historical
data
I
mean,
I
think
it's
just
going
to
either
check
or
uncheck
the
box
like
and
I'm
not
exactly
sure
on
leads
what
you
do
about
historical
data,
because
we
don't
stamp
it
anywhere.
E
We
have
an
issue
open
to
start,
stamping
it
at
the
time
of
mql,
but
we
haven't
been
stamping
it
in
the
past.
So
I
don't
know
what
will
happen
with
your
historical
leads.
I
think
the
box
is
just
going
to
either
come
unchecked
or
get
rechecked
and.
F
I
think
that's
a
bunch
of
leads.
I
think
that
also
aligns
to
my
next
question,
which
was
an
account
closes.
Let's
say
it
closes
tomorrow
we
drove
that
mql
last
week
it
was
a
great,
really
fast
sales
cycle,
but
like
when
we
pulled
the
data
in
two
days.
That
opportunity
is
closed.
So
now
it's
no
longer
first
order.
If
you
were
to
be
looking
at
the
dashboard
and
say
first
order
only
that
mql
won't
show
up
anymore,
because
that's.
E
Live
and
always
changing,
that's
why
we
need
to
stamp
it
at
the
time
of
mql.
So
it's
going
to
what's
going
to
happen
is
when
your
lead
or
contact
gets
marked
as
mql
it's
going
to
stamp
whatever
the
value
is
from
the
account
at
that
time.
So
if
it's
first
order
at
that
time,
it'll
be
checked,
as
this
is
a
first
order.
Mql
later
they
buy
something,
but
your
historical
lead
is
still
going
to
be
marked
as
a
first
order.
Mql,
that's
the
part.
We
don't
have
anything
for
right
now,.
F
And
that
is
my
oh
moment,
because
that
makes
sense
moving
forward,
but
if
we
don't
have
that
in
place
right
now,
then
any
mql
is
where
we're
then
closing
an
opportunity
related
to
that
mql.
When
we
check
the
box
for
first
order,
then
the
opportunity
is
closed.
Anything
we're
looking
at
historically
is
going
to
start
taking
out
those
mqls
that
we
generated
that
actually
turn
into
an
sao
on
a
closed
one.
E
Right,
I
think
robert
and
david
have
logic
on
that
td
weekly
dashboard
that
deals
with
that.
I'm
pretty
sure
david.
You
can
correct
me
if
I'm
wrong,
but
I
think
that's
what
their
code
is
doing
is
looking
to
see.
Was
it
a
first
order
at
the
time
of
mql,
not
just
copying?
What's
on
the
account
right
now,.
A
Okay,
now
I
know
if
the
stamping
is
going
to
be
another
account.
Demographics
field
I
felt
like
no
internet
movie,
is
different.
E
Well,
yeah!
Well,
actually.
Originally
that
was
the
plan.
We
did
have
an
account
demographics
field
that
was
called
account.
Demographics
first
order
available.
They
just
didn't
finish
it
in
time,
and
so
they
got
rid
of
it
because
they
were
trying
to
launch
the
account
demographics.
On
february
1st,
we
could
call
it
that
I
think
the
plan
is
actually
to
have
a
stamped
field.
That's
just
on
lead
and
contact,
so
it's
gonna
be
called
something
I
think
like
first
order.
Mql
true
false
is
my
guess:
at
what
they're
gonna
build?
A
E
A
E
Yeah
robert
sent
you
here
what
perfect
timing
for
you
to
pop
up,
because
I
have
one
more
question
about
this.
First
order
available:
stamping
for
mqls,
let
me
let
me
actually
go
find
that
issue
and
open
it.
Real,
quick.
E
The
one
question
I
have
that
we
didn't
fully
answer,
and
this
is
because
I
don't
know
that
well
how
mqls
work
here
at
gitlab.
Do
you
guys
have
can
something
become
an
mql
more
than
once
like?
Let's
say
they
have
whatever
behavior
they
meet
the
threshold
they're
in
mql
now
and
then
it
happens
again
later.
D
E
Got
it
okay?
So
when
we're
talking
about
stamping
first
order
available,
I
think
do
we
care
about
at
both
mql
times,
like
the
fir
the
first
one
and
the
current
one,
or
do
we
only
care
about
whether
it
was
first
word
available
at
the
very
first
time
it
became
an
infuel,
I'm
wondering
do
we
need
one
field
or
two
stamp
fields.
D
B
E
Cool
I'm
good
with
that
we
can
make
two
and
then
the
other
thing.
I
wanted
to
just
confirm
with
you.
You
said
you're
using
a
combination
of
mql
date
and
mql
date
time
in
furge.
E
The
stamping
would
be
easier
if
it
was
one
field
that
they
have
to
look
for
a
change
in
is
that,
can
I
ask
them
to
make
a
combined
one
or
is
there
some
reason
we
don't
have
a
combined
one?
Now
I.
E
Values,
perfect,
yeah!
That's
that's
exactly
what
I
was
thinking
because
then
they
they
have
one
field
and
they're
looking
to
see
when
it
goes
from
blank
to
populated.
At
that
time
you
stamp,
I
think,
that's
what
we
need
to
make
it
work.
A
E
E
A
Gotcha,
that's
awesome,
yeah,
so
looking
forward
to
to
just
following
that
issue
and
knowing
timeline,
so
I
I
think
we
can
get
more
accurate
reporting
for
ourselves
as
well.
So
this
has
been
super
helpful
for
me.
I
don't
know
if
anyone
else
have
anything
to
discuss.
B
No
agnes,
thanks
for
raising
these
things
like
it's,
it's
important
that
we're
all
aligned
and
I
think,
that's
maybe
a
gap
where,
at
least
personally,
I
wasn't
aware
that
you
were
doing
so
much
on
the
reporting
side,
and
I
know
that
you
are
doing
a
lot.
So
I
think,
in
terms
of
like
just
generally
communicating
some
of
the
things
like
the
the
presentation
that
malia
did
like
moving
forward
I'll,
make
sure
that
you're
incorporated
on
that-
and
I
would
ask
like
david
and
robert
to
also
make
sure
help.
A
E
E
So
I
think
what
she's
doing
is
using
zoom
info
to
build
the
same
kind
of
logic
on
the
lead,
so
that
it
always
gets
filled
in
whether
there's
a
matching
account
or
not,
which
is
good,
because
I
think
that
will
plug
a
lot
of
holes
in
your
reporting
on
the
lead
side.
Yeah.
E
A
Yeah,
so
that's
that
whole,
but
at
least
you
know,
because
I
think
we
have
in
the
past,
we
had
like
we're
debating
whether
we
want
to
use
our
fields
or
we
want
that.
You
know
for
the
leads
right
or
the
account
demographics,
and
then
the
user
feels
we
realize
it
was
so
manual
because,
like
if
everyone
is
moving
and
everything
and
there's
lead
routing
problems
and
whatever
it
becomes
even
more
challenging
to
nail
down
like
how
many
mqls
is
for
a
segment
region.
A
E
No,
it's
okay,
that's
a
solvable,
hole
and
yeah
the
account.
Demographics
fields
were
kind
of
built
for
this
reason,
so
that
we
could
have
standardized
reporting
across
all
of
the
objects
like
the
user
fields
were
built
by
sales,
just
on
opportunities
for
what
sales
needs.
The
account
demographics
are
on
leads
contacts
and
accounts,
so
all
the
way
across.
So
we
can
all
kind
of
line
up
so
yeah.
I
think
it'll
work
once
we
get
once
we
get.
E
A
That'll
be
they'll
be
much
better
for
the
quality.
I
think
the
only
other
concern
I
have
is,
if
somehow
we
can't
match
it
with
a
zoom
info
christine,
like
you
know,
and
maybe
you
know,
this
is
something
that
can
help
answer,
but
just
because
I
know
we
have
some
leads.
That
just
gives
us
gmail,
for
example,
in
the
past,
and.
E
E
One
too,
which
I
will
link,
but
one
of
the
things
we're
looking
at,
is
well
we're
looking
at
a
few
things
data
normalization,
so
that
is
about
cleaning
up
the
data
we
have
on
our
salesforce
account
records
now
so,
where
we've
got
junk
in
there
or
you
know,
like
zip
codes
that
don't
have
the
right
number
of
digits
or
you
know
something
is
misspelled
as
dot
con
instead
of
dot
com
and
all
of
those
things
affect
the
data
enrichment
tools
and
prevent
us
from
getting
good
data
so
step,
one
step,
two
we're
looking
at
plugging
holes
in
our
data
enrichment.
E
So
one
one
aspect
of
that
is
what
you
just
talked
about
with
free
email
addresses
so
gmail
yahoo.
All
of
those
things
that
aren't
company
email
addresses
you're
not
going
to
get
good
data
from
a
tool
like
zoom
info
with,
so
we're
looking
at
potentially
some
other
data
providers
that
can
help
plug
those
holes
and
also
looking
at
separating
out
our
free
emails
from
our
corporate
emails,
so
that,
when
we're
looking
at
how
our
enrichment
tools
perform,
we
should
have
really
good,
like
close
to
100.
E
Match
rates
on
corporate
email
addresses
right
and
then
the
gmail's
yeah
there's
still
going
to
be
some
holes
there.
We
know
that,
but
we
want
to
be
able
to
optimize
it
like
with
them
separate
so
on.
The
corporate
side.
Zoom
info
is
currently
our
single
source
of
data,
but
there
are
still
holes
right,
like
there
are
companies
in
like
emea
and
apac
and
japan,
where
zoom
info
in
particular
is
kind
of
north
america
specific
and
doesn't
give
great
data.
So
we're
talking
to
a
company
now
called
open
price.
E
That
is
all
about
this
kind
of
data,
stuff
and
they've
got
connections
with
a
bunch
of
different
vendors.
So
through
them
you
can
kind
of
make
like
a
waterfall.
So,
like
you
check
zoom
in
for
first,
if
they
don't
have
it,
you
go
check
them
dmb.
If
they
don't
have
you
go
check
somewhere
else
to
try
to
optimize
and
make
sure
we
fill
in
as
many
holes
as
we
can.
So
that's
our
our
data
enrichment
step.
E
That's
going
to
take
a
little
bit
of
time,
but
we're
working
on
that
and
then
they
also
have
specific
providers
for
the
free
email
side,
so
really
yeah.
So
we're
working
on
all
of
that
stuff.
It's
just
going
to
take
a
little
bit
of
time
right
now,
we're
in
the
procurement
process
with
open
price
this
that
we've
selected
them
as
a
vendor,
I'm
hoping
that
we
can
buy
it
soon.
E
A
A
E
We
have
a
plan,
it's
just
taking
a
little
bit
of
time
to
get
there
but
kind
of,
like
the
account
demographics.
I
think
that
took
us
like
a
year
to
build
and
you
know
to
get
get
going
with
so
data
infrastructure.
We
we're
we're
working
on
it.
That's.
E
Meetings
too,
with
open
price
and
rob
from
marketing
ops.
B
E
A
A
You
know
we
really
can,
because
we
do
look
at
these
data
so
much
right
like
the
segment
region,
especially
first
order
to
really
optimize
our
like
paid
ad
spend
and
it
you
know
it's
it's
it's
been
so
challenging
like
just
to
have
say,
like
thirty
percent
of
our
farm
fails,
not
have
anything
you
know
like
other
or
like
gmail,
and
it's
also,
but
it's
not
like,
we
can
prevent
people
from
filling
in
I
mean
we
can,
but
then
that
might
reduce
our
conversion
rate.
E
E
E
I'll
put
that
on
the
list,
I
had
kind
of
like
a
list
of
fields
that
we
really
care
about,
and
it's
all
the
stuff
that
we're
using
now
in
our
reporting,
but
I
can
add
job
titles
to
that
too.
E
So
this
is
one
that
I
bought
last
year
and
it's
what
we're
using
on
the
sales
side
to
calculate
lam.
So
it
looks
at
linkedin
resumes
using
a
persona
for
software
developer
that
we
built
inside
their
tool
to
try
to
get
us
developer
accounts
for
each
company,
and
then
we
use
that
to
calculate
okay.
We've
sold
this
many
licenses,
but
they
have
this
many
developers.
So
we
have
this
much
room
for
growth
and
that's
the
lamb.
E
Anyway.
You
can
build
personas
in
that
tool,
but
it's
based
on
linkedin
resumes
so
the
job
titles
there
are
not
normalized,
so
we
tried
it
with
job
titles.
It
didn't
work
great
and
then
we
started
doing
this
kind
of
job
function,
thing
where
linkedin
has
sort
of
tried
to
collect
the
resumes
of
a
particular
function
and
that
seemed
to
work
better
for
software
developer
numbers.
E
You
could
try
that
that
might
be
a
possible
thing
you
could
try.
I
think
we
can
build
out
six
personas
in
that
tool
and
right
now
we're
only
using
one.
E
E
Yeah,
that's
what
we're
doing
for
developer
accounts,
there's
also
some
other
stuff
in
there.
That
I
think,
is
really
cool
for
marketing.
I
don't
think
anybody
from
marketing
is
using
this
tool,
but
we
have
had
it
for
almost
a
year,
we're
just
about
to
renew
it,
and
I
think
it
would
be
really
cool
for
you
guys
to
use,
because
I
know
we
spent
a
lot
of
money
on
linkedin
advertising.
E
So
if
we
could
kind
of
like
line
up
we're
advertising
to
the
hi
lamb
customers,
highland
based
on
developer,
accounts
we're
getting
from
linkedin.
I
think
that
would
you
know,
help
us
all
like
pull
in
the
same
direction.
E
Yeah,
I
can
give
you
access
I'll.
Just
I'll
just
send
you
it's
gonna
send
you.
I
think
it
sends
like
a
like
an
email
and
when
you
log
in
it
wants
your
personal
linkedin
login.
E
It
doesn't
have
like
a
get
lab
company
one,
but
I'll
just
add
you
and
you
can
play
around
with
it.
The
only
thing
is
that
it
charges
by
credits,
and
so
what
you
want
to
do
is
look
at
it.
E
First
inside
the
tool
before
you
try
moving
anything
to
salesforce
and
you'll
probably
need
some
help
when
you
get
to
that
point,
but
you
can
go
in
there
in
the
tool
and
play
around
with
the
personas
and
do
the
research
and
see
if
it
works
for
you
and
it'll
match
against
the
salesforce
accounts
and
everything
right
there
inside
the
tool.
It
just
doesn't
cost
anything
until
you
either
download
it
or
export
it
to
salesforce.
A
I
might
yeah,
if
you
can
give
me
access
I'll,
take
a
look.
I
might
set
up
a
separate
call
with
you
just
to
get
a
bit
more
familiar
on
the
you
know
how
you're
using
it
yeah
I've
heard
about
it,
but
I
never
personally
like
play
with
it.
So
when
we
cross
that
bridge
you
know,
then
I
don't.
I
just
don't
want
to
like
waste
any
credits
or
anything
like
that.
E
Yeah
yeah
I'll,
send
you
a
license
and
then
yeah
we
can
meet
and
play
around
with
it
together.
Yeah
I'll
set
up
a
separate.
E
B
Okay,
helpful
and
david
robert
I
wanted
to
check.
Is
that
because
I'm
not
aware
of
our
team
using
any
of
linkedin
sales
insights
like
would
it
be
helpful
for
you
all
to
especially,
I
guess
david
on,
like
the
persona
stuff
that
craig
and
dave
were
asking
for
like?
B
C
I
agree
yeah
it
that
definitely
sounds
like
it,
because
you're
solving
trying
to
solve
the
same
problem.
E
Yeah
yeah,
so
there
they're
like
caveats
with
it:
yeah
anyway,
we
can,
we
can
meet
and
I'll
give
you
sort
of
a
brief
overview
of
how
we're
using
it
in
sales,
but
I
think
you
guys
could
potentially
use
it
too.