Google Ads Data Manager Update on 16 November: What's Changing?

From 16 November 2026, the way Google Ads Data Manager processes customer data is changing. Google has announced that it will drop the requirement to send customer data pre-hashed with SHA-256 and will support encrypted data processing by default.

At first glance it looks like a small technical update, but it matters for advertisers who build Customer Match lists, send CRM data to Google Ads or upload offline conversions.

The update also takes effect just 11 days before Black Friday on 27 November. A problem with customer data transfers could cause trouble during one of the busiest campaign periods of the year.

So what exactly is changing in Google Ads Data Manager? What does dropping the hashing requirement mean? Could existing integrations be affected?

In this article we cover the new data processing model, its possible effects on advertisers and what to check before 16 November.

How is Google Ads Data Manager changing on 16 November?

Google Ads has long used SHA-256 hashing to match customer data with the ad platform.

Hashing turns information such as an email address or phone number into a fixed-length digest through a one-way mathematical operation. Google can then compare these digests with its own account data to match eligible records.

Whether advertisers hash data before sending it to Google depends on the integration method. In Google Ads' manual customer list uploads, for example, the hashing can also be done by tools Google provides.

The 16 November change specifically concerns how Google Ads Data Manager processes data.

According to the notice Google sent to advertisers, as reported by industry publications, in the new system:

• Customer data will no longer have to be pre-hashed with SHA-256.

• Data received through Data Manager will go through an encrypted processing flow.

• Google will process the data in a hardware-isolated environment called a Trusted Execution Environment (TEE).

• In this environment the necessary data will be decrypted, normalised and matched with Google account data.

• Matched records can be used for ad targeting and conversion measurement, subject to the relevant eligibility rules.

The change covers four data transfer methods:

1. CRM connections

2. Transfers via cloud storage

3. Direct file uploads

4. Data Manager API

However, Google's public announcement doesn't explain all the technical details of how existing hashed data uploads will be handled in the new system.

So the change doesn't mean existing integrations necessarily have to be rebuilt.

What's the difference between hashing and encryption?

To understand the new Google Ads update, you need to know the difference between hashing and encryption.

Both are used in data security, but they don't do the same job.

Hashing turns data into a fixed-length digest through a one-way mathematical operation. A SHA-256 digest is conventionally shown as a 64-character hexadecimal value.

Under normal conditions, hashing can't be reversed. But that doesn't mean hashed personal data is always anonymous.

Encryption prevents data from being read without the right key. Unlike hashing, encrypted data can be decrypted again with the correct key.

The two methods aren't complete alternatives to each other. Some data processing flows use both.

In fact, Google's existing Confidential Matching with Encryption documentation explains that in certain encryption flows personal data is first hashed and then encrypted.

So the 16 November update doesn't mean Google is abandoning hashing across all its systems.

Why is Google Ads dropping the SHA-256 requirement?

The main reason Google gives is to reduce formatting errors when matching customer data.

With hashing, even a tiny difference in the data produces a completely different result.

For example:

• An extra space in an email address

• Upper and lower case not being normalised

• A phone number saved without the country code

• Data fields not formatted as expected

If these issues aren't fixed before hashing, they can hurt match rates.

Google's new approach aims to reduce these errors by normalising data inside the secure processing environment.

Will Customer Match rates increase?

They may, but it isn't guaranteed.

Imagine you have a list of 10,000 customers.

If some of the email addresses on the list were saved in different formats, normalisation errors could stop some records from matching Google accounts.

The new processing approach can help reduce losses caused by this kind of error.

But data format isn't the only thing that determines Customer Match rates.

Whether customers can be matched to a Google account, how current the data is, account eligibility and Google's data use policies all affect the result.

Google says in the announcement that it aims to improve match accuracy, but it hasn't shared a verified figure for how large that improvement will be.

Who does the Google Ads Data Manager update affect?

The effect depends on how you send customer data to Google Ads.

Check priorities are a general assessment based on the likely need for technical intervention.

Teams that have built their own data transfer infrastructure in particular should review this update carefully.

But there's an important detail here: Google's announcement doesn't say existing hashed data will definitely be rejected after 16 November.

So it may not be the right move for advertisers to remove their hashing straight away or start sending customer data in a different format.

The first step is to confirm that your integration is compatible with Google's current documentation.

6 checks before the Google Ads Data Manager update

The most important preparation before 16 November is to review your current data transfer processes and set a reference point for comparison.

1. Identify the channels your customer data comes through

List the methods by which customer data reaches your Google Ads account.

Check CRM integrations, cloud storage connections, manual file uploads and API transfers separately.

If you use more than one method, each may have a different data processing flow.

2. Record your current Customer Match results

Record the state of your customer lists before 16 November.

In particular, track:

• Number of customer records uploaded

• Customer Match rates

• Usable audience size

• Upload and processing errors

• Offline conversion upload counts and results

This data can serve as a reference for assessing any differences after the change.

Remember that matching can take time to complete. So don't directly compare a newly uploaded list with an older list that has finished processing.

3. Check with your CRM and integration provider

If you use HubSpot, Salesforce or a third-party data integration tool, review your provider's statements about the update.

In particular, find out whether your current connection supports the new data processing model and whether any configuration change is needed on your side.

4. Review your own scripts and API integrations

If you send data with custom software, check your current pipeline with your technical team.

Review the data formats, hashing fields, encryption options and error messages in the Data Manager API documentation.

Don't assume your current system will stop working. But don't remove hashing or start sending raw customer data without verifying first.

5. Monitor the first automated uploads

For the first data transfers after 16 November, don't just check whether the job completed.

Also check the processing status of uploaded records, error messages, usable audience size and offline conversion results.

A successful file upload doesn't mean every customer record matched a Google account.

6. Prepare Black Friday customer lists early

It can help to prepare the customer lists you plan to use in Black Friday campaigns before 16 November and upload them with your current system.

That gives you a chance to spot integration issues before the busiest campaign period. For the other settings to check before Black Friday, see our ad account checklist.

Remember, though, that lists need to be kept appropriately up to date and customer data must be processed with the necessary permissions.

Google Ads Data Manager updates in 2026

The 16 November change is part of Google's work throughout 2026 to build first-party data integrations around Data Manager.

Other changes to Customer Match, offline conversions and API integrations were made during the year.

These changes show Google steering advertisers towards Data Manager and the Data Manager API.

But the 1 April and 15 June rules don't mean all existing Customer Match or offline conversion uploads via the Google Ads API were shut off.

The restrictions concern integrations that don't meet the past usage conditions Google set.

IP matching for advertisers in Turkey

In 2026 Google also announced features for using additional signals in Customer Match, such as IP addresses and user interaction timestamps.

But the use of this data is subject to geographic and policy-based restrictions.

In particular, there are exceptions for users in the European Economic Area, the United Kingdom and Switzerland.

Users in Turkey may fall outside these geographic exceptions, but that doesn't mean IP addresses can be used unconditionally.

Data must be collected appropriately, Google's Customer Match policies must be followed and personal data protection obligations must be met.

Google Ads Customer Match and KVKK: what to watch for

One important aspect of the 16 November update is how customer data is protected.

Although hashing and encryption are different methods, both play a role in data security.

Google's new Data Manager approach provides for incoming data to be processed inside a hardware-isolated Trusted Execution Environment (TEE).

A TEE is a security technology designed to isolate the processing of sensitive data from the rest of the system.

Google's Confidential Matching infrastructure isn't entirely new, though. The company announced the approach in 2024. The 2026 update is a new stage in how that existing technology is used in Data Manager's data processing.

Using a secure processing environment doesn't remove personal data protection obligations, however.

One important point: customer data hashed with SHA-256 isn't always considered anonymous data.

Records that can be matched or re-linked with other information in particular may still count as personal data.

So businesses that send customer data to Google Ads should review:

• The purposes for which data is collected and used

• The required explicit consent and privacy notice processes

• The legal conditions for transferring personal data abroad

• Their integration providers' data processing practices

• Access, retention and security policies

For businesses in Turkey, these assessments need to be made in line with KVKK, Turkey's data protection law, and related legislation. We cover the general obligations for Shopify stores in our KVKK and ETBİS compliance guide.

In data uploads that agencies carry out on behalf of clients in particular, it's important to clarify each party's responsibilities.

Frequently asked questions

What does Google Ads Data Manager change on 16 November 2026?

Google has announced that it will drop the requirement to send customer data pre-hashed with SHA-256 through Data Manager and will support encrypted data processing by default.

Can I keep sending hashed customer data?

Google's current documentation includes methods that work with hashed data. But the 16 November announcement doesn't explain in detail how all older upload flows will be handled in the new system. So check the current documentation and your provider's statements before changing your integration.

Will my Customer Match rate increase?

It may, but it isn't guaranteed. Google aims to reduce errors caused by data formatting. The real effect depends on data quality, how matchable your users are and the integration you use.

Do I need to change anything if I upload CSVs manually?

Google Ads already supports options for hashing customer data in manual uploads. So if you only upload manually, you may not need a major technical change. You should still check the current file template and your upload results.

Do Data Manager API users need to update their integrations?

It hasn't been confirmed that every integration needs a mandatory update. Checking current data formats and supported methods is recommended, especially for custom-built pipelines.

Does this change affect Enhanced Conversions?

Customer data sent through Data Manager and used for conversion measurement may be affected by the new processing approach. But it can't be said that all Enhanced Conversions setups running only through the Google tag will change in the same way.

Can the update be turned off?

The public announcement doesn't mention a clear opt-out for this change. That doesn't mean there are no configuration options at all, so check the current Data Manager settings.

Conclusion: review your data transfer processes before 16 November

The 16 November 2026 Google Ads Data Manager update is a significant change in how customer data is sent to and matched by the ad platform.

The new approach may help reduce formatting errors and improve match accuracy.

But higher match rates and a smooth transition aren't guaranteed.

Advertisers who work with customer lists and offline conversion data, especially ahead of Black Friday, should check their current integrations, record reference data and monitor the first uploads after the update.

Above all, don't read Google's new processing model as meaning your existing hashing setup must be removed.

The right approach is to verify your current data flow, check technical compatibility and test any change before rolling it out.

Sources

1. PPC Land: Google Ads Data Manager stops requiring hashed customer data November 16

2. Google Ads Data Manager: Confidential Matching with Encryption

3. Google Ads Help: About the Customer Matching Process

4. Google Ads Help: Create a Customer Match List by Uploading a Data File

5. Google for Developers: Data Manager API Release Notes

6. Google for Developers: Google Ads API Feature Deprecations

7. ContentGrip: Google Ads Customer Match IP and Timestamp Signals