First-Party Data Examples: What Counts and How to Use It

First-Party Data Examples That Actually Move the Needle

A SaaS company I audited last quarter had 14,000 email addresses in HubSpot, three years of Stripe transaction data, and a GA4 property logging 80,000 sessions per month. On paper, plenty of first-party data. In practice, none of it reached their ad platforms. Google Ads was optimising on form submissions. Meta saw maybe half the actual conversions. The CEO was convinced paid media "just doesn't work for us."

The problem was not a lack of data. It was a lack of activation. They had the raw material but no pipeline connecting it to the platforms that needed it.

I will not rehash the first-party data definition here -- if you need to define first party data from scratch, start with the first-party data meaning guide. This post skips the theory. Instead, it walks through concrete first-party data examples organised by category, and for each one shows exactly how to activate it -- the specific integration, the platform feature, and the result you should expect. If you want to understand how first-party compares to third-party data, that is covered in its own post too.

Five Categories of First-Party Data (With Examples)

I find it useful to group examples of first-party data into five categories based on how the data enters your systems. Each has different activation paths and different levels of effort to connect.

1. Declared identity data

Data users give you explicitly: email addresses, phone numbers, names, company names, shipping addresses. It is the highest-value first-party data you own because it enables deterministic matching -- no probabilistic modelling, no cookie dependency.

Example	Where it lives	Activation path
Email submitted at checkout	Ecommerce backend, CRM	Hash and send via Google Enhanced Conversions and Meta Conversions API
Phone number on a lead form	CRM (HubSpot, Salesforce)	Include as a secondary match key in enhanced conversions for web and enhanced conversions for leads
Shipping address at purchase	Ecommerce backend	Hash address fields and pass to Google Ads for improved conversion matching
Business email on a demo request	CRM	Feed back as offline conversion when deal closes; also powers customer-match audiences

How to activate it. Capture the identifier at the moment of interaction, SHA-256 hash it, and send it server-side alongside the conversion event. For Google, this is Enhanced Conversions. For Meta, the Conversions API. For LinkedIn, the LinkedIn Conversions API. The platforms match the hash to a logged-in user, closing the attribution loop even when cookies are gone.

Match quality matters. Google Ads surfaces a coverage metric for enhanced conversions; Meta shows Event Match Quality scores from 1-10. I aim for coverage above 80% on Google and EMQ above 7 on Meta. Below those thresholds, the hashed data is not matching well enough.

2. Transactional data

Purchase records, subscription events, refunds, revenue figures. This data sits in your ecommerce backend, billing system, or ERP -- the ground truth for what your business actually earned.

Example	Where it lives	Activation path
Purchase with order value	Shopify, WooCommerce, custom backend	Send as purchase event with value via server-side tracking; feed into GA4 and ad platforms
Subscription renewal	Stripe, Chargebee, Recurly	Import as offline conversion to Google Ads; send via CAPI to Meta
Refund or cancellation	Billing system	Upload as conversion adjustment in Google Ads to correct ROAS calculations
Contract value (B2B)	CRM (closed-won stage)	Import as offline conversion with actual revenue, not estimated lead value

How to activate it. Transactional data is where the gap between "data you have" and "data your ad platforms see" is widest. Most companies track the front-end conversion (form fill, add-to-cart click) but never send the backend outcome back to the algorithm.

For ecommerce, the fix is a server-side tracking setup that sends purchase events from your backend rather than relying on a client-side tag firing after a thank-you page loads. For B2B, it is offline conversion imports that send real deal values back to Google Ads, or CAPI events that send closed-won signals to Meta. I cover why this matters disproportionately for long sales cycles in the B2B measurement guide.

3. Behavioural data (on-site)

Page views, product views, add-to-cart actions, scroll depth, search queries. Data you observe on your own properties -- collected by your analytics, structured through your data layer, and owned entirely by you.

Example	Where it lives	Activation path
Product views and add-to-cart	Data layer, GA4	Build remarketing audiences; feed product-level signals to Google and Meta dynamic ads
Internal site search queries	Data layer, GA4	Identify demand gaps; feed into keyword strategy
Checkout abandonment (step reached)	Data layer, GA4	Create step-specific audiences for retargeting with tailored creative
Content engagement (scroll, video %)	Data layer, GA4	Score leads by engagement depth in B2B; suppress low-intent traffic

How to activate it. Behavioural data is only as useful as the data layer that structures it. Without a clean data layer implementation, your events are inconsistent and your audiences are unreliable.

Once the data layer is solid, activation splits into two paths. Audience building: create GA4 audiences based on high-intent behaviours (viewed product 3+ times, reached checkout step 3) and export them to Google Ads and Meta for retargeting. Event optimisation: use behavioural events as micro-conversions that feed machine-learning models when macro-conversion volume is too low to optimise directly.

4. CRM and lifecycle data

Lead status, deal stage, lifetime value, churn risk score, support ticket history. This is data your sales and success teams generate daily -- and it is arguably the most underused first-party data in marketing.

Example	Where it lives	Activation path
Lead qualified (MQL/SQL)	CRM	Upload as offline conversion to Google Ads and Meta so bidding optimises for quality, not volume
Deal closed-won with revenue	CRM	Import with actual deal value; this is the signal that teaches Smart Bidding which clicks generate revenue
Customer lifetime value	CRM, billing system	Build value-based lookalike audiences on Meta; use as conversion value in Google Ads value-based bidding
Churn / cancellation	CRM, support system	Create suppression audiences to stop spending on users who already left

How to activate it. The CRM is the richest first-party data source most companies own, and the one least connected to their ad platforms. The activation path is offline conversion imports: export hashed emails and conversion events from your CRM, match them to ad clicks, and let the algorithm learn from real outcomes.

For Google Ads, the mechanism is enhanced conversions for leads -- hashed email sent at form submission, then matched when the offline conversion (deal closed) is uploaded later. For Meta, it is the Conversions API with offline event sets. For LinkedIn B2B campaigns, the LinkedIn CAPI serves the same purpose.

Google Ads accepts offline conversion uploads within 90 days of the click. If your sales cycle is longer, upload intermediate stages (MQL, opportunity created) before the window closes. I cover this timing problem in the long B2B sales cycles guide.

5. Consent and preference data

Consent choices, communication preferences, channel opt-ins. Often overlooked as "first-party data," but it is -- and it directly affects what you can do with everything else.

Example	Where it lives	Activation path
Cookie consent choice	CMP (Cookiebot, OneTrust, etc.)	Feed into Google Consent Mode v2 to enable modelled conversions for non-consented traffic
Email opt-in/out status	ESP, CRM	Enforce suppression; avoid sending to opted-out users (compliance and deliverability)
Marketing channel preferences	Preference centre	Respect choices to build trust; segment by preferred channel for activation

How to activate it. Consent data determines the ceiling for everything else. If your consent implementation is broken -- banners that do not actually block tags, Consent Mode not integrated, consent state not passed to your server container -- then the first-party data you collect downstream may be legally compromised.

Integrate your CMP with Consent Mode v2 so Google can model conversions for users who declined consent. Google reports that Consent Mode recovers on average 65% of ad-click-to-conversion journeys that would otherwise be lost. But the modelling only works if your consented first-party data is clean enough for the model to learn from.

From Collection to Activation: The Common Failure Pattern

Most companies I audit are not short on first-party data. They are short on activation. The failure pattern is consistent:

1. Data exists but is siloed. Emails in the CRM, transactions in Stripe, behaviour in GA4, consent in the CMP -- none of them connected.
2. Only front-end events reach ad platforms. A pixel fires on the thank-you page. The backend conversion (actual purchase, qualified lead, closed deal) never makes it back.
3. No identity bridge. The hashed email captured at form submission is not passed to the conversion tag, so enhanced conversions and CAPI have nothing to match on.
4. Consent breaks the chain. Consent Mode is not implemented, or implemented incorrectly, so the first-party signal from consented users does not feed Google's models.

The fix is not a new tool. It is plumbing: connecting what you already collect to the platforms that need it. That is what my marketing measurement practice is built around -- auditing the gaps and building the pipelines so signal flows end to end.

First-Party Data Marketing: A Quick Activation Checklist

If you want to know whether your first-party data is actually activated, check these five things:

1. Enhanced conversions enabled and validated. Google Ads shows coverage above 80%. You are sending hashed email (at minimum) with every conversion tag.
2. Conversions API running with deduplication. Meta EMQ is above 7. Browser and server events are deduplicated using event_id to avoid double-counting.
3. Offline conversions flowing from CRM. Closed deals and real revenue values are imported to Google Ads and Meta, not just front-end form fills.
4. Consent Mode v2 integrated. Your CMP sends consent signals to Google Tag Manager. Consent state is passed to your server container.
5. Server-side tracking live. A server GTM container runs on your subdomain. Cookies are set server-side, surviving Safari's 7-day cap on JavaScript-set cookies.

If three or more of these are missing, your first-party data is collected but not activated. The first-party data examples above only generate value when the pipeline from collection to ad platform is complete. Otherwise, the algorithms are optimising on a fraction of what you actually know about your customers.

FAQ

Not sure your first-party data is actually reaching the platforms that need it? Get in touch -- I will audit your activation gaps and tell you exactly what to connect.