{# DE + SK hreflang odebráno 2026-05-24 — viz core/settings.py LANGUAGES. cross_lang_alternates is set False by views whose CS/EN versions live on DIFFERENT paths (KB articles/categories, blog posts) — there the naive same-path alternate would point at a non-existent URL, so we emit only the self-canonical instead of a wrong reciprocal. #} Skip to content

Lead and B2B measurement with server-side: connect tracking to your CRM

B2B isn't measured like a store — the conversion isn't a sale but a lead that matures in the CRM. How to connect server-side tracking to your CRM and measure lead quality, not just count.

D
DataNostro Team 7. 6. 2026 · 9 min · Intermediate

B2B and lead generation have a different problem than online stores. The conversion isn't a $12.90 purchase but an enquiry that may — or may not — turn into a six-figure deal three months later. Measuring just the number of submitted forms means optimizing for quantity over quality. Here's how to do it right.

Why B2B measurement is harder

  • The conversion matures off-site. The lead is qualified, negotiated, signed — in the CRM, not on the website. The ad platform doesn't know about it.
  • Not every lead is worth the same. A hundred leads where one closes a big deal is very different from a hundred evenly small ones.
  • A long cycle. Months can pass between the ad click and closing — and the client-side cookie expired long ago.

What server-side does about it

  • Reliable lead capture. The form submission is measured server-side, so you don't lose it to an ad-blocker.
  • Longer-lived identification. Server-set first-party cookies last longer, so the longer B2B journey stays connected.
  • Capturing GCLID and context. On arrival from Google Ads you capture the click identifier and store it with the lead — so you can later attribute the closed deal back to the ad.

CRM integration and offline conversions

The key to B2B measurement is closing the loop between the website and the CRM:

  • Create/update a CRM record on conversion straight from the server-side container. DataNostro can do this for HubSpot, Salesforce, Pipedrive and Zoho — see platform connections in the docs.
  • Send offline conversions back to advertising. When a lead in the CRM matures into a deal, send that "offline" conversion (with its real value) back to Google Ads via the stored GCLID. Ads then optimize for actual deals, not submitted forms.
  • Enhanced Conversions for Leads use the hashed email from the form for better matching. More in Enhanced Conversions.

Practical advice

  • Store the source and click identifier with every lead — without them you can't close the loop.
  • Define a "quality lead" and measure that, not just submission count.
  • Send the closed-deal value back to advertising so it learns on profit.

Summary

In B2B, the winner isn't whoever collects the most forms but whoever measures lead quality all the way to the closed deal. Server-side tracking connected to a CRM and offline conversions makes that possible — and shifts ad optimization from quantity to real revenue. Start with the complete guide to server-side tracking.

Share

A new article once a month

In-depth server-side tracking guides + case studies from the CZ market. No spam, just 1 email a month. Unsubscribe anytime.

Back to Tracking