B2B lead generation
CRM form handoff
The campaign parameters exist in the browser and the record is created by a server, so unless the parameters are put into the submission on purpose they never make the trip and the lead lands with no origin.
Paid, fixed scope · Within ten business days after complete access
What breaks
Embedded 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 own
A campaign parameter is a property of the URL a browser loaded. A server handler receiving a form post sees the fields it was sent and nothing else. If the submission does not carry the source explicitly, as fields, the record is created without it. The fallback is not an error state, it is direct, which reads as a legitimate result rather than as missing data. Embedded third-party forms make it worse: the form renders inside a frame the page does not control, so code on the page that would have added the fields never gets the chance, and the vendor captures only what its own frame could see.
Why nobody catches it
Direct is a plausible bucket for B2B. Buyers genuinely do type the domain in, they genuinely do arrive from unlinked sources, and a large direct share reads as brand strength to anyone predisposed to believe it. That reading is defended in the room, because the alternative is admitting a measurement gap in front of the people funding the channel. Underneath it, the form works perfectly and the lead reaches sales, so nothing ever escalates the problem to the person who could fix it.
The work
The field map from ad click to created record, and the record itself from a real submission showing the source populated.
- 01Capture first touch on arrival and persist it somewhere that survives the visit, not only for the page the form sits on
- 02Write the source into the submission as fields the handler actually receives, and confirm the fields exist on the destination object
- 03Establish what an embedded form can and cannot see from inside its frame before designing around it
- 04Submit one real form and read the created record to confirm the source arrived
Elsewhere in lead generation and crm
One stack usually has more than one of these.
These boundaries compound. A brand running a hosted checkout and a subscription plan has two separate reasons for its channel report to be wrong, and fixing one leaves the other in place. The audit establishes which are live on your stack before anything gets rebuilt.
Start with the smallest useful check
Send one account running forms into the crm 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