Latest · Ad platforms

Google Drops the Hashing Rule. Your Pipeline Still Needs Checking

October 19, 2026

Starting November 16, Google Ads Data Manager stops requiring SHA-256 hashing for Customer Match and enhanced conversions uploads. Encryption takes its place. That's the whole announcement, and it's quietly a bigger deal than it sounds.

For years, your CRM-to-Google pipeline hashed every email and phone number before it left the building. Somebody on your team or at your agency built that step, tested it, and hasn't touched it since. Now the requirement underneath it is changing, and what happens to data you've already hashed under the old method is unknown. Does it keep working? Does it need to be reprocessed? Nobody's said.

If retargeting past tour prospects or matching leased-up residents for renewal campaigns runs through Customer Match, that pipeline is worth a five-minute look before November 16, not after. The failure mode here isn't dramatic. It's quiet. Conversion counts just start looking a little off, retargeting audiences shrink a little, and three weeks later someone's asking why cost-per-lead crept up and nobody has an answer because nothing "broke."

Talk to whoever built or maintains your integration, whether that's internal IT, your CRM vendor, or your PPC agency, and ask them directly what changes on their end. If they say "nothing," get that in writing. If they're not sure, that's your answer too.

This is a plumbing update, not a strategy one. But plumbing is exactly the kind of thing nobody checks until the basement floods.

Source: PPC Land, October 18, 2026