First-party data: What is left of tracking when cookies disappear?

First-party data is data your business collects itself, directly from customers: enquiries, orders, newsletter sign-ups, CRM data and behaviour on your own website. As browsers, operating systems and consent banners keep restricting tracking via third-party cookies, this data of your own becomes the most important foundation for advertising and analytics.

Why traditional tracking has gaps

• Many visitors reject marketing cookies in the consent banner.
• Browsers such as Safari and Firefox heavily restrict cookies from other domains.
• Ad blockers suppress tracking scripts.
• Customers switch between phone, laptop and calling you.

The result: Google Ads, Meta and Analytics miss part of your conversions. Automated bidding learns from incomplete data and gets worse.

Which first-party data you can use

1. Conversions from your CRM: Which enquiry turned into a deal, and at what value?
2. Customer lists: Email addresses of existing customers, uploaded in hashed form, for example to exclude them from new-customer campaigns.
3. Form data: for enhanced conversions in Google Ads.
4. Website data on your own domain: for example via server-side tagging on your own subdomain.

What the law says

Even your own data may only be used with a legal basis. For advertising purposes, that is usually consent. Customer lists may only be uploaded if your privacy policy covers it and customers have been informed accordingly. Your own data makes tracking more robust, but it does not make it consent-free. If in doubt, get advice from a data protection specialist.

How to get started

1. Check what data sits in your CRM and whether it is linked to where the enquiry came from.
2. Build forms so that the source, such as the Google click ID, is stored with the enquiry.
3. Set up enhanced conversions in Google Ads.
4. Send closed deals from your CRM back to Google Ads on a regular basis.
5. Adapt your consent banner and privacy policy to how the data is used.

Related reading: Enhanced conversions: When are they worth it, and what do you need? and Tracking audit: How often should you have Analytics and Tag Manager checked?

FAQ

What is the difference between first-party, second-party and third-party data?

First-party data is collected by you, directly from your customers and visitors. Second-party data is a partner’s first-party data that they share with you under an agreement. Third-party data comes from providers who gather data from many outside sources and resell it, often via third-party cookies.

Does Consent Mode replace the use of first-party data?

No, the two complement each other. Consent Mode makes sure Google tags respect the user’s consent choice and uses modelling to estimate missing conversions from users who did not consent. First-party data such as form or CRM data, on the other hand, provides real, measured results and so improves the basis automated bidding learns from.

Do I need server-side tracking to use first-party data?

Not necessarily. Enhanced conversions and importing CRM data also work without a tagging server of your own. Server-side tagging is mainly worth it if you want more control over which data goes to which ad platform and want to consolidate measurement on your own domain.

When to hand this over

• Your ad platforms report far fewer enquiries than you actually receive.
• Your CRM and ad accounts are not connected.
• You are unsure which data you may use and how.

We connect ad accounts, Analytics and CRM with clean consent handling. Learn more about strategy & analysis or book a free initial consultation.