Google Data Manager Switch: What to Baseline Nov. 15

Sealed envelopes and a server cage in a dim agency room at dusk

Google Data Manager stops requiring SHA-256 hashes on November 16, 2026, and will support encrypted customer data by default, then decrypt, normalize, and match it inside a hardware-isolated trusted execution environment. The notice is an unquantified match-accuracy claim for Customer Match and enhanced conversions, and it leaves integration and privacy questions open. The useful step on November 15 is a baseline, not a rewrite of connectors that already succeed.

Updated November 15, 2026

Key Takeaways

  • Data Manager stops requiring SHA-256 hashes on November 16, 2026.
  • Encrypted lists are decrypted, normalized, and matched inside a TEE.
  • Google cites better match accuracy but gives no lift figure.
  • API guides still said to hash as of November 1, 2026.

What does the Google Data Manager switch actually change?

The notice in the trade press is an undated email, Encryption in Google Ads Data Manager, posted on LinkedIn on October 18 by Anthony Higman, founder and CEO of ADSQUIRE. PPC Land quotes Google writing to accounts that use the tool “to import first-party offline customer data for Customer Match and enhanced conversions.” The public copy ends mid-message. November 16 is the effective date, not a date on the email.

Google’s rationale is one line: “We’re updating Google Ads Data Manager to offer better performance and to leverage our latest innovations in privacy-enhancing technology.” The change itself:

Starting on November 16, 2026, we will no longer require hashed customer data (SHA-256) for Google Ads Data Manager and will instead support encrypted customer data by default. This change improves match accuracy using privacy-enhancing technology and minimizes errors caused by formatting discrepancies prior to hashing.

Routes named: CRM connections, cloud storage imports, direct file uploads, and the Data Manager API. Google then “decrypts, normalizes, and matches this data with Google account data” inside the TEE. Matched records are “marked as matched” and used “to improve relevant targeting and measurement.”

On our reading, the moved job is formatting. A trailing space, a capital, or a missing country code changes the hash and fails silently. API rules from the December 9, 2025 launch put that cleanup on the advertiser or a partner.

Where is the match-rate upside, and where is it not?

There is no published lift. Google says the change “improves match accuracy” and, as PPC Land reported, cites no percentage, test, or comparison with current rates. An unnumbered accuracy claim is not a forecast. Hold spend shifts until you can score that conversion claim before budget moves.

Search Engine Watch notes Smart hash already normalizes and hashes some connections, so this is not only a CSV fix. PPC Land records that confidential matching has used a TEE by default since September 2024, at no extra charge. Encryption was still optional on Google’s April 2026 Ads DevCast.

Item Before November 16 What the undated email says
Hashing SHA-256 required No longer required
Encryption Optional, on confidential matching Default
Normalization Advertiser or partner, before the hash Google, inside the TEE
Published lift None given Improves match accuracy; no figure

Which integrations and privacy reviews are still open?

Several integration questions are unanswered. The email does not say if scheduled SHA-256 uploads keep working or match as well as encrypted data, who holds keys on each route, or whether “by default” can be declined. As of November 1, Tofu Ads Agent found no official help article, and API guides updated October 21 still said to hash. The encryption guide says “Don’t encrypt unhashed values.”

Only Data Manager routes are covered. Customer data terms are unchanged in the email, PPC Land noted. Policy still requires your privacy policy to say you share customer data with third parties to perform services, and consent where the law or Google’s policies call for it.

PPC Land reported that Kamal Janardhan, then senior director of product management for measurement, said around the September 2024 introduction of confidential matching that the system isolates business data during processing so that nobody, Google included, can access it. PPC Land’s separate inference, which Google does not state, is that readable emails, phones, and addresses exist inside the TEE during decrypt and normalize.

What should performance teams baseline on November 15?

Our baseline day is November 15. Boxoo, last checked November 13, still says to confirm after November 16 that uploads succeed and match rates hold.

  1. Leave working uploads unchanged through November 16.
  2. List each Data manager connection and any confidential matching badge.
  3. Note whether the CRM, the connector, or Google formats and hashes.
  4. Save dated diagnostics, Customer Match rates, and enhanced-conversion counts.
  5. Keep API hashing until Google revises the guides.
  6. If you must hold the key, Google’s Cloud KMS path can be “complex or infeasible” off an object store such as Google Cloud Storage.
  7. Brief legal with the email. Terms are unchanged; consent still has to cover sharing data with Google.
  8. Hold any assumed lift out of a Black Friday media reset.

Frequently asked questions

When does Data Manager stop requiring SHA-256?

Google’s undated email to Data Manager users, first posted October 18, 2026, sets the effective date at November 16, 2026, for Customer Match and enhanced conversions, with encrypted data supported by default.

How much will match rates improve?

Google says the change improves match accuracy and minimizes errors caused by formatting discrepancies prior to hashing. No percentage, test, or benchmark is in the email or the trade reports here.

Will hashed uploads still work?

The email does not say. No longer requiring hashes suggests they may still be accepted, but it does not confirm scheduled SHA-256 uploads will keep working.

Should developers stop hashing API payloads now?

Not on the November 1 record. Tofu Ads Agent reported the API guides still said to hash and not to encrypt unhashed values.

Notice an error?

Help us improve our content by reporting any issues you find.