Merging first party data with SEO: the cookie stayed, the case for your own data did not change
TL;DR
Difficulty: Intermediate
- Google dropped its plan to remove third party cookies from Chrome (July 2024, confirmed April and October 2025). Safari and Firefox block them already, and UK law needs a yes for advertising tracking.
- Search Console counts organic clicks from Google's side, with no cookie, so it sees visitors your analytics cannot.
- Turn search visitors into subscribers with guides that answer the question and offer something extra, with newsletter consent as a separate unticked box.
- Record the page each subscriber joined on, join to orders in your own database, and value each topic per click, not per session.
The cookieless future I wrote about in 2024 never arrived in Chrome, and it hardly matters. I show why most visitors were already out of reach, how organic search turns into first party data under UK rules, and how a Leeds tea merchant uses her own database to decide which article to write next.
The point: the cookie did not die, and you still need your own data
When I first wrote this piece, the received wisdom was that Chrome would soon block third party cookies and every marketer had to prepare for a cookieless future. That did not happen. Google changed course, and Chrome still has third party cookies today.
The advice survives anyway, for a plainer reason. A large share of your visitors already browse with third party cookies blocked, the UK rules already require a yes before any advertising tracking, and the only data that is reliably yours is the data people give you directly. Search is the best way I know to meet those people, because a visitor who arrives from a search has told you what they want before they have clicked anything.
So this article is about one thing: how to turn organic search visitors into first party data you can actually use, lawfully, and how to measure content by what it teaches you about your customers rather than by traffic alone. The broader paid media side has its own piece, on first party data strategy for cookieless marketing, and the mechanics of the consent banner are in event tracking and consent mode.
One invented business carries every example. Kirkstall Tea is a loose leaf tea merchant in Leeds, run by Amira, selling online at kirkstalltea.example. Every number about it is made up. The law and the Google documentation are real, and footnoted.
What actually happened to third party cookies in Chrome
A third party cookie is one set by a domain other than the site you are on. An ad network's script on a tea shop's page sets one, and the same cookie is read again on a news site, which is how the network knows it is the same browser. That cross site recognition is what retargeting and most cross site measurement were built on.
Here is the timeline, from Google's own announcements.
On 22 July 2024 Google said that instead of deprecating third party cookies, it would introduce a new experience in Chrome that lets people make an informed choice applying across their browsing.1 On 22 April 2025 it went further: it would maintain its current approach to offering users third party cookie choice in Chrome, and would not roll out a new standalone prompt.2 On 17 October 2025 it confirmed that approach again and retired most of the Privacy Sandbox technologies that were meant to replace cookies, including Topics, Protected Audience and the Attribution Reporting API, citing limited expected value and low adoption.3
So, said plainly: Chrome did not deprecate third party cookies, there is no new prompt coming, and most of the replacement technology is gone. The old version of this article said Chrome would soon follow Safari and Firefox. That was the plan in 2024 and it is not true now, so I have corrected it.
The other browsers never waited. Safari has blocked third party cookies by default since March 2020, when WebKit described it as the first mainstream browser to do so.4 Firefox confines cookies to the site that created them, which Mozilla calls Total Cookie Protection, and made it a default for all desktop users worldwide in 2022.5
And in the UK the law sits on top of whatever the browser allows. The ICO's guidance on storage and access technologies says there are no advertising purposes that meet the strictly necessary exception, and that you must get consent for any cross site or cross device tracking.6 The regulator behind that guidance is now the Information Commission (still the ICO on its website). The Data (Use and Access) Act 2025 established the Information Commission7 and abolished the office of Information Commissioner with effect from 30 September 2026.8
Worked example: how many of Kirkstall's visitors can a retargeting cookie reach?
Amira wants to know whether the Chrome news changes anything for her. Two facts decide it: which browser a visitor uses, and whether they said yes to advertising.
Her server logs record the browser of every request, no cookie involved. For October they show 48% Safari, 44% Chrome, 3% Firefox and 5% other browsers. Safari and Firefox block third party cookies by default, so only Chrome and, at most, the other 5% can carry one. That is 49% at the very most, and less in practice, because some Chrome users switch them off.
Her consent banner, counted in aggregate, shows that 60% of visitors accept advertising cookies.
A visitor can only be reached if both things are true. If we treat the two as independent, the share is the product of the two probabilities:
Here is the share of visitors a third party retargeting cookie can follow, is the share whose browser accepts third party cookies, and is the share who accepted advertising on the banner. Multiplying probabilities for "both" is covered in Foundations: probability, including when the independence assumption breaks.
Step by step: . At most about 29% of Kirkstall's visitors are reachable by a third party cookie, and Chrome keeping its cookies did not change that by a single visitor. For seven in 10 visitors, the future Amira was told to prepare for arrived years ago.
First party data, in plain words
First party data is information your business collects directly from the people it deals with, on its own site, in its own shop, through its own forms. Orders, email sign ups, answers to a quiz, a request for a sample, a reply to an email.
Second party data is someone else's first party data, shared with you under an agreement. Third party data is collected by a business with no direct relationship to the person, usually across many sites, and sold or used on.
The old version of this article called first party data "permission based" by nature. That is too generous. Collecting data yourself does not make it lawful, and it does not mean the person agreed to everything you might want to do with it. Under UK GDPR, data must be collected for specified, explicit and legitimate purposes, and be limited to what is necessary for those purposes.9 What makes first party data valuable is not that it is automatically clean, it is that you know where it came from and can make it clean.
Worked example: sorting Kirkstall's data into the three kinds
Amira lists what she holds or uses.
- Orders in her shop database, with name, address, email and what was bought: first party.
- Email addresses from the newsletter form: first party.
- Answers to her tea finder quiz: first party.
- A list of tea lovers offered by a Bristol cookware shop under a joint promotion agreement: second party, and she needs to check exactly what those people agreed to before she touches it.
- Interest audiences she can target inside an ad platform, built from browsing across other sites: third party.
Only the first three belong to her relationship with the customer. The rest of this article is about growing those three from search.
Search Console sees your organic traffic without a single cookie
Here is the fact that makes Search Engine Optimisation (SEO) the natural partner of first party data. Google Search Console reports your performance in Google Search from Google's side of the click. It does not depend on a tag running in the visitor's browser, so a visitor who rejects your cookies is still counted there.
Google's own help page puts the contrast mildly: Search Console data may differ from tools such as Google Analytics, which track traffic only from users who have JavaScript enabled, and Search Console removes duplicates and visits from robots.10 Its Performance report gives four metrics. Clicks are the number of times a user clicked through to your site from Google Search results. Impressions are how often your site appeared. Click through rate (CTR) is clicks divided by impressions. Average position is the average position of the topmost result from your site.11
Two limits matter. First, privacy filtering: queries that are not issued by more than a few dozen users over two to three months are anonymised and never shown as rows, although their clicks are included in the chart totals unless you filter by query.12 Second, row limits: the interface exports 1,000 rows, while the API and the Looker Studio connector allow up to 50,000 rows per day per site per search type.12
Worked example: Kirkstall's October, seen from Google's side
Search Console shows Kirkstall's site appeared 210,000 times in Google Search in October and received 6,300 clicks.
is the click through rate, clicks is the number of clicks from Google Search to the site, and impressions is the number of times the site appeared in results. It is a rate, events over opportunities, explained in Foundations: ratios and rates.
Step by step: , so 3.0%.
Amira exports the query rows and adds them up: 5,355 clicks. The gap, clicks, about 15%, came from anonymised queries. They are real visitors, she just cannot see what they typed.
In Google Analytics 4 (GA4), the same month shows 3,900 sessions from organic Google search. Her banner shows that about 62% of visitors accept analytics, and , which is close. That match is partly luck, because a click and a session are not the same thing and are counted by different systems. But it makes the point: GA4 sees the consenting share, Search Console sees everyone who clicked.
Keep the search data longer than Google does
Search Console keeps 16 months of performance data. When you link it to GA4, the Search Console reports in Analytics are limited to the same 16 months, the data appears about 48 hours after collection, and the two reports you get show queries and landing pages, with Landing page, Device and Country as the only Analytics dimensions they combine with.13 GA4 itself keeps user level data for either two or 14 months on a standard property, a setting that affects explorations and funnel reports, not the standard aggregated reports.14
That is fine for this month's questions and poor for a three year view of which topics bring which customers. Search Console offers a bulk data export: a daily export of performance data to BigQuery, Google's data warehouse, with every query except the anonymised ones.15 Once it runs, the data accumulates in your own warehouse for as long as you choose to keep it. Your shop database already keeps every order for as long as you keep it.
Worked example: what Amira keeps, and where
Amira switches on the bulk export in November, so from that day her warehouse holds every day's query and page data. She keeps her orders in the shop database as she always has. She sets GA4 retention to 14 months, the longest a standard property allows.14
A year later she can ask a question none of the tools answers on its own: which queries led to pages that produced newsletter subscribers who bought within 90 days. The search side comes from the export, the subscriber and order side from her own database. Nothing in that question needs a cookie. If you want the warehouse plumbing in detail, my BigQuery setup for a Rails and Solidus shop walks through it.
The path from a search to a known person
A search visitor is anonymous. To turn them into first party data, the page has to offer something worth leaving an email address for, and the form has to collect that address lawfully. The order of events matters, so here it is as a flow.
Read the flow from the top. The first box is the only one Google sees. Everything from the second box down happens on Amira's site and is hers. The decision box is the legal hinge: what the visitor asked for and what they agreed to receive afterwards are two separate things, and the page keeps them separate.
The UK rules for email you collect from search
Two sets of rules apply. UK GDPR governs the personal data itself. The Privacy and Electronic Communications Regulations (PECR) govern the marketing emails you send.
Under regulation 22 of PECR, you must not send unsolicited direct marketing by email unless the recipient has consented, with one exception, known as the soft opt in. It applies when you obtained the person's contact details in the course of a sale or negotiations for a sale, you only market your own similar products and services, and you gave them a simple, free way to refuse both when you collected the details and in every message since.16 Since 5 February 2026 there is a separate soft opt in for charities, which does not help a tea shop.16
The ICO's guidance on electronic mail marketing explains what "negotiations" means. The person must actively express an interest in buying your products or services, such as signing up to a free trial or requesting a quote, and simply logging in to browse is not enough.17 For consent, it says the consent must clearly cover your email marketing, and you must not use pre ticked boxes, silence or inactivity as evidence of consent.17
Worked example: Kirkstall's three sign up points
Amira collects email addresses in three places, and each needs its own reasoning.
- Checkout. A customer buying tea gives an email address to complete the sale. This is a sale, so the soft opt in can apply to marketing for similar products, provided the checkout offers a clear way to refuse there and then, and every email after carries an unsubscribe link.16
- The brew chart download on the water guide. Reading a free guide is not actively expressing an interest in buying tea, so I would not rely on the soft opt in here. The page sends the chart the visitor asked for, and asks for newsletter consent with its own unticked box.17
- The newsletter box in the footer. Plain consent, worded to say exactly what arrives and how often.
Gated content is a trade, so make it a fair one
Gating means putting something behind a form: you get the resource once you give an email address. It works when the resource is worth more than what you ask for. It fails, commercially and legally, when the visitor is forced to accept marketing to get it.
The ICO's guidance on valid consent says you should not make consent a condition of a service unless the processing is necessary for that service, and that bundled consent is presumed not to be freely given.18 It also says you can incentivise consent to some extent, as long as you do not unfairly penalise people who refuse.18
My practice follows from that. The email address needed to send the chart is the price of the chart. The newsletter is a separate question, and saying no to it changes nothing about what the visitor receives. And I never gate the answer to the search query itself. The page answers the question in full, then offers something extra. Someone who searched "what water is best for green tea" and finds a form instead of an answer goes straight back to Google.
Worked example: the water guide's capture rate
The guide "Brewing tea with Leeds tap water" answers the question on the page and offers a printable brew chart by email. In October it received 2,400 clicks from Google Search, according to Search Console. 192 visitors requested the chart, and 71 of those also ticked the newsletter box.
is the capture rate, is the number of people who gave an email address, and is the number of organic clicks to the page. It is another rate, see Foundations: ratios and rates.
Step by step: , so 8% of searchers asked for the chart. Then , so 37% of those also chose the newsletter. And , so about 3% of the page's search visitors became newsletter subscribers. Using Search Console clicks as the denominator means the rate does not depend on who accepted cookies.
Interactive tools: ask only what you will use
A quiz, a calculator or a finder tool is useful twice. It helps the visitor decide, and every answer tells you something about what they need. The old version of this article was right about that. What it left out is the limit: UK GDPR requires personal data to be adequate, relevant and limited to what is necessary for the purpose.9 A question you will never act on is a question you should not ask.
Worked example: the Kirkstall tea finder
Amira's first draft of the tea finder asked eight questions: age, gender, postcode, birthday, caffeine, milk, preferred flavour, and how the visitor brews. I go through them with her, one by one, asking what each changes in the recommendation.
Age, gender and postcode change nothing. Birthday would be used for a discount email, which is marketing and a separate purpose. So four questions stay: caffeine or not, milk or not, which flavour family (malty, floral, smoky or fresh), and teapot, infuser or bags. Four answers are enough to recommend three teas.
In October 3,800 visitors from search reached the finder, 1,150 completed it, and 230 asked for their results by email with the newsletter box ticked. The completion rate is , and the share who completed and subscribed is . The 230 records hold an email address, four answers and the page they started on. Every field is used in the next section.
Record where each subscriber came from, and segment by topic
This is the step most sites skip, and it is the one that turns content into customer insight. When someone signs up, store which page the form was on. No cookie is needed: the form simply sends its own page path along with the email address, in a hidden field. Then join subscribers to orders in your own database by email address, and tell people in your privacy notice that you do this.
Grouping subscribers by the topic of the page they joined on shows which questions bring buyers. In GA4, a sign up can also be marked as a key event, which Google defines as an event that measures an action particularly important to the success of your business,19 but GA4 only sees consenting visitors. The shop database sees every subscriber and every order.
Worked example: Kirkstall's subscribers by entry topic
Amira groups her content into four topics and looks at everyone who subscribed from July to September, and what they spent in their first 90 days. The query runs on her own database:
SELECT s.entry_topic,
COUNT(DISTINCT s.email) AS subscribers,
COALESCE(SUM(o.item_total), 0) AS revenue_90d
FROM subscribers s
LEFT JOIN orders o
ON o.email = s.email
AND o.completed_at >= s.subscribed_at
AND o.completed_at < s.subscribed_at + INTERVAL '90 days'
WHERE s.subscribed_at >= '2026-07-01' AND s.subscribed_at < '2026-10-01'
GROUP BY s.entry_topic
It returns four rows. Brewing guides: 310 subscribers, £4,030. The tea finder: 230 subscribers, £5,520. Gift guides: 140 subscribers, £4,620. Caffeine and health questions: 180 subscribers, £1,260.
The revenue per subscriber is a mean:
is the mean 90 day revenue per subscriber in a topic, is the number of subscribers in that topic, and is what subscriber spent in their first 90 days, zero for those who bought nothing. The mean and its weak spots are in Foundations: the mean.
Step by step: brewing guides . Tea finder . Gift guides . Caffeine and health .
The gift guide subscribers spend nearly five times as much as the caffeine readers. That is a product insight as much as a marketing one: gift buyers want boxes and bundles, and Amira's newsletter for them should look nothing like the one for people asking whether green tea keeps them awake.
Measure content by what each click is worth
The old article said to measure content by its contribution to audience intelligence rather than sessions or bounce rates. I agree, but a principle you cannot put a number on tends to lose to a traffic chart in a meeting. So here is the number I use: the expected value of one organic click to a topic.
is the expected value of one organic click, is the probability that a click becomes a subscriber (the capture rate from earlier), and is the mean 90 day revenue per subscriber. It is an expected value, a probability times a payoff, covered in Foundations: expected value, and the capture rate is a rate from Foundations: ratios and rates.
It is deliberately conservative. It ignores visitors who buy without subscribing, and it uses revenue where margin would be more honest. Use margin if you have it.
Worked example: which Kirkstall topics deserve the next article
From July to September, Search Console shows organic clicks per topic: brewing guides 7,750, tea finder 4,600, gift guides 2,800, caffeine and health 12,000.
Capture rates, subscribers divided by clicks: brewing , finder , gifts , caffeine .
Value per click, capture rate times revenue per subscriber: brewing , finder , gifts , caffeine .
Multiplied by 1,000 to make them readable:
The horizontal axis shows the four content topics. The vertical axis is the expected 90 day revenue, in pounds, from 1,000 organic clicks to that topic. The caffeine pages bring the most traffic, 12,000 clicks, and the least value, £105 per 1,000. The gift guides bring the fewest clicks and the most value, £1,650 per 1,000, about 16 times as much. A traffic report would tell Amira to write more about caffeine. Her own data tells her to write the next gift guide.
That does not mean deleting the caffeine pages. They answer real questions, they earn links, and they bring people to the site who may buy later. It means the next hour of writing goes where a click is worth most.
What I would build, in order
If Amira came to me, I would do the work in this order.
- Search Console verified and linked to GA4, with the bulk export to BigQuery switched on from day one, because it only collects from the day it starts.1315
- Every sign up form sends its page path, and every subscriber record carries the consent wording they saw and the date.
- Gated offers that never hide the answer, with the newsletter as a separate unticked box.1718
- Interactive tools stripped down to the questions that change the result.9
- A monthly report from the shop database: subscribers and 90 day revenue by entry topic, and the value of 1,000 clicks per topic.
- Only then, the paid side, using the same first party data. That is a separate project, covered in the first party data strategy for cookieless marketing.
None of it depends on what Chrome does with cookies next year. In the shops I have worked on, that is the real argument for first party data: not that the cookie is dying, but that this data is yours, measured from your side of the counter, and it keeps working whatever the browsers decide.