Demand generation teams, sales-led pipelines, CRM-owned qualification stages, long consideration windows, and a handoff meeting where two systems disagree
B2B lead generation
The form submits, the CRM stores the lead without the source that produced it, and the pipeline built from those records reads as direct, which is the same thing as unattributed with a friendlier name.
Paid, fixed scope · Within ten business days after complete access
Where the click dies
The drawing below crosses one boundary. Watch what the record carries into the CRM, and what never comes back out of it.
Where it dies
The click dies at the CRM boundary. The form writes a record, and the campaign behind it survives that write only where the source was captured on the form and mapped to a field the CRM keeps. Past the boundary the stages are real and none of them returns: qualification and close stay inside the CRM unless somebody built the upload back, so the ad platform keeps buying against form fills and never learns which ones were worth having.
What breaks
Diagnosed first-hand on live accounts, not read off vendor documentation.
The form posts to the CRM through a server-side handler or a third-party embed that was never handed the campaign parameters, so the record lands with an empty source and falls back to direct. Where source is captured, it is often captured on the last page rather than the first, so a returning buyer is credited to the email that reminded them instead of the campaign that found them. Then there is the stage that decides everything downstream. Sales marks a lead qualified inside the CRM, and that state is never sent back to the ad platforms, so bidding optimizes toward form fills. Volume rises. Pipeline does not.
Why nobody catches it
Direct is not an error state. It is a legitimate bucket, so a pipeline weighted toward direct reads as brand strength rather than a broken handoff, and it gets defended as brand strength in the meeting where someone questions it. Underneath that, marketing reports leads and sales reports pipeline, and neither number is wrong on its own. They are built from two records that were never joined, and nobody owns the join. So the argument returns every quarter and is settled by whoever is more senior in the room rather than by evidence.
The work
The field map from ad click through to CRM record, the qualification definition sales agreed to in writing, and an import log showing what matched and what did not.
- 01Capture first touch, persist it, and write it onto the record the CRM actually creates, not onto a cookie that expires long before the deal closes
- 02Agree with sales what qualified means and which field holds it, before anything is sent anywhere
- 03Send that qualified stage back to the ad platforms as an offline conversion, with the identifier that lets it match
- 04Trace one real submission from ad click to CRM record to platform import, and keep the trace
Where it goes missing
The same money, four or five different ways to lose it.
Each of these is a boundary the transaction crosses on its way to being recorded, and each breaks for a structurally different reason, so each one has its own page. Most stacks are running more than one of them at the same time, which is why fixing the obvious one often moves the number less than expected.
- CRM form handoffEmbedded vendor forms, forms that post server-side, gated content and demo requests, and any submission that creates a record in a system the website does not ownRead →
- Offline conversion importSales-led pipelines with qualification stages in the CRM, long sales cycles, and any account where bidding currently optimises toward form fillsRead →
- Marketing automation syncMarketing automation platforms syncing to a CRM, two systems that both hold a source field, and any stack where a lead record is written by more than one toolRead →
- Meeting schedulerDemo requests and sales calls booked through a scheduling tool, embedded booking widgets, and routing tools that qualify and assign in the same stepRead →
- Long consideration windowConsidered purchases with months between first touch and close, committee buying, multiple contacts from one account, and any deal longer than a browser will rememberRead →
Other industries
- Live entertainmentTrampoline parks, waterparks, family entertainment centres, bowling, mini golf, escape rooms, laser tagRead →
- Direct to consumerStorefronts running paid acquisition, checkout extensions and post-purchase upsell apps, subscription and replenishment brands, and the billing system that renews all of itRead →
Start with the smallest useful check
Send one Lead generation and CRM account and we will read its setup before anyone signs anything.
Send the domain, the customer journey, and the platforms that should receive it. The tracking audit shows what is working, what is missing or duplicated, and the exact build recommended next.
Paid, fixed scope · Within ten business days after complete access