A reported Google Ads Data Manager notice says SHA-256 pre-hashing will no longer be required from November 16, with encrypted customer data processed inside a trusted execution environment. Here is what advertisers should verify before the change.
Google Ads Data Manager is preparing a significant change to how advertisers submit first-party customer data. According to an email notice sent to some accounts using Data Manager, from November 16, 2026, advertisers will no longer be required to pre-hash customer data with SHA-256. The notice says encrypted customer data will be supported by default and processed inside a hardware-isolated trusted execution environment (TEE).
The reported change covers Data Manager workflows used for Customer Match and enhanced conversions, including CRM connections, cloud storage imports, direct file uploads and the Data Manager API. It could reduce errors caused by inconsistent formatting before hashing, but advertisers should confirm the implementation details for their own integrations.
What is changing?
Historically, advertisers and their integration partners commonly normalized customer identifiers—such as email addresses and phone numbers—and hashed them with SHA-256 before uploading them for matching. A small formatting difference, such as an extra space or a phone number without the correct country code, can produce a different hash and prevent a match.
The reported Google notice says Data Manager will instead accept encrypted customer data by default. Google will decrypt, normalize and match the data inside a trusted execution environment. Google says the approach is intended to improve match accuracy and reduce errors caused by formatting differences before hashing.
Which workflows are covered?
- CRM connections used to import first-party customer data
- Cloud storage imports
- Direct file uploads in Data Manager
- Data Manager API integrations
- Customer Match and enhanced-conversions use cases named in the reported account notice
Why this matters for advertisers
1. Fewer pre-upload formatting errors
If Data Manager normalizes supported identifiers during processing, advertisers may have fewer failures caused by inconsistent casing, whitespace or phone-number formatting. Google has not published a quantified match-rate improvement for this change, so businesses should measure their own results rather than assume a specific uplift.
2. Integration workflows may need review
Agencies and businesses that currently hash customer data in a CRM, ETL pipeline or custom API integration should review the new requirements before changing production workflows. Do not remove existing hashing logic until the relevant Google documentation and the account’s upload route confirm what formats are accepted.
3. Privacy and governance teams should review the processing model
The notice describes Google decrypting, normalizing and matching data inside a hardware-isolated trusted execution environment. This is an important detail for privacy, security and legal reviews. Organisations should examine the applicable Google terms, technical documentation, consent basis, data-retention arrangements and any client-specific data-processing commitments.
What advertisers should do before November 16
- Check the account notice: confirm whether the Google Ads account has received the Data Manager notification and which workflows it covers.
- Inventory data pipelines: document CRM connections, cloud storage jobs, direct uploads and API integrations that send Customer Match or conversion data.
- Do not prematurely remove hashing: wait for route-specific instructions and test in a controlled workflow. The reported notice does not fully explain how existing hashed uploads will be handled.
- Review encryption requirements: establish whether a particular upload method requires configuration, key management or partner-side changes.
- Validate data quality: compare upload diagnostics, match rates and conversion measurement before and after the change.
- Update governance documentation: involve privacy and security stakeholders where customer identifiers are transferred or processed.
Important documentation caveat
This update is based on an account email reproduced publicly and reported by PPC Land on October 18, 2026. The notice says the change begins November 16, 2026, but several implementation questions remain unanswered in the reproduced text, including whether existing hashed uploads continue unchanged, whether advertisers can choose to keep hashing, and what configuration is required for each import route.
Google’s currently accessible Data Manager and enhanced-conversions documentation still describes hashing and related data-handling options. Advertisers should therefore treat the reported notice as a change to verify against the latest documentation and the specific account workflow—not as confirmation that every Google Ads customer-data upload method has already changed.
Key takeaway
The reported November 16 update could simplify first-party data imports by shifting more normalization and matching work into Google’s confidential processing environment. For now, advertisers should audit their Data Manager integrations, retain working pipelines until the applicable instructions are clear, and validate both match quality and privacy requirements before making changes.
Sources and further reading
- PPC Land — Google Ads Data Manager stops requiring hashed customer data November 16 (October 18, 2026; reporting based on a reproduced account email).
- Google for Developers — Data Manager API overview.
- Google Ads Help — Set up enhanced conversions for web.
