Home › Guides › Google Ads Data Manager

Google Ads Data Manager: what lead-gen businesses should send first

By Abhishek Thakral · abhi.performs, Dubai · Updated October 2026 · 9 min read

As of 19 Oct 2026, Google Ads Data Manager is the main route for getting CRM data into Google Ads, and the way it handles that data is about to change. PPC Land reported on 18 October that Google has told advertisers Data Manager will stop requiring SHA-256 hashed customer data from 16 November and will accept encrypted data by default.

Most lead-gen businesses I work with in the UAE have never opened Data Manager. Their best data, which leads turned into viewings, consultations and sales, sits in a CRM or a spreadsheet and never reaches the bidding system. This guide covers what the tool does, what to send first, the formatting mistakes that quietly drop rows, and what the hashing change means for you.

What Google Ads Data Manager does

Google describes Data Manager as a data import and management tool with a point-and-click interface. You find it in Google Ads under the Tools icon in the left-hand menu, then Data manager (About Google Ads Data Manager, Google Ads Data Manager Help).

It works with three ideas:

• Data source. Where the data comes from: an imported file, a connected product such as BigQuery or HubSpot, or a third-party integration. Google also lists Amazon Redshift, MySQL, Oracle, PostgreSQL, SFTP, Snowflake and HTTPS.
• Connection. One table or file pulled from that source.
• Destination. Where the data gets used. For Google Ads that means Customer Match, offline conversion import and enhanced conversions for leads.

The useful part is reuse. You connect a source once and can send it to more than one destination. The same Data manager page also holds your Google tag settings and default consent settings for website and uploaded data.

If you have a developer, there is also the Data Manager API. Google launched it in December 2025 as one connection for uploading audience lists and sending offline conversion events, available for Google Ads, Google Analytics and Display & Video 360. (Google Ads & Commerce blog, 9 Dec 2025). For most small and mid-sized accounts, the point-and-click version is enough.

The 16 November change: hashed to encrypted

Until now, the standard advice for customer data was to hash it with SHA-256 before it left your systems. Google's own help centre still describes that process for anyone who hashes their own files.

According to PPC Land, a Google email shared on LinkedIn says that from 16 November 2026 Data Manager will no longer require SHA-256 hashed customer data. It will accept encrypted data by default, then decrypt, normalise and match it inside a Trusted Execution Environment. The email names Customer Match and enhanced conversions (PPC Land, 18 Oct 2026).

Treat the detail with some care. The email is undated, Google had not published a help page or announcement on it when I wrote this, and it does not say whether files you already hash keep working or whether the new route is optional. Check the notice in your own account and Google's help centre before you change anything that runs today.

The direction is not new. In September 2024 Google introduced confidential matching, which processes uploaded data inside a Trusted Execution Environment, and made it the default for Customer Match connections, including those made through Data Manager, at no extra charge. Google said advertisers can get attestation that data was processed as intended, and that those with strict policies could encrypt data before it leaves their servers (Google Ads & Commerce blog, 12 Sep 2024). The reported change makes that encrypted route the default instead of the exception.

For most advertisers the practical effect is less formatting work on your side. For anyone with a script or agency pipeline that hashes files before upload, it is a reason to check that pipeline in November rather than assume.

What to send first if you sell offline

Data Manager can feed audiences and conversions. If a sales team turns your enquiries into revenue, those two are not equal.

1. Lead outcomes first. Send what happens after the form: qualified lead, booked viewing or consultation, closed deal. This changes what Smart Bidding optimises towards, which is where the money is.
2. Exclusion lists second. Existing customers and leads you have already marked as junk, uploaded as Customer Match lists, so you stop paying to reach them again. Meta needs the same list for the same reason, see Meta custom audiences and its automatic customer exclusions.
3. Targeting lists last. Past buyers as a signal for similar people. Useful, but it will not rescue a campaign that is bidding on the wrong conversion.

The destination for lead outcomes depends on how you track. Google's help page says that for enhanced conversions for leads you map at least an email or phone number, and the GCLID is optional if your Google tag is set up for user-provided data. For offline conversion import, the GCLID is required (Prepare your data for import, Google Ads Data Manager Help). If your forms do not capture the GCLID today, enhanced conversions for leads is the easier path.

This is the same principle I set out in fix your ad tracking first: the platform can only find more of what you tell it counts. If you run a Google Ads lead form, the qualified answers in the form are a start, and the CRM outcome is the stronger signal.

How to connect a source in Google Ads Data Manager

The flow is the same for most sources:

1. Open Tools, then Data manager, and choose to connect a product or upload a file.
2. Pick the source. A CSV export from your CRM is fine to start. HubSpot and BigQuery connect directly. Database and SFTP connections need Google's listed IP ranges allowed in your firewall.
3. Choose the destination: a conversion action for lead outcomes, or a customer list for Customer Match.
4. Map the columns to Google's fields and apply the date and time conversion.
5. Set a schedule for recurring imports, so outcomes keep flowing without someone remembering to upload.
6. Check the run history after the first import and compare rows sent with rows accepted.

Formatting traps that silently drop rows

Google's preparation guide has several rules that catch UAE accounts in particular:

• Phone numbers in E.164. That means a plus sign, the country code and the number, with no spaces, dashes or brackets. A UAE mobile saved as 050 123 4567 needs to become +971501234567.
• Dates in the right order. Google warns that a date like 02/01/2026 can be read as month first, and if the system detects a single row in DD/MM/YYYY format the import fails. Most UAE spreadsheets are day first, so convert dates to YYYY-MM-DD before export.
• A fallback timezone. Conversion rows without a timezone are not imported unless you set one. Set Asia/Dubai if your CRM stores local times.
• Headers and file names. The first line of a CSV must hold the column headers, and a file without an extension is rejected.
• Hashing only if you choose to. Data Manager can normalise and hash personal data for you. If you hash yourself, lowercase and trim emails first, and never hash IP addresses or timestamps.

For Customer Match, Google lists email, phone and mailing address fields, with country codes and names formatted to its rules. Optional fields include IP address and an interaction timestamp, and a timestamp cannot be sent without an IP address.

Consent and who owns the data

Data Manager has its own consent settings for uploaded data, and the people in your list should have agreed to their data being used this way. Check your privacy policy and consent wording with whoever handles legal for your business before the first upload. For consent on the website itself, see the Consent Mode v2 guide.

If you run Meta alongside Google, the same CRM export can feed both platforms. The Google tag gateway guide covers the website side of first-party data. Data Manager covers everything that happens after the lead leaves your site.

What to do now

1. Open Data manager in your account and see what is already connected under Connected products.
2. Agree one outcome with your sales team that means a good lead: a qualified status, a booked appointment or a sale.
3. Export it weekly with email, phone in E.164, date in YYYY-MM-DD and a timezone. Capture the GCLID on your forms if you can.
4. Connect it as enhanced conversions for leads or offline conversion import, schedule it, and check rows accepted after the first run.
5. Upload an existing-customer list to Customer Match and use it as an exclusion.
6. In mid-November, check any pipeline that hashes files before upload against Google's help centre, and read the notice in your account.

This is part of how I set up Google Ads management: real outcomes into the account first, then bidding and budget.

Frequently asked questions

Related