The most valuable information about a Google Ads campaign does not always exist inside Google Ads.
Google Ads can record that somebody clicked an advert and submitted a form. However, the advertising platform may not initially know whether that enquiry was suitable, whether the sales team contacted the lead, whether a quotation was accepted or how much revenue the customer eventually generated.
That information usually lives elsewhere—in a CRM, sales pipeline, booking platform, customer database, payment system or data warehouse.
Google Ads Data Manager helps connect these systems. It provides a central interface for bringing selected first-party data into Google Ads and activating it for advertising use cases such as conversion measurement and Customer Match.
For lead-generation businesses, this can connect advertising activity with later CRM outcomes such as:
Qualified Lead
Appointment Booked
Sales Opportunity
Quotation Accepted
Customer Acquired
Revenue Generated
For ecommerce and retail businesses, it can help connect customer and transaction data from systems beyond the website, including repeat purchases, telephone orders, in-store sales and customer lists.
The strategic value is straightforward: Google Ads can move beyond optimising for the first measurable action and receive feedback about the outcomes that matter to the business.
What Is Google Ads Data Manager?
Google Ads Data Manager is a data import and connection tool within Google Ads. It uses a point-and-click interface to connect external customer data sources with supported Google Ads destinations.
It can connect data held in systems such as CRMs, databases, cloud storage platforms and structured files. The data can then be mapped, filtered, transformed, scheduled and used for supported advertising purposes.
Google describes Data Manager as a central place for connecting first-party data with its advertising products. In practical terms, it sits between a source and a destination:
Data source → Data Manager connection → Google Ads use case
For example:
HubSpot lifecycle data → Data Manager → Qualified Lead conversion
Or:
Customer database → Data Manager → Customer Match audience
Or:
Google Sheet containing completed sales → Data Manager → Converted Lead and revenue imports
Data Manager also brings linked products, Google tags and first-party connections into a more central management area. Its map view can display supported routes from data sources through connection mechanisms to conversion destinations, making complex account setups easier to understand and troubleshoot.
Why Google Introduced Data Manager
First-party data activation has traditionally required a mixture of manual uploads, separate product links, CRM-specific integrations, scheduled files, automation platforms and custom API development.
That created several problems:
Connections were configured in different parts of Google Ads.
Each source used a different setup process.
Field mapping and formatting often required technical work outside Google Ads.
Manual files became outdated.
Failed imports were not always identified quickly.
Advertising teams could not easily see where data originated.
CRM and marketing teams frequently used different definitions for the same outcome.
Data Manager does not remove every technical challenge, but it creates a more consistent connection framework. An advertiser can select a source, choose a use case, map fields, apply transformations, define filters and schedule refreshes from a central interface.
This is increasingly important because modern Google Ads optimisation depends on the quality of the data supplied to it. Automated bidding can only learn from the conversion actions and values it receives.
If every form submission is treated as equally valuable, Google Ads will attempt to generate more form submissions. If the account also receives accurate Qualified Lead, customer and revenue data, bidding can be aligned more closely with commercial outcomes.
The Two Main First-Party Data Use Cases
Data Manager supports two particularly important forms of first-party data activation: conversions and audiences.
Conversion Measurement
Conversion connections import events that occurred after or outside the original website tracking process.
For a service business, the journey might be:
Advert click → Website enquiry → Qualified Lead → Sales Opportunity → Customer → Revenue
The first enquiry may be recorded by the Google tag. Later stages are recorded in the CRM and returned to Google Ads using Data Manager or another supported upload method.
This is commonly called offline conversion tracking, although the outcome does not need to happen physically offline. A sales stage recorded in an online CRM, a payment completed through an invoicing platform or a contract signed electronically can all be treated as imported conversions because they occurred outside the original website conversion event.
Google now recommends enhanced conversions for leads over legacy offline conversion imports where the setup is suitable. Enhanced conversions for leads can combine user-provided data, such as an email address or telephone number, with identifiers, such as the GCLID, improving the ability to connect later CRM outcomes with earlier advertising interactions.
Learn more in our guides to Google Ads offline conversion tracking and enhanced conversion tracking for leads.
Customer Match Audiences
Customer Match uses first-party customer information to create audience segments in Google Ads.
Depending on account eligibility, policy requirements and campaign type, these audiences can support uses such as:
Re-engaging existing customers
Excluding current customers from acquisition campaigns
Reaching known prospects or subscribers
Differentiating existing customers from new customers
Informing audience observation and campaign analysis
Supporting new-customer acquisition strategies
Examples could include:
Previous customers who have not purchased recently
Customers with a high lifetime value
Subscribers who have not yet become customers
Existing customers to exclude from introductory offers
Customers associated with a particular product or service category
Customer Match should not be treated as permission to upload any available contact database. Google requires data to have been collected in a first-party context and imposes policy, consent, privacy and account-eligibility requirements. The business must also ensure that its privacy disclosures, consent handling and data use comply with applicable law and Google policy.
What Data Sources Can Connect to Data Manager?
Google supports direct connections with a growing range of systems. At the time of writing, the official supported-source directory includes categories such as:
CRM and marketing platforms, including HubSpot, Salesforce, ActiveCampaign and Zoho CRM
Databases and data warehouses, including BigQuery, MySQL, PostgreSQL, Oracle, Snowflake and Amazon Redshift
Cloud and file storage, including Google Cloud Storage, Google Drive and Amazon S3
Structured file routes, including Google Sheets, HTTPS and SFTP
Commerce platforms such as Shopify for supported use cases
Support varies by source and destination. A connector that supports Customer Match does not necessarily support conversion imports in the same way, and some platforms have source-specific field, object, permission or subscription requirements.
The list also changes over time. Before designing an implementation, confirm the required source and destination in Google’s current supported-source directory rather than assuming that every system shown in Data Manager supports every use case.
If a CRM is not offered as a direct connector, possible routes may include:
The CRM’s native Google Ads integration
A supported database or cloud-storage source
A controlled Google Sheets, HTTPS or SFTP feed
An approved integration partner
The Data Manager API
Another suitable server-side integration
The best route is normally the most direct, reliable connection that meets the business requirement. Adding extra automation platforms or data hops without a clear reason creates more credentials, mappings, and failure points to maintain.
Data Manager and HighLevel
HighLevel is not currently listed in Google’s direct Data Manager source directory. That does not mean HighLevel data cannot be used with Google Ads; it means the correct route should be selected based on the account’s requirements and the features available in HighLevel.
Where HighLevel offers a suitable native Google Ads measurement or CRM integration, that should usually be assessed first. If the required lifecycle events, identifiers or values cannot be sent through the native route, a controlled file, database, API or integration workflow may be considered.
The objective is not to use Data Manager simply because it exists. The objective is to create a dependable feedback loop between the advertising click, the contact record, the sales outcome and Google Ads.
Data Manager and HubSpot
HubSpot is available as a direct Data Manager source for supported conversion and Customer Match use cases. This can make it possible to select CRM data, apply lifecycle-stage conditions, map the required fields and associate the connection with a conversion action or audience.
However, a connector does not repair an inconsistent CRM.
Before sending HubSpot data to Google Ads, the business should still define:
What qualifies a lead
Which lifecycle stage represents a genuine sales opportunity
When a customer conversion should be recorded
Which date represents the conversion time
Where conversion value is stored
How duplicate records are handled
Whether the original advertising identifiers and first-party data are retained
Who owns ongoing data-quality monitoring
Our Google Ads CRM integration guide explains the broader CRM design considerations beyond the connection itself.
How Google Ads Data Manager Works
A Data Manager implementation normally contains six components.
1. The Source System
This is where the original data is stored. It may be a CRM, database, warehouse, ecommerce platform or structured file.
The source should be treated as the system of record. For lead generation, CRM fields and lifecycle stages should define the outcome. A connection should not rely on loosely managed tags or free-text notes when a stable field can provide a more reliable value.
2. The Selected Data
The connection does not need to send every record or every field. The source can provide a dedicated table, selected object, report or filtered subset.
For example, a single CRM dataset could contain several lifecycle stages, while separate filtered connections import:
Records where lifecycle stage equals Qualified Lead
Records where lifecycle stage equals Sales Opportunity
Records where lifecycle stage equals Customer
Google requires a separate connection for each audience or conversion event, although the same underlying table or file can be reused with different filters.
3. Field Mapping
Source fields must be mapped to the destination fields expected by Google Ads.
Depending on the use case, these may include:
Conversion action
Conversion date and time
Conversion value
Currency
Order or transaction ID
GCLID
GBRAID or WBRAID
Email address
Telephone number
Event source
Correct mapping is essential. A connection can technically run while still producing weak results if the wrong date, value, lifecycle field or identifier is selected.
4. Data Transformation
Data Manager can apply transformations before import. These can help standardise and prepare source values without requiring every change to be made in the original system.
Available transformations can include actions such as:
Normalising and hashing customer information
Converting date and time values
Changing text case
Combining or splitting fields
Replacing values
Multiplying numerical fields
Not every transformation is available for every source. Complex commercial logic should generally be calculated in the source system where it can be tested, documented and reused, rather than hidden inside an advertising connection.
5. Filters
Filters determine which rows become an audience member or conversion event.
Examples include:
Lifecycle stage = Qualified LeadOpportunity status = Closed WonCustomer consent = TrueRevenue > 0Service type = Boiler Installation
Filters make it possible to reuse a structured source for multiple destinations. They also reduce the need to build separate data pipelines for relatively simple segmentation rules.
6. The Destination and Schedule
The final connection is associated with a conversion action or audience segment. Data Manager can then import updated source data on a schedule supported by that connection.
Google supports daily scheduled imports for Data Manager connections. The source must be refreshed before the scheduled run; Data Manager cannot import information that has not yet been written to the connected source.
Audience refresh options and source-specific behaviour can vary, so the operating schedule should be checked for the selected connection.
Data Required for Enhanced Conversions for Leads
A strong enhanced-conversions-for-leads implementation should preserve as much accurate matching information as reasonably available.
Typical fields include:
Conversion name or a field used to filter the conversion event
Conversion date and time with an unambiguous timezone
Email address and/or telephone number
GCLID where available
GBRAID or WBRAID where relevant
Conversion value and currency where appropriate
Order or transaction ID where appropriate
Event source, such as web, telephone, app or in-store
Google recommends importing available GCLIDs alongside first-party customer data where possible. The sources complement each other: click identifiers provide direct advertising linkage, while properly handled first-party data can improve matching durability and support attribution in cases that identifiers alone may not cover.
For UK advertisers, telephone numbers should use the international E.164 format, such as +442012345678, without spaces, brackets or dashes.
Dates should be unambiguous and include the correct timezone. An ISO 8601 value such as 2026-08-10T14:30:00+01:00 is safer than a date such as 10/08/2026, which may be interpreted differently by systems expecting a US date format.
Hashing, Privacy and Confidential Matching
Email addresses, telephone numbers and other private customer identifiers must be handled correctly.
Data Manager can normalise relevant personally identifiable information and hash it using SHA-256 before it is sent for the supported use case. Advertisers can also prepare properly normalised and hashed data themselves where required by their architecture.
Hashing is not a substitute for consent, lawful processing or appropriate governance. The advertiser remains responsible for ensuring that the data was collected and shared legitimately, that privacy information is accurate and that applicable Google policies are followed.
For direct Customer Match connections, Google says confidential matching is enabled automatically at no additional cost. It processes matching within a trusted execution environment and removes identifiers that are not needed after matching. Optional encryption controls are also available for organisations with more advanced security requirements.
This improves the technical processing model, but it does not change the advertiser’s obligations under UK data-protection law, Google’s EU User Consent Policy or Customer Match policies.
Data Manager Versus Google Tag Manager
The similar names can confuse, but Data Manager and Google Tag Manager perform different jobs.
Google Tag Manager controls tags and events on a website or app. It can deploy Google Ads conversion tags, capture form data for enhanced conversions and send online interaction data.
Google Ads Data Manager connects external first-party data sources with Google Ads. It is particularly relevant when data already exists in a CRM, database, cloud platform or file.
The two often work together:
Google Tag Manager records the original lead → CRM stores the sales outcome → Data Manager returns the later outcome to Google Ads
Data Manager therefore complements website tagging; it does not replace it.
Data Manager Versus Google Analytics
Google Analytics measures behaviour across websites and apps. It helps explain how users arrived, what content they viewed and which events occurred during their digital journey.
Data Manager is designed to connect and activate external data for supported Google advertising use cases.
GA4 may tell you that a user submitted a form. The CRM may later tell you that the lead became a £12,000 customer. Data Manager can help return that later outcome to Google Ads.
Google Analytics, Google Ads conversion tracking and CRM conversion imports should therefore be designed as parts of one measurement architecture rather than treated as interchangeable tools.
Data Manager Versus a CRM or Customer Data Platform
Data Manager is not where a sales team manages contacts, records calls, sends quotations or maintains an opportunity pipeline. That remains the role of the CRM.
It is also not a complete customer data platform. It does not replace enterprise identity resolution, multi-channel activation, consent orchestration or data-warehouse modelling.
Data Manager is better understood as a connection and activation layer for Google advertising. Its purpose is to move selected, correctly governed data from an existing source into an appropriate Google Ads destination.
A Recommended Lead-Generation Measurement Structure
For many service businesses, a useful structure is:
Website Lead – the initial form, call or booking recorded through website conversion tracking.
Qualified Lead – a genuine prospect who meets the business’s qualification criteria.
Sales Opportunity – a qualified prospect that has progressed into an active commercial process.
Customer – a completed sale, accepted quotation, signed agreement or paid first invoice.
Revenue – the actual or agreed value produced by the customer.
Not every stage should automatically become a primary bidding goal.
Website leads may provide the volume needed for campaign learning, while deeper-funnel outcomes provide quality information. Once the deeper events are accurate and frequent enough, the account can assess whether bidding should optimise towards Qualified Leads, customers or conversion value.
This is a measurement and bidding decision, not simply a technical connection choice. Read our guide to primary and secondary Google Ads conversions before changing campaign optimisation goals.
How to Set Up Google Ads Data Manager
The precise setup varies by source, but the general process is consistent.
Step 1: Define the Business Outcome
Begin with the commercial event you want to measure or the customer segment you want to activate.
Avoid starting with the connector. “Connect the CRM to Google Ads” is not a sufficiently precise requirement.
A better requirement is:
Import a Qualified Lead conversion when a contact meets our qualification criteria, using the time the lead was qualified and the original GCLID plus available first-party customer data.
Step 2: Audit the Source Data
Confirm that the required fields are present, populated consistently and retained for long enough.
Check:
Advertising identifiers
Email and telephone formatting
Conversion-stage definitions
Conversion timestamps
Timezones
Currency and values
Consent status
Duplicate records
Test contacts
Internal or spam enquiries
If the source data is unreliable, automating the import will only automate unreliable measurement.
Step 3: Create the Conversion Action or Audience
For conversions, select the category that accurately represents the event. Google commonly recommends Qualified Lead or Converted Lead for enhanced conversions for leads.
Configure the action’s value, attribution, counting and primary or secondary status according to its business role.
For Customer Match, define the audience purpose and ensure the selected customers are eligible for that use.
Step 4: Connect the Data Source
In Google Ads, open Tools → Data Manager and select the required product or source.
Choose the direct connection where supported, authorise the source and select the appropriate data location, object, file or table.
Google Ads administrator access is generally required, along with the necessary permissions in the source system.
Step 5: Filter and Map the Data
Select only the records needed for the conversion or audience. Map every required field carefully and add transformations where appropriate.
Pay particular attention to conversion time, identifiers, values and the field used to determine the lifecycle event.
Step 6: Set the Refresh Schedule
Choose a schedule appropriate to the source and use case. Make sure the source refresh completes before Data Manager attempts to import it.
Daily imports may be sufficient for many lead-generation businesses. A business that requires faster bidding feedback may need to assess an API or more immediate native integration instead.
Step 7: Test Before Using the Data for Bidding
Run controlled test records through the complete journey.
Confirm that:
The source record meets the intended filter
The correct conversion action receives the event
The conversion time reflects the actual outcome
The value and currency are correct
Duplicate events are prevented
Test records can be identified and excluded
Diagnostics show successful imports
Do not immediately switch bidding to a new imported conversion action before its accuracy, volume and latency have been assessed.
Common Google Ads Data Manager Mistakes
Connecting Data Before Defining the Strategy
A functioning connector is not the same as a functioning measurement system. Decide which decisions the data will support before building the import.
Importing Every CRM Stage
Sending every minor stage creates clutter and can make goal configuration difficult. Import events that represent meaningful changes in commercial value.
Using Inconsistent Lifecycle Definitions
If one salesperson marks almost every enquiry as qualified while another uses a strict definition, the imported signal will be inconsistent.
Optimising for Rare Outcomes Too Early
A business may prefer to optimise for customers, but a campaign generating only a handful of customer conversions may not provide enough regular feedback. Qualified Leads or Sales Opportunities may offer a better balance between quality and volume until more data is available.
Losing the Original Click Identifier
GCLID, GBRAID and WBRAID values should be captured and retained where applicable. They should not be discarded merely because first-party customer data is also available.
Incorrect Conversion Times
The import should use the time the selected event actually happened—not the time the file was created or the connection ran.
Ambiguous UK Date Formats
Values such as 05/06/2026 can be interpreted as 5 June or 6 May. Use an unambiguous timestamp with a timezone.
Sending Revenue Without a Clear Definition
Decide whether value represents gross revenue, net revenue, first payment, expected contract value or another metric. Mixing definitions makes ROAS unreliable.
Ignoring Consent and Suppression Logic
Customer Match connections should include the appropriate consent and eligibility rules. Suppression, deletion and refresh processes need to be operational, not merely documented.
Assuming a Successful Run Means Accurate Data
A technically successful import can still contain the wrong records, stage, time or value. Reconcile imported counts and values with the source system.
Monitoring and Troubleshooting
Data Manager provides connection statuses and diagnostics that can help identify failed authorisation, inaccessible sources, schema changes, invalid formats, missing fields and row-level import problems.
The map view can also make supported conversion connections easier to trace from the source through the connection to the destination.
A practical monitoring routine should include:
Connection status
Last successful refresh
Source record count
Rows accepted and rejected
Match or import diagnostics
Conversion volume by action
Delay between CRM outcome and Google Ads import
Imported value compared with CRM revenue
Unexpected increases or decreases
Duplicate conversion checks
Review diagnostics after the first import, after any CRM or schema change and at regular intervals thereafter.
The CRM, Data Manager and Google Ads figures will not always match immediately because of processing delays, attribution rules, date definitions and unmatched records. The aim is not blind numerical equality; it is a documented and explainable reconciliation.
When Data Manager Is the Right Choice
Data Manager is particularly useful when:
The source has a supported direct connector
Daily scheduled refreshes meet the business requirement
A point-and-click setup is preferable to custom development
The required filtering and transformations are relatively straightforward
The business wants central visibility of Google Ads data connections
First-party data needs to support conversions or Customer Match
It may be less suitable as the only solution when:
Near-real-time event delivery is essential
The business requires complex multi-system logic
The source is not supported and no controlled file or database route exists
Conversion events require advanced deduplication or reconciliation
The business needs activation across several advertising platforms, not only Google
A native CRM connection already provides the required outcome more directly
In these cases, a native integration, the Data Manager API, a server-side process or a carefully designed automation workflow may be more appropriate.
How Data Manager Supports Better Bidding
Data Manager does not improve campaign performance merely by being connected. Its value depends on the quality and suitability of the signal it supplies.
The progression is usually:
More complete measurement → Better understanding of lead quality and value → Better goal selection → Better-informed automated bidding
For example, two campaigns may each generate 100 enquiries at £50 per lead. At first, they appear equal.
After CRM outcomes are imported:
Campaign A produces 25 Qualified Leads and 10 customers.
Campaign B produces 10 Qualified Leads and 2 customers.
Lead volume alone concealed a major commercial difference.
Once sufficient reliable data exists, Google Ads may be able to optimise towards the actions and values more closely associated with profitable growth. This can support strategies such as Maximise Conversions, Target CPA, Maximise Conversion Value or Target ROAS, depending on the account’s economics and conversion volume.
Read our guide to Maximise Conversion Value and Target ROAS before moving from lead-based bidding to value-based optimisation.
Google Ads Data Manager Implementation Checklist
Before launch, confirm that:
The business outcome is clearly defined.
The CRM or source system is the agreed source of truth.
Lifecycle stages have written definitions.
Required identifiers are captured and retained.
Email addresses and telephone numbers are consistently formatted.
Conversion timestamps are unambiguous and include a timezone.
Conversion values have one documented commercial definition.
Consent and privacy requirements have been reviewed.
The selected source supports the intended destination.
Source and Google Ads access permissions are in place.
Filters exclude spam, tests and ineligible records.
Field mappings have been reviewed.
Duplicate events are prevented.
The source refresh completes before the scheduled import.
Test records have passed through the complete workflow.
Diagnostics and reconciliation have an owner.
Bidding will not use the new action until data quality and volume are sufficient.
Summary
Google Ads Data Manager provides a central way to connect first-party customer data with Google Ads.
Its most important uses are importing later conversion outcomes and maintaining Customer Match audiences. For lead-generation businesses, it can help connect the original advert click with CRM stages such as Qualified Lead, Sales Opportunity, Customer and Revenue. For ecommerce and retail businesses, it can help activate customer and transaction data stored beyond the original website purchase event.
The platform simplifies connections, field mapping, transformations, filters, scheduling and diagnostics. However, it does not replace website tagging, CRM design, consent management or commercial measurement strategy.
The strongest implementation begins with a clearly defined business outcome, reliable source data and a documented conversion architecture. Data Manager then becomes the connection layer that carries those outcomes back into Google Ads.
When implemented correctly, the result is not simply more data. It is better feedback: feedback that helps advertisers distinguish cheap leads from valuable prospects, connect campaign investment with customers and revenue, and make smarter decisions about where advertising budget should be allocated.
Next Actions
Do you want to connect Google Ads with your CRM, sales pipeline and revenue data?
One PPC can audit your current conversion tracking, review your CRM data structure and design a suitable implementation using native integrations, Google Ads Data Manager, enhanced conversions for leads or another appropriate connection method.
Contact One PPC to arrange a Google Ads tracking and CRM integration review.
Frequently Asked Questions
Is Google Ads Data Manager Free?
Google does not charge a separate Data Manager platform fee within Google Ads. However, the connected CRM, database, integration partner, cloud platform or implementation work may have its own costs.
Does Data Manager Replace Google Tag Manager?
No. Google Tag Manager deploys and controls website or app tags. Data Manager connects external first-party sources such as CRMs, databases and files with Google Ads. They can form different parts of the same measurement system.
Does Data Manager Replace Offline Conversion Tracking?
No. Data Manager is one method of importing offline or later-stage conversion data. The conversion use case remains offline conversion measurement or, preferably where suitable, enhanced conversions for leads.
Should I Use Enhanced Conversions for Leads or Legacy Offline Conversion Import?
Google recommends enhanced conversions for leads for suitable lead-generation implementations because it can use first-party customer data alongside click identifiers and offers more durable matching and attribution capabilities than legacy offline conversion import.
Can Data Manager Import Revenue?
Yes, supported conversion connections can include conversion values. The source must store a reliable value, and the business should define exactly what the imported value represents.
Can I Connect Google Sheets to Google Ads Data Manager?
Yes. Google Sheets is a supported source for applicable conversion and Customer Match uses. Structured data needs headers and appropriate formatting, and the Sheet must be refreshed before a scheduled import runs.
Does Data Manager Work With HubSpot?
Yes. HubSpot is available as a direct source for supported conversion and Customer Match use cases. The account must still have suitable CRM fields, lifecycle definitions, permissions and data quality.
Does Data Manager Work With HighLevel?
HighLevel is not currently shown in Google’s direct Data Manager source directory. Assess HighLevel’s native Google Ads features first, then consider a supported file, database, API or integration route if the native connection does not meet the requirement.
How Often Does Data Manager Refresh Data?
Google supports daily scheduled imports, while some audience connections may offer other refresh options. The exact behaviour depends on the source and use case. The source itself must be updated before the connection runs.
Is Customer Data Automatically Hashed?
Data Manager can normalise and hash relevant private customer data using SHA-256. Advertisers remain responsible for consent, lawful processing, privacy disclosures and compliance with Google’s policies.
What Is the Biggest Risk With Data Manager?
The greatest risk is not usually the connector failing. It is successfully importing the wrong business definition—for example, inconsistent Qualified Leads, inaccurate revenue, duplicate customers or incorrect timestamps. Source-data governance is as important as the technical setup.