Google Ads Change History
gadschangehistory.comby
BM
Change historychevron_rightGoogle Adschevron_rightOct 18, 2026

Google Ads Data Manager to stop requiring SHA-256 hashed customer data from November 16, 2026

Date
Oct 18, 2026 (first reported)
Effective
Nov 16, 2026
Regions
Global
Primary source
PPC Land

Google emailed Data Manager users to say that from November 16, 2026 it will no longer require customer data to be hashed with SHA-256 and will accept encrypted data by default, decrypting, normalizing and matching it inside a hardware-isolated trusted execution environment. The formatting and hashing work moves from the advertiser to Google.

The notice covers CRM connections, cloud storage imports, direct file uploads and the Data Manager API, and names Customer Match and enhanced conversions in Google Ads. Google says the change should offer better performance and improve match accuracy by removing errors from formatting differences before hashing, without giving figures. Matched records are marked as matched and used for targeting and measurement. The email states no country exclusions and does not mention Display & Video 360 or Google Analytics, though both receive data through the Data Manager API. Open questions: whether existing hashed uploads keep working and at what match rate, whether the change is optional, who holds encryption keys on routes other than the API, how the trusted execution environment can be verified, what happens to unmatched records and how long decrypted data persists. Google's confidential matching in a trusted execution environment was announced in 2024 and the Data Manager API already offered optional encryption, so the change makes encryption the default and drops hashing as a requirement.

Sources

Related changes

Undo

← See this change in the change history