Google Data Manager: What It Changes for Tracking

Olamide Sule, founder of Dolphin Analytics: a digital analytics expert based in London delivering solutions for agency and in-house clients.

Google Data Manager is Google’s front door for getting CRM and first-party data into Google Ads. We set up, audit and fix GA4 and GTM tracking for agency and in-house clients most weeks, and the question we hear now is whether Data Manager changes the import work that sits on top of it. It changes the plumbing. It does not fix the conversion tracking underneath, which is where most teams pulling their hair out with data challenges are actually stuck: leads in the CRM that Google Ads cannot tie back to a click.

This is the walkthrough we give clients: what Data Manager is, which sources it connects, how to set up a connection, and where it breaks.

What is Google Data Manager?

Google Ads Data Manager is a point-and-click tool inside Google Ads that imports customer data from outside Google and puts it to work in your campaigns. Google’s help page says you can import first-party data and use it in Customer Match and offline conversion import. You open it from the Tools icon in the left-hand navigation, then Data manager.

The same help page describes the tool with three terms worth learning before you click anything:

• Data source: the product or file you connect, such as HubSpot, BigQuery or a Google Sheet.
• Connection: the data object pulled from that source.
• Destination: the Google product where the data gets used.

Google’s Data Manager overview also puts two related settings on the same page: managing your Google tag, and setting consent defaults for personal data that arrives through website tags and imports.

What does Data Manager change in your tracking setup?

Data Manager changes how CRM data reaches Google Ads, not what that data needs to contain. In the setups we inherit, CRM data usually reaches Google Ads through a hand-built export or a developer’s script. With Data Manager, a marketer can connect a CRM or warehouse from a menu instead. The rows still need an identifier that matches them to an ad click.

Google’s data preparation guide spells out what an offline conversion row needs: the GCLID (Google Click ID) from the click, and the date and time the conversion happened. The conversion name is optional; Google uses it only to filter which conversion action the row counts toward. For enhanced conversions for leads, Google says at least one of email address or phone number should be mapped. The same guide says Data Manager normalises and hashes those personal fields for you, so the CRM can send plain values.

When we audit accounts, the missing identifier is the fault we find most. Forms that drop the GCLID before it reaches HubSpot, or a CRM field that gets overwritten on the second visit, break the import whichever route carries it. Our offline conversion tracking guide covers the capture step in full, and the enhanced conversions for leads walkthrough covers the hashed-email route.

Which data sources does Google Data Manager connect?

Google publishes a supported data sources table for direct connections, and the use case matters as much as the name. Most sources support both offline conversion import and Customer Match. Two common ones do not.

Source type	Examples from Google’s table	Offline conversions	Customer Match
CRM and email platforms	HubSpot, Zoho CRM, ActiveCampaign, Klaviyo	Yes	Yes
Salesforce	Salesforce	Yes	No
Ecommerce	Shopify	No	Yes
Warehouses and databases	BigQuery, Snowflake, Amazon Redshift, MySQL, PostgreSQL, Oracle	Yes	Yes
Files and storage	Google Sheets, Google Drive, Google Cloud Storage, Amazon S3, SFTP, HTTPS	Yes	Yes

The Shopify gap catches ecommerce teams out. If you want store orders as offline conversions, the usual route is a warehouse or file source that does support it, fed from the store.

How do you connect a data source in Data Manager?

Google’s connect a data source guide requires Google Ads administrator access, and the first row of your data must hold the column headers. File sources must be .csv or .tsv. For conversions, the path is:

1. In Google Ads, click the Tools icon, then Data manager.
2. Under Featured products, pick your source (for example HubSpot).
3. Under Data source, choose Direct connection.
4. Under Use case, choose Conversions.
5. Accept the customer data policy and click Continue.
6. Link the product, then click Next.
7. Upload or select the data, and add filters if you only want some rows (for example, only deals at a qualified stage).
8. Click Next and map each column to its field from the dropdowns: GCLID, conversion name, conversion time, and email or phone.
9. Add transformations if a column needs reshaping, then click Next.
10. Review the connection details and click Finish.

For a Customer Match list, choose Audiences at step 4 and pick the data type (emails and phone numbers, user IDs or device IDs). Google’s connection guide adds two rules that trip teams up: you need one connection per audience or conversion event, and the data source name must stay identical every time its data updates. Agree a fixed file or table name before the first import, and tell whoever owns the CRM export not to rename it.

What are multi-source conversions?

Multi-source conversions, in beta, join your Google tag conversions to a second source such as a CRM or order database. Google’s multi-source conversions page says the transaction ID (order ID) is the key that deduplicates events and matches the upload to the tag. Where they match, the uploaded conversion value permanently overwrites the value the tag recorded. GCLID is listed as highly recommended, and the setup starts with a trial period in which the new source feeds reporting and diagnostics but does not affect bidding.

That overwrite rule is the one to plan around. The CRM becomes the source of truth for value, so a refund or a mistyped deal amount in the CRM flows straight into Google Ads. The tag and the upload must also agree on format: if one sends pounds and the other sends pence, the values will not line up.

What does the Data Manager API add?

The Data Manager API is the code route to the same job. Google describes it as a single ingestion API for data partners, agencies and advertisers, sending audience and conversion data to Google Ads, Google Analytics, Display & Video 360, Campaign Manager 360, Search Ads 360 and Google Ad Manager. It carries Customer Match lists, offline conversions and events, and supports confidential matching and encryption.

Google’s API guidance points it at teams that need automated, code-based ingestion and have the developers to maintain it, or a data partner who integrates on their behalf. Our rule of thumb: stay in the screen while you have a few connections from sources on the supported list. Move to the API when an agency is running the same import across many client accounts, or when the source is not on the list at all.

Is Data Manager a replacement for server-side GTM?

No. The two move different data. Google’s server-side tagging docs describe a server container that runs the familiar tag, trigger and variable model to measure activity wherever it happens. Data Manager moves records you already hold: a closed deal, a subscription renewal, a customer list.

In our work the two sit side by side. Browser and server events tell Google Ads that someone converted on the site; Data Manager tells it which of those leads turned into revenue weeks later. Our server-side tracking guide covers the first half.

How we set up Data Manager for clients

The setup screen takes minutes. The work that decides whether it helps sits upstream: getting a click ID or an email address onto every CRM record, choosing the stages worth importing, and checking the imported numbers against the CRM before bidding relies on them. When we map a client’s data end to end, we often find revenue that none of their marketing tools can see. On one engagement it was this:

For a subscription retailer, we found more than £5M of subscription revenue that no marketing tool could see, so spend could finally be planned against the whole business.

Data Manager is the kind of route that makes that revenue usable in Google Ads, once the identifiers are in place.

When to call someone

Data Manager is self-serve when your source is on Google’s list and your CRM already stores the GCLID. Bring someone in when any of these is true:

• Imported conversions match far fewer clicks than the CRM shows leads from paid search.
• The GCLID field in your CRM is empty on most paid leads, or holds the first click only.
• Your source, or the use case you need, is missing from the supported table.
• You plan to switch on multi-source conversions and are not sure the CRM values are clean enough to overwrite the tag.
• You run the same import across several client accounts and need the API.

If you want a quick outside view of the tags on your site first, run a free Sonar scan. For a person’s read on a messy import, tell us what’s broken, or book a call.