What changed
Third-party browser cookies degraded before Google managed to remove them. iOS App Tracking Transparency (2021) removed IDFA for over 80% of iOS users. Safari and Firefox have been blocking third-party cookies by default for years. Chrome restricted cross-site tracking through Privacy Sandbox.
The result: advertising pixels work at forty to sixty percent of their potential accuracy, especially on mobile devices. For B2B where clients use corporate laptops with ad blockers - even less.
What first-party data is
First-party data is data you collect directly from your users with their explicit consent:
- Email at registration or when downloading a resource
- Behavior on the site (pages, clicks, time) through your own analytics tool
- Interaction history in CRM (calls, meetings, emails)
- Data from forms (interests, company size, budget)
This is your data, not the data of an advertising platform or a data broker.
Why this matters for B2B
In B2C, first-party data is needed for personalization. In B2B - for attribution and budget decisions.
If you don’t know which channel each lead came from (and each closed deal), you can’t make informed decisions about your advertising budget. Every marketing decision becomes intuitive.
Practical collection methods
UTM parameters in CRM
The basic method: add UTM parameters (utm_source, utm_medium, utm_campaign) to every advertising link, and when a lead is created, save them in the CRM.
Implementation: hidden fields in the form, populated by JavaScript from URL parameters. Or a webhook from the form that passes the UTM to the CRM API.
This gives first-touch attribution: you know where the lead came from initially.
Click IDs (gclid, fbclid, li_fat_id)
Advertising platforms append proprietary click IDs to the URL when a user clicks an ad. Capture them the same way as UTMs - via JavaScript into the form - and save them in the CRM.
Click IDs allow the Conversions API to accurately match a conversion to a click on the platform side without a pixel.
Conversions API (server-side)
Instead of a browser pixel: your server sends the conversion event (lead, deal, purchase) directly to the advertising platform’s API. Data flows server-to-server, the browser is not involved.
Meta CAPI, Google Ads Enhanced Conversions, LinkedIn Conversions API all work on this principle. Matching is done by email (SHA-256 hash), phone, or click ID.
Progressive profiling
Instead of a long form upfront: a short form (email, name), and additional data is requested later - on the next page, in a follow-up email, on a call.
Conversion from traffic to lead is higher (fewer fields = fewer drop-offs), and data accumulates gradually in the CRM.
“How did you hear about us?” field in CRM
The old-school manual method that works better than many technical solutions. An SDR or AE asks on the first call: “How did you find us?” and records the answer in the CRM.
Combining UTM attribution with the manual field gives the most complete picture.
EU and GDPR
In the EU, data collection requires a legal basis. For first-party data:
- Explicit consent at registration or form submission
- Legitimate interest for behavioral analytics of registered users
A cookie banner is required for any non-essential cookies. First-party analytics without cookies (Plausible, Fathom) doesn’t require a banner.
For Conversions API: you’re passing hashed client data (email, phone) to advertising platforms. This is permissible when you have a Privacy Policy that mentions sharing data with third parties and user consent in place.
Tools for closing the data loop
Collecting first-party data is the first step. The second: connecting data from different sources (advertising, site, CRM) into a single picture.
Prooflytics does this for B2B: captures UTM and click IDs on site visits, attaches them to CRM leads, closes the loop on deals, and shows real CAC by channel.
Takeaway
First-party data is not a technical challenge, it’s an organizational one. Start simple: UTM on every link, UTM on every lead in the CRM, a “source” field that the SDR fills in. This takes a day to implement and produces the first data within a week.
Technical tools (Conversions API, server-side events) add accuracy, but without the basic UTM discipline they’re useless.