Google Says Data Manager Stops Requiring Hashed Data on Nov 16. Its Help Pages Still Say Hash. Change Nothing Yet
The short version
An undated Google email, posted to LinkedIn and reported by PPC Land on October 18, says that starting November 16, 2026, Google Ads Data Manager "will no longer require hashed customer data (SHA-256)" and will support encrypted customer data by default, across CRM connections, cloud storage imports, direct file uploads and the Data Manager API. Two days out, Google's own documentation does not say that. Read on November 14, the Data Manager help pages still say customer data should be hashed, that Data Manager hashes it for you, and that encryption is optional. The Data Manager API formatting guide, last updated November 3, still requires SHA-256 before any encryption. Nothing I read says hashed uploads stop working. The move: do not rebuild a pipeline for this date. Make sure someone checks every upload on the 16th and 17th.
What Google announced
Google has not published this anywhere I could find. The source is an email titled "Encryption in Google Ads Data Manager," shared on LinkedIn by Anthony Higman of ADSQUIRE and written up by PPC Land on October 18. PPC Land notes the copy carries no send date. As quoted there, the email says:
- Date: "Starting on November 16, 2026, we will no longer require hashed customer data (SHA-256)."
- Default: Data Manager "will instead support encrypted customer data by default."
- Scope: CRM connections, cloud storage imports, direct file uploads and the Data Manager API.
PPC Land also flags what the email leaves out: it does not say what happens to files advertisers already hash, and it does not say whether the change is optional.
Google's live pages, read November 14, describe the current setup. The Prepare your data for import page says imported private customer data "should be hashed," that Data Manager will hash it with SHA-256 for you, and that this smart hashing is automatic. The Confidential matching with encryption page says confidential matching is now the default technique for building audience lists, and that encrypted data is an optional feature "not required by Google." Its own steps still say to hash PII fields with SHA-256 before encrypting, using keys held in Google Cloud KMS. The Data Manager API formatting guide (updated November 3) says to hash email and phone with SHA-256, and to Base64-encode the hash bytes if you encrypt. None of the three pages mentions November 16.
What it actually means
Two different things are being described, and they are easy to blur. Confidential matching is about where Google does the match, inside an isolated environment, and Google's page says it is already the default. Encryption is about what you send, and today it sits on top of hashing, not instead of it. The email describes a further step: encrypted data in, no SHA-256 required. If that ships, it changes the formatting rules your connectors follow. It has not shipped in the documentation.
So the risk is not that hashing stops working on Monday. Nothing on the record says that, and "no longer require" is not the same as "no longer accept." The risk is a partner tool or an in-house script that changes its format on the 16th because of the email, while Google's side still expects hashed input, or the reverse. Either way the symptom is quiet: a Customer Match list that stops refreshing, or fewer offline conversions arriving. Those feed customer lifecycle goals, value-based bidding and the offline conversion imports your bidder learns from, and a stale list does not raise an error banner. Nine days before Black Friday, that is the failure worth catching.
Google's incentive is plain enough. Fewer formatting rules means more uploads succeed and more first-party data reaches the bidder, which helps match rates and helps Google. That is a reasonable change. It would be more reasonable with a help page and a date on it.
The email has a date. The documentation does not. Until they agree, the pipeline that works today is the one to keep.
Signal or noise: medium, mostly as a monitoring job
Medium if you upload customer lists or offline conversions through Data Manager, a CRM connector, cloud storage or a partner tool, because a format change two days before an undocumented date is how quiet failures start. It moves to High the day Google publishes the change in its help pages with a date. Low if you send Google no first-party data. Nothing to switch on or off this week.
The Monday-morning playbook
- List the uploads. Every account that sends customer lists or offline conversions, and the path for each: Data Manager connection, cloud storage, file upload, Data Manager API, Google Ads API or a partner tool.
- Name an owner for each. The person who gets the error email. If nobody does, that is your finding, and it matters more than the date.
- Do not change formats for November 16. Google's pages still document hashing, and nothing says hashed uploads will be rejected. Keep what works.
- Ask partner tools one question in writing. Are you changing your upload format on or around November 16, and if so, based on what Google documentation?
- Record a baseline today. Last successful upload, list size, match rate and offline conversions per day, for each path.
- Check on November 16 and 17. First upload ran, list size held, conversion counts in line with the baseline. If anything drops, check the format before touching bids.
- Re-read Google's two help pages on the 16th. If they change, revisit this playbook. I will update this brief if they do.
Related: Customer lifecycle goals depend on the customer list these uploads keep fresh.
This rollout is logged on the Google Ads changes and deadline calendar and rated on the signal vs. noise ledger, both reviewed weekly.
The bottom line
November 16 is a date in an email, not yet a date in Google's documentation. Keep hashing, make sure every upload has an owner, and check the 16th and 17th like you would any pipeline change before peak season. If Google publishes the change, the rebuild can wait until after Cyber Monday unless the docs say otherwise.
Frequently asked
Does Google Ads Data Manager still require SHA-256 hashing?
As of November 14, 2026, Google's Data Manager help pages say customer data should be hashed and that Data Manager hashes it with SHA-256 automatically, and the API guide still requires SHA-256 before any encryption. A Google email reported by PPC Land says the requirement ends on November 16, 2026, but no Google help page I read says so.
What happens to existing Customer Match lists on November 16?
Google's documentation does not say anything changes on November 16. The email describing the change does not say what happens to files advertisers already hash, so nothing on the record says existing lists or hashed uploads stop working. Check that each list refreshes on the 16th and 17th.
How do I check that my Data Manager uploads still work?
Record a baseline before November 16: last successful upload, list size, match rate and offline conversions per day for each upload path. On November 16 and 17, confirm the first upload ran and the numbers held. If something drops, check the upload format before changing any bidding.
Get the next brief in your inbox
When Google ships something that matters, you'll get the decode: what changed, whether it's signal or noise, and the move worth making this week. Free, no firehose, unsubscribe any time.