►
From YouTube: Robert Kohnke and Taylor Murphy discuss Pipe to Spend
Description
A
B
That
cost
is
not
calculated
in
the
campaign
cost
and
NetSuite
as
far
as
I
understand.
So
that's
something
that
we'll
have
to
add
on
you
know
iteration
two
or
screen,
but
for
now,
when
he
wants
the
baseline
to
be,
is
just
NetSuite
actual
cost
compared
to
pipeline
generated
from
Salesforce.
Is
there
a
time
delay
on
the
pipeline
generation?
We
haven't.
We
didn't
get
that
detailed,
but
I.
A
Okay,
cool,
so
I've
got
the
this
is
the
the
project
and
and
Rico
and
everything
open
here.
So
in
DB
T
we
have
the
the
pipe
to
spend
consolidated
model
which
pulls
in
from
a
bunch
of
different
things.
So
all
right,
so
he
already
said:
headcount
is
going
away.
This
just
for
the
record,
was
previously
a
Google.
A
A
We
have
the
whole
fullest
thing
somewhere,
the
headcount
number
and
then
the
salary
per
month.
Basically
so
not
gonna
use
that,
presumably
this
one
you
would
still
want
to
use.
So
this
is
the
transformed,
visible
attribution,
touchpoint
transformed
model
which
yeah
this
does
have
all
of
the
so
that
this
this
case
wine
statement
here
is
really
controlling
like
where
the
touch
points
coming
from
and
to
watch
PI
be
it
goes
into,
and
so
you
know,
you'd
have
kind
of
free
rein
on
that.
A
So
that's
I
think
that's
actually
pretty
straightforward
yeah.
So
this
is
where
the
work
will
need
to
be.
Redone
is
is
pulling
in
the
data
from
NetSuite,
so
we
have
this
general
ledger
this.
What
this
is
referencing
is,
it
is
out
of
date
and
we're
kind
of
in
progress.
So
you
see
with
NetSuite
in
the
NetSuite
stitch
NetSuite
stitch
is
the
new
primary
source
and
we're
gonna
deprecated
NetSuite
and
renamed
NetSuite
stitch
to
NetSuite.
A
So
you
like
what,
if
you're
working
on
this,
go
ahead
and
pull
from
the
NetSuite
stitch
file,
and
we
have
our
NetSuite
stitch,
all
entries,
which
is
equivalent
to
this
general
ledger.
That's
what
she
would.
Let
me
turn
off
notifications,
so
you
would
use
this
and
then,
as
part
of
our
refactor,
we
can
just
go
in
and
kind
of
switch
the
names,
but
none
of
the
functionality
will
change.
A
What
we
were
doing
previously
is
basically
for
demand,
advertising
and
then
field
events.
I
was
all
I
was
doing,
is
just
filtering
by
the
account
code
number
and
basically
assigning
each
expense
to
one
of
these
pipes,
so
whether
it's
AdWords
terminus
or
whatever
I'm
guessing
that's
gonna,
I,
don't
know
in
NetSuite
how
the
campaigns
spend
is
going
to
be
tied
to
a
specific
account
code
or
anything
in
NetSuite,
but
that
the
high
level
was
like
60
120
is
like
demand.
Advertising
61
30
is
field
events,
and
so
maybe
that's
the
difference
and
then
yeah.
A
All
we
did
is
just
kind
of
joined
it
all
together.
This
joint
started
from
the
headcount,
so
you'd
have
to
switch
that
up,
and
then
we
took
the
other
key
point
here.
We
took
oh
yeah
the
joins
and
when
we
join
in
the
spend
we
do
it
for
three
months
after
the
fact.
So
it's
you
know,
the
spend
in
March
applies
to
the
pipe
in
June,
okay
yeah,
which
initially
was
like
the
same
I
think
the
same
month
or
one
month,
but
LJ
had
argued
to
get
it
switched
to
three
months.
A
Snowflake
or
periscope,
just
cuz
I
felt
it
was
easier.
The
downside
of
this
and
I
think
where
people
cuz
like
as
soon
as
you
see
like
okay,
well,
here's
the
pipe
to
spend
like
alright.
Let
me
dive
in
and
see
the
campaigns.
I
think
the
way
to
do
that
is
to
still
build
this
base
kind
of
simplified
view
and
then
switch
to
you
do
like
drill
downs
and
then
have
like
pass
in
the
the
parameters
from
the
drill
down
into
a
new
viewer
model.
A
B
B
A
A
This
should
have
it.
This
should
just
be
kind
of
like
the
general
ledger
for
the
company,
so
you
should
be
able
to
go
through
I,
don't
know.
Why
is
this
unhappy
there?
We
go
so
there's
some
weird
things
in
here
so
like
every
there's
account
codes,
but
sometimes
account
codes
aren't
necessarily
unique
unless
they're
paired
with
their
parent
account
code,
which
is
what
your
so.
A
There's
I
don't
know
how
the
the
campaigns
are
kind
of
linked
up,
but
at
the
end
of
the
day
you
should
just
be
able
to.
If
you're
like
I
know
the
account
codes
that
I
want
or
I
know
the
vendors
entities
you
can
just
you
know
some
of
the
I
think.
But
if
we
do
debits
yes,
seven
amount
as
the
spend
yeah
it
should
be,
should
be
good
to
go
there
great.
B
A
A
We
can
just
put
it
in
an
epoch
and
they
have
like,
and
then
we
go
a
pipe
to
spend
and
then
all
these
related
issues,
because
I
think,
like
there's
gonna,
be
specifically
for
the
use
case
of
expenses
coming
through
expensive
fine
into
NetSuite.
It's
like
a
specific
unit
of
work
that
we're
gonna
have
to
do
and
they'll
probably
be
a
merge
request
tied
to
it.
So,
let's
just
we
can
open
an
issue
that
we
can
make
an
epic
if
you're,
okay
with
it
being
in
the
data
group,
or
would
you
prefer
be
it.
B
Seems
like
it's
a
data
thing,
because
it's
not
marketing
opps
there
there's
a
number
of
things
are
going
to
touch
it
that
are
all
going
to
end
up
being
DBT
model
changes,
so
it
makes
sense
in
a
data
group
and
then
we
can
attached
the
finance
issue
in
the
marketing
office
issue
and
the
data
issue
in
yeah
I
think
that
makes
sense
all
right,
she's
already
on
the
data
side.
So
that's
that's
fine
as
well.
Yeah.
A
B
B
Me
scan
I
think
that
was
the
major
thing
is
I
just
want
to
get
an
understanding,
and
when
we
had
originally
discussed
this
I
thought
it's
gonna
be
a
whole
different
thing
to
look
at
because
we
were
acting.
You
have
to
explain
how
the
headcount
was
calculated,
but
we've
just
removed
that
so
I
think
this
became
extremely
simple,
yeah,
very
extremely
simple,
yeah.
A
I
think
you'll
you'll
be
able
to
get
into
so
we've
masked
the
data
in
NetSuite,
but
in
theory,
spend
on
salaries
in
there
as
well
and
so
I
think
at
some
point
you
should
be
able
to
roll
that
back
and
do
it,
but
certainly
isn't
it
like
an
MVC,
a
big
lift
so
that
it
exists.
It's
just
a
matter
of
getting
into
a
form,
that's
usable,
but
it
also
doesn't
like
expose
everybody's
salaries
across
the
board.
Exactly
yeah.