Google dropped its plan to remove third-party cookies from Chrome, yet ad measurement still leaks: iPhones restrict tracking, dashboards mix in modelled conversions, and many Indian enquiries close on WhatsApp or the phone. Conversion APIs, offline imports, UTMs and asking every lead still show what works.
A small ad budget can still show which channels bring paying customers, as long as you stop relying on the ad dashboards alone. Send outcomes from your own records back to Google and Meta, tag every link you control, ask every new enquiry how they found you, and judge channels monthly on cost per qualified enquiry.
The cookie story did not end the way it was meant to. Google abandoned its plan to remove third-party cookies from Chrome, and Chrome accounted for about 90 per cent of browsing in India in March 2026, according to StatCounter. Measurement still leaks, just not for the reason most people expected: iPhones restrict tracking, dashboards fill gaps with modelled numbers, and many Indian customers see an ad on one device, then call or WhatsApp you from another.
- Chrome's share of browsing in India, March 2026
- 90%
- Chrome's share of browsing in India, March 2026
- iOS share of mobile browsing in India the same month
- 6%
- iOS share of mobile browsing in India the same month
- Attribution models Google Analytics dropped in November 2023
- 4
- Attribution models Google Analytics dropped in November 2023
- Privacy Sandbox technologies Google decided to retire in October 2025
- 10
- Privacy Sandbox technologies Google decided to retire in October 2025
01
What actually happened to cookies
The short history explains why so much 'cookieless' advice from a few years ago is out of date. Safari and Firefox did lock third-party cookies down by default, but Chrome, by far the most used browser in India, kept them.
Jan 2020
Chrome plans to end third-party cookies
Google sets out a path towards making them obsolete.
Mar 2020
Safari blocks them all
Third-party cookies are blocked by default across the board.
Apr 2021
App Tracking Transparency
iPhone apps must ask before tracking people across other companies' apps and websites.
Jun 2022
Firefox isolates cookies
Total Cookie Protection gives every site its own cookie jar by default on desktop.
Nov 2023
Google Analytics drops four models
First click, linear, time decay and position-based attribution are removed.
Jul 2024
Google changes course
Chrome will keep third-party cookies and offer users a choice instead.
Apr 2025
No cookie prompt either
Google keeps Chrome's existing cookie settings and drops the planned standalone prompt.
Oct 2025
Privacy Sandbox winds down
Google decides to retire the Attribution Reporting API, Topics and eight other technologies.
Taking all of these factors into consideration, we've made the decision to maintain our current approach to offering users third-party cookie choice in Chrome.
02
Where measurement really leaks
Apple is the first leak. Beyond Safari's cookie blocking and App Tracking Transparency, Apple's Link Tracking Protection removes tracking information from links shared in Mail and Messages and from links in Safari Private Browsing, and Safari 26 stopped known fingerprinting scripts from reading URL parameters in September 2025. In India, where Safari had under 3 per cent of browsing in March 2026 and iOS about 6 per cent of mobile browsing, this leak is real but narrow.
The second leak is that dashboards now blend observation with estimates. Google Ads models conversions it cannot observe, for example from Safari, Firefox and iOS apps covered by App Tracking Transparency, and reports both kinds together in the Conversions column. Modelled figures can take up to five days to settle. Google Analytics 4 now offers only data-driven attribution and two last-click options.
The third leak is the biggest for Indian small businesses: the sale happens off the website. A customer sees your Instagram ad, saves the number and phones next week. A patient taps a Click-to-WhatsApp ad and books in the chat. No pixel sees either outcome unless you send it back.
03
Close the loop with your own data
The fix is to send real outcomes back. On Google, enhanced conversions for leads captures a hashed email address or phone number from your website form, then lets you upload the same details when that lead becomes a customer, so the sale is matched to the ad. Google calls it an upgraded form of offline conversion import and advises sending the click ID as well whenever you have it. Phone numbers must include the country code, which for India means +91.
On Meta, the Conversions API sends events from your server or CRM, and Meta calls it the recommended way to send offline and in-store events. For Click-to-WhatsApp ads, the Conversions API for Business Messaging lets your WhatsApp provider report what happened in the chat, such as a qualified lead or a purchase, tied to the original ad click through a click ID. That data opens up purchase optimisation, so Meta can look for people who buy, not just people who say hello.
Uploading customer contact details is processing personal data, so say so in your privacy notice and on your forms. India's DPDP Rules, notified on 14 November 2025, give businesses 18 months to comply and require a clear notice of the specific purpose for which data is collected.
| Where the enquiry happens | What to send back | Tool |
|---|---|---|
| Website form | The form submission, then the sale | Google enhanced conversions for leads; Meta Conversions API |
| Click-to-WhatsApp chat | Qualified lead or purchase, matched to the ad click | Meta Conversions API for Business Messaging |
| Phone call after an ad click | The outcome, logged against the stored click ID or contact | Google offline conversion import |
| Walk-in or referral | The answer to 'How did you hear about us?' | Your CRM |
04
UTMs, and the question every lead gets asked
For links you control, UTM tags still work. Google Analytics recommends always setting utm_source, utm_medium and utm_campaign, treats values as case sensitive, and warns that missing parameters show up as '(not set)' in reports. Agree a naming scheme once, write it down, and use it everywhere.
Then add the cheapest tool in attribution: ask. Put a required 'How did you hear about us?' field on every form, and have whoever answers the phone or WhatsApp record the answer in the CRM. Self-reported answers are imperfect, but they catch what no tracker can, such as a friend's recommendation or a hoarding near your shop.
- Lowercase everything: utm_source=instagram, never Instagram.
- One source per platform, so facebook and instagram stay separate.
- One medium per channel, such as cpc, paid_social, email, whatsapp or qr.
- Campaign names that match the campaign in the ad platform exactly.
- A tagged QR code on every flyer, standee and visiting card.
05
Read it monthly, not daily
Small budgets produce small numbers, and small numbers swing. Google itself suggests judging Smart Bidding over periods with at least 30 conversions, such as a month or longer, and modelled conversions keep updating for days. A daily dashboard on ₹30,000 a month is mostly noise, and optimising into noise burns money.
Review once a month with a rolling three-month view: spend, enquiries, qualified enquiries and customers by channel, with cost per qualified enquiry as the deciding number. When platform data and your CRM disagree, trust the CRM. Our post on splitting a small budget shows how to rebalance on that number.
06
What to do this month
- Switch on enhanced conversions for leads in Google Ads, and capture email and phone on every form.
- Set up the Conversions API for website events in Meta Events Manager, then ask your CRM or WhatsApp provider to send qualified leads and sales back.
- Store the click ID with each lead in your CRM, so offline outcomes can be matched later.
- Add a consent and purpose line to every form that collects a phone number or email.
- Publish a UTM naming sheet and use it on every link, email and QR code.
- Make 'How did you hear about us?' mandatory on forms, calls and chats.
- Review monthly on cost per qualified enquiry over a rolling quarter.
Sources
Checked against the official documentation and announcements below, current as of 23 April 2026.
- Google Privacy Sandbox, October 2025
- Google Privacy Sandbox, April 2025
- Google Privacy Sandbox, July 2024
- Google Ads: conversion modelling
- Google Ads: enhanced conversions for leads
- Meta: Conversions API for Business Messaging
- Google Analytics: attribution settings
- StatCounter: browser market share in India, March 2026
