CRM Tracking for Google Ads

Generating a form submission or telephone call is only the beginning of the sales process. The lead may later book an appointment, receive a quote, become qualified, enter a sales opportunity or eventually turn into a paying customer.

Google Ads does not automatically know when these later outcomes occur. Without CRM integration, it may optimise campaigns around the people most likely to submit a form rather than those most likely to become profitable customers.

Integrating Google Ads with a customer relationship management system closes this information gap. It connects advertising activity with sales outcomes, allowing businesses to measure lead quality, revenue and return on advertising spend more accurately.

More importantly, it gives Google Ads stronger data for campaign optimisation.

What Does a Google Ads CRM Integration Do?

A Google Ads CRM integration creates a feedback loop between advertising, lead management and sales.

When somebody clicks an advert, Google can generate identifiers and attribution data connected to that interaction. These values are captured by the website and stored against the resulting contact in the CRM.

As the contact progresses through the sales process, the CRM records important milestones such as:

• Lead created

• Appointment booked

• Marketing-qualified lead

• Sales-qualified lead

• Quote issued

• Opportunity created

• Deal won

• Revenue collected

Selected events can then be returned to Google Ads as conversions.

The result is a continuous measurement cycle:

Google Ads click → website enquiry → CRM contact → sales qualification → customer or revenue → Google Ads conversion

Instead of evaluating advertising solely by cost per enquiry, the business can calculate cost per qualified lead, cost per customer, conversion rate and actual return on advertising spend.

Why Basic Lead Tracking Is Often Insufficient

Website conversion tracking normally records the immediate action completed by a visitor. This might be a submitted contact form, a telephone-button click or an online booking.

These actions are useful, but they do not necessarily represent commercial value.

Consider two campaigns:

Metric	Campaign A	Campaign B
Advertising cost	£5,000	£5,000
Enquiries	100	60
Cost per enquiry	£50	£83
Qualified leads	15	30
Customers	3	10
Revenue	£9,000	£30,000

If performance is judged by cost per enquiry, Campaign A appears more efficient. However, Campaign B generates twice as many qualified leads, more than three times as many customers and considerably more revenue.

Without CRM data, an advertiser may reduce Campaign B’s budget and allocate more money to the campaign producing lower-quality enquiries.

CRM integration changes the optimisation target from:

Which clicks generate the most form submissions?

to:

Which clicks generate qualified opportunities, customers and revenue?

That is a much more commercially useful question.

The Data That Should Be Stored in the CRM

A dependable integration starts with the right CRM data model. Important attribution values should normally be stored in dedicated contact or lead fields rather than relying entirely on tags.

Fields act as the source of truth. Tags can still be useful for segmentation, workflow enrolment and temporary states, but they are less suitable for holding structured attribution data.

A practical set of CRM fields may include:

CRM field	Purpose
First UTM source	Original source that introduced the contact
First UTM medium	Original marketing medium
First UTM campaign	Original campaign
First landing page	Initial page visited
Latest UTM source	Most recent known source
Latest UTM medium	Most recent marketing medium
Latest UTM campaign	Most recent campaign
Latest landing page	Most recent tracked landing page
GCLID	Google Click ID
GBRAID	Privacy-preserving identifier associated with certain iOS app activity
WBRAID	Privacy-preserving identifier associated with certain iOS web activity
Lead creation date	When the CRM record was created
Qualification date	When the lead became qualified
Opportunity date	When a genuine sales opportunity was created
Customer date	When the deal was completed
Opportunity value	Expected commercial value
Revenue	Confirmed customer value
Conversion event ID	Unique reference used to prevent duplicate imports
Consent status	The applicable data-sharing consent status

The CRM should retain both original and latest attribution where possible. Overwriting the first-touch values every time a contact returns to the website destroys useful acquisition information.

GCLID, GBRAID and WBRAID

When Google Ads auto-tagging is enabled, a Google Click ID—known as a GCLID—can be appended to the landing-page URL.

For example:

https://example.co.uk/service/?gclid=example123

The website can capture this value and store it with the lead. When a later CRM event is uploaded, Google uses the identifier to associate the conversion with the original advertising interaction.

The GCLID is case-sensitive and should be stored without changing its format.

Not every attributable interaction will contain a conventional GCLID. Google also supports:

• GBRAID: associated with certain app-related conversions originating from iOS devices.

• WBRAID: associated with certain web conversions originating from iOS devices.

These identifiers should be captured and preserved when present. An implementation should not assume that every Google Ads visitor will always provide a GCLID.

Google’s current Data Manager specification supports GCLID, GBRAID and WBRAID alongside user-provided identifiers and other event information. See Google’s Data Manager field requirements.

Enhanced Conversions for Leads

Google now recommends Enhanced Conversions for Leads for new lead-generation implementations.

This extends traditional offline conversion tracking by using consented, first-party customer information—such as an email address or telephone number—to help match a CRM event with the earlier advertising interaction.

The data is normalised and hashed using SHA-256 before being sent to Google. Hashing converts the information into a standardised, non-readable value for matching.

Enhanced Conversions for Leads can use information such as:

• Email address

• Telephone number

• First and last name

• Address information

• Google click identifiers

• A unique transaction or event ID

• Conversion date and time

• Conversion value and currency

• Consent status

Google states that this approach can provide more durable measurement, improved matching, cross-device conversions and engaged-view conversion reporting compared with traditional click-ID-only imports. Read Google’s Enhanced Conversions for Leads overview.

Click identifiers should still be captured whenever possible. Google recommends continuing to include existing GCLIDs because they help associate conversions with specific advert clicks.

Enhanced Conversions for Leads vs Traditional Offline Imports

The two methods are related, but they are not identical.

Method	Principal matching data	Main consideration
Traditional offline conversion import	GCLID, GBRAID or WBRAID	Depends heavily on capturing and retaining the click identifier
Enhanced Conversions for Leads	Hashed customer data, supported by click identifiers where available	More durable matching and currently recommended by Google
Direct website conversion tracking	Browser or server-side event recorded at the point of conversion	Usually measures the initial online action rather than later CRM outcomes

A strong implementation will frequently use both website tracking and CRM-based conversion events.

The website tag records the original lead. The CRM then returns later milestones such as qualification, opportunity creation or completed sale.

As of 2026, Google is moving offline and Enhanced Conversions for Leads uploads towards its Data Manager infrastructure. Businesses implementing a new connection should therefore use Google Ads Data Manager, a supported native CRM connection or a current integration designed around the Data Manager API rather than building against a legacy upload process. Review Google’s current offline conversion guidance.

Choosing Which CRM Events to Send to Google Ads

Not every CRM status should become a Google Ads conversion.

An internal task, an automated email, an attempted telephone call or a minor pipeline update does not necessarily represent additional commercial intent. Sending too many weak or overlapping events can make reporting confusing and give automated bidding the wrong objectives.

A clearer conversion structure might look like this:

CRM event	Recommended treatment	Possible value
Form submitted	Primary initially or secondary later	Low
Telephone-button click	Secondary	Very low
Connected telephone enquiry	Secondary or primary where reliable	Low
Appointment booked	Primary where commercially significant	Medium
Qualified lead	Primary	Expected lead value
Opportunity created	Primary for longer sales cycles	Expected opportunity value
Customer acquired	Primary	Actual revenue or profit-based value
Repeat purchase	Separate conversion where appropriate	Actual transaction value

Google provides dedicated Qualified lead and Converted lead goal types. These are intended to connect advertising with later CRM outcomes and support Google Ads’ lead-funnel reporting. See Google’s qualified and converted lead guidance.

The best optimisation event is generally the deepest reliable stage that occurs frequently enough and quickly enough to influence bidding.

For example, optimising for completed sales may be theoretically ideal. However, if a business generates only five sales per month and takes 90 days to close each deal, the signal may be too sparse and delayed for dependable campaign-level bidding.

In that situation, a consistently defined qualified lead or sales opportunity may provide a more useful optimisation signal.

Google’s current lead-generation guidance recommends at least 15 conversions in the previous 30 days at account level and advises uploading offline data regularly, ideally every day. In practice, higher and more consistent volumes usually provide a more stable signal. Review Google’s lead-quality best practices.

Primary and Secondary Conversion Actions

Google Ads separates conversion actions into primary and secondary actions.

Primary conversion actions appear in the main Conversions column and can be used by automated bidding. Secondary actions remain available for analysis in the All conversions column but do not normally control bidding.

This distinction is important.

A mature lead-generation account might use:

• Qualified lead as a primary conversion

• Converted customer as a primary conversion

• Initial form submission as a secondary conversion

• Telephone-button click as a secondary conversion

• Email-button click as a secondary conversion

This prevents Google from treating a weak micro-conversion as if it had the same importance as a genuine sales outcome.

When introducing a new CRM conversion action, initially setting it as secondary allows the advertiser to test volume, matching, duplication and values without immediately changing bidding behaviour. Google’s implementation checklist recommends validating a new Enhanced Conversions for Leads action before making it primary. See the implementation checklist.

Assigning Values to Leads and Opportunities

Sending conversion values allows Google Ads to distinguish between outcomes of different commercial importance.

For a completed sale, the business may send actual transaction revenue or, preferably where available, a value aligned with gross profit or contribution margin.

For qualified leads, an expected value can be calculated:

Expected lead value = Lead-to-customer rate × Average customer value

If 20% of qualified leads become customers and the average customer is worth £2,000, the estimated qualified-lead value would be:

0.20 × £2,000 = £400

This is more defensible than assigning arbitrary values such as £10 to a form submission and £100 to a qualified lead.

For businesses with different services, locations or customer types, values can be calculated at a more granular level:

Lead type	Close rate	Average customer value	Expected lead value
Residential service	25%	£800	£200
Commercial service	10%	£8,000	£800
Maintenance contract	35%	£2,400	£840

Once sufficient conversion value data exists, the advertiser may consider value-based bidding. However, values must be accurate and consistently applied. Poorly designed values can be more damaging than using no values at all.

CRM Integration Methods

The best connection method depends on the CRM, sales process and available technical resources.

Native CRM Integration

Some CRM systems can connect directly through Google Ads Data Manager. Supported sources and capabilities vary, but Google provides direct guidance for platforms including HubSpot, Salesforce and Zoho.

A native connection is usually preferable when it supports the required fields, events and update frequency. It reduces the number of systems involved and normally requires less maintenance.

Google Ads Data Manager

Data Manager provides a central interface for bringing first-party business data into Google Ads.

It supports several types of data source, including CRM platforms, databases, cloud storage, spreadsheets and HTTP or SFTP sources. Businesses can map source fields to conversion properties and configure recurring imports.

This is now the strategic route for many offline conversion and Enhanced Conversions for Leads implementations. View Google Ads Data Manager.

CRM API or Data Manager API

A custom API integration provides more control over event timing, consent values, conversion adjustments, error handling and field mapping.

It is suitable when:

• The CRM has no suitable direct connection

• Several systems contribute to the sales journey

• Events need to be sent in near real time

• Conversion values can change

• Failed uploads require automated retries

• The organisation has sufficient technical resources to maintain the integration

Each conversion should include a unique event or transaction ID wherever supported. This helps prevent accidental duplication and allows an existing conversion to be adjusted or retracted.

Scheduled File Import

A CRM report can be exported to a spreadsheet or CSV file and imported on a schedule.

This can work for smaller organisations, but it introduces several risks:

• Delayed conversion uploads

• Manual formatting errors

• Duplicate records

• Incorrect date or timezone formats

• Missing click identifiers

• Inconsistent field names

• Limited monitoring of rejected records

A scheduled, automated connection is generally more dependable than repeated manual uploads.

A Recommended Integration Architecture

A robust implementation normally has five connected layers.

1. Website Tracking

The website records the original enquiry and captures available attribution data.

This may include:

• UTM parameters

• GCLID, GBRAID and WBRAID

• Landing-page URL

• Referring URL

• Form identifier

• Telephone tracking information

• User-provided data, where consent and policy requirements are satisfied

The tracking must be tested across redirects, cookie-consent states, embedded forms, appointment calendars and multi-page journeys.

2. CRM Storage

The captured values are written to dedicated CRM fields.

The system should preserve first-touch attribution while separately recording the latest known source. Where the CRM uses separate contact, company and opportunity records, relevant attribution fields may need to be associated or copied between objects.

3. Sales-Stage Governance

Each conversion-worthy stage needs a precise definition.

For example, a qualified lead might require:

• A genuine service requirement

• A valid service location

• Suitable budget or commercial fit

• Verified contact information

• No duplicate or spam record

• Confirmation that the business can provide the requested service

If individual salespeople apply different definitions, the data sent to Google will be inconsistent.

4. Event Workflow

A CRM workflow identifies when a record reaches the relevant milestone.

The workflow should:

• Confirm that required matching data exists

• Record the conversion date and time

• Calculate or retrieve the conversion value

• Generate a unique event ID

• Confirm consent status

• Prevent the same event from being sent twice

• Send the event through the selected integration

• Record whether the upload succeeded or failed

5. Google Ads Optimisation

After validation, selected CRM events can become primary conversion actions.

Campaigns can then be evaluated using commercially meaningful metrics such as:

• Cost per qualified lead

• Lead-to-opportunity rate

• Cost per opportunity

• Customer acquisition cost

• Lead-to-customer rate

• Revenue by campaign

• Return on advertising spend

• Gross profit return on advertising spend

Common Integration Problems

CRM integrations often fail because of data handling rather than the connection itself.

The Click ID Is Not Stored

The GCLID appears in the landing-page URL but is lost before the form is submitted. This commonly occurs when there are redirects, cross-domain journeys, embedded forms or appointment systems that do not retain the original parameters.

Attribution Fields Are Overwritten

A returning direct or organic visit replaces the original Google Ads source. The CRM can no longer identify how the contact was initially acquired.

First-touch and latest-touch attribution should be stored separately.

The Conversion Time Is Incorrect

The integration sends the time of the original enquiry rather than the time the lead became qualified or the sale occurred.

Every conversion event should use the time at which that specific business outcome happened.

Weak Events Are Used for Bidding

Telephone-button clicks, page views and unverified enquiries are included as primary conversions alongside qualified leads.

Automated bidding then has an incentive to generate whichever action is easiest rather than the outcome with the greatest commercial value.

Duplicate Conversions Are Uploaded

A workflow runs repeatedly whenever an opportunity record is updated, sending the same qualified-lead event multiple times.

Unique event IDs and workflow safeguards are essential.

Sales Teams Do Not Maintain the CRM

Offline conversion tracking is only as reliable as the underlying CRM. If opportunities are not updated, lost deals remain open or revenue is missing, the feedback returned to Google Ads will be incomplete.

Values Are Arbitrary

Values are selected to influence bidding without being connected to close rates, revenue or profit. This distorts reporting and can cause budgets to move towards the wrong lead types.

Consent Is Ignored

Enhanced conversion data must be handled in accordance with applicable privacy requirements and Google’s customer-data policies. The integration should retain the appropriate consent status and avoid transmitting unnecessary information.

Google states that IP-address matching is not supported for end users in the UK, EEA or Switzerland. UK implementations should therefore not treat IP addresses as a dependable user-matching field.

Measuring Whether the Integration Is Working

A technically successful upload does not automatically mean the overall system is accurate.

The implementation should be reconciled across four levels:

1. Website: How many valid leads were submitted?

2. CRM: How many contacts, qualified leads and customers were recorded?

3. Integration: How many events were accepted, rejected, delayed or duplicated?

4. Google Ads: How many conversions were attributed and included in reporting?

The numbers will not always match exactly. Consent choices, attribution windows, cross-device behaviour, identifier availability and processing delays can create legitimate differences.

However, large or unexplained discrepancies should be investigated.

Google notes that most imported conversions process within several hours, although GBRAID- and WBRAID-keyed conversions can take up to 72 hours. See Google’s troubleshooting guidance.

Useful quality checks include:

• Percentage of paid leads containing a usable identifier

• Match rate for uploaded CRM events

• Number of rejected events

• Duplicate-event rate

• Average delay between the CRM event and upload

• Percentage of leads with complete qualification data

• CRM revenue compared with imported conversion value

• Qualified-lead and customer volumes by campaign

Google Ads CRM Integration Checklist

Before using CRM data for campaign bidding, confirm that:

• Google Ads auto-tagging is enabled

• The website captures GCLID, GBRAID and WBRAID where present

• Click identifiers retain their original case and format

• First-touch and latest-touch attribution use separate CRM fields

• Email addresses and telephone numbers are normalised correctly

• User-provided information is hashed where required

• Consent status is collected and transmitted appropriately

• Qualification criteria are documented

• Conversion events use the correct date and time

• Each event has a unique identifier

• Duplicate events are prevented

• Conversion values reflect expected or actual commercial value

• Failed uploads are visible and retried safely

• New conversion actions are tested as secondary

• CRM and Google Ads totals are reconciled

• Only stable, commercially meaningful events are activated for bidding

Turning Advertising Data into Revenue Data

Integrating Google Ads with a CRM is not simply a tracking improvement. It changes the way advertising performance is measured and optimised.

Basic website tracking tells a business which campaigns produce enquiries. CRM integration reveals which campaigns produce qualified opportunities, customers and revenue.

That distinction is particularly important for service businesses, B2B organisations and companies where a sale happens after a telephone call, appointment, quotation or longer sales process.

The most effective implementation does not send every CRM action back to Google. It captures reliable attribution, defines meaningful sales stages, assigns defensible values and returns the strongest available commercial signals.

When the CRM accurately reflects how the business makes money, Google Ads can be optimised around the same objective.