The problem is often the feedback loop
A B2B service business can generate enquiries from Google Ads without generating worthwhile opportunities. The dashboard shows conversions, the reported cost per lead looks acceptable, and the sales team says most enquiries are unsuitable.
Both views can be correct.
Google Ads optimises towards the conversion signals supplied to it. If those signals are form submissions, telephone-link clicks or booking-page visits, the campaign may learn to generate more of those actions rather than more qualified buyers.
Tracking will not rescue an uncompetitive offer or irrelevant targeting. However, without a reliable connection between advertising and sales outcomes, it is difficult to identify which problem needs fixing.
Why service campaigns lose commercial relevance
Search intent is mixed
Service searches often combine buyers with jobseekers, students, suppliers and people looking for free advice. Broad terms can also attract businesses whose requirements are outside your delivery model.
Review actual search terms, not just the keywords configured in the account. Separate materially different services and buying intentions. Use negative keywords to exclude clearly irrelevant demand, without blocking legitimate research by potential customers.
Landing pages should explain scope, suitability and delivery constraints. A specialist integration consultancy should not present itself as an unlimited source of general IT support.
Every enquiry receives the same value
A generic contact form may collect support requests, recruitment enquiries and potential contracts. Treating every submission as an equally valuable conversion gives bidding systems a distorted target.
The same problem occurs when a campaign counts all of these as primary conversions:
- A visitor clicks a telephone number.
- They submit an enquiry.
- They book a meeting.
- Sales later qualifies the opportunity.
These are stages of one journey, not necessarily four independent commercial outcomes.
Sales outcomes arrive late
B2B buying cycles commonly extend beyond the initial enquiry. If sales updates remain in a spreadsheet or CRM that never feeds back into advertising, the campaign cannot distinguish promising demand from noise.
The fix is a measurement architecture, not simply another tag.
Define the conversion model before implementing tags
Agree a small set of lifecycle events with sales and marketing:
| Event | Meaning | Typical use | |---|---|---| | Enquiry accepted | A valid submission reaches the backend | Early funnel measurement | | Qualified lead | Sales confirms fit against agreed criteria | Potential bidding signal | | Opportunity created | An active buying process is recorded | Downstream quality measurement | | Contract won | A deal is confirmed | Commercial outcome reporting |
Qualification criteria should be observable: service fit, geography, credible requirements and an appropriate buyer or stakeholder. “Sales liked the conversation” is not a stable definition.
In Google Ads, primary conversion actions generally feed the Conversions column and bidding when their goals are selected for the campaign. Secondary actions are generally observational and appear in All conversions. Custom goals require particular care because included actions can be used for bidding even when marked secondary.
Audit campaign-level goal settings as well as account defaults. Making an event secondary does not replace checking how each campaign actually uses it.
Select the deepest outcome that occurs consistently enough and soon enough to guide optimisation. A won-contract signal may be commercially meaningful but too sparse or delayed to serve as the only bidding input.
Build a traceable path from click to CRM
A practical architecture is:
Ad interaction → landing page → accepted enquiry → CRM record → qualification event → Google Ads import
Each step needs an explicit data contract.
Capture attribution where it is permitted
Subject to consent and applicable requirements, retain supported Google click identifiers, such as GCLID and, where relevant, GBRAID or WBRAID. Preserve campaign parameters for internal reporting too.
Check that redirects, booking tools and domain transitions do not strip identifiers. UTMs describe campaign context, but they do not replace Google’s supported click identifiers for click-based conversion imports.
Do not put names, email addresses or enquiry text into tracking URLs.
Create a stable enquiry identifier
Generate a unique enquiry ID when the backend accepts the submission. Attach it to:
- The application’s enquiry record.
- The corresponding CRM record.
- Relevant analytics events, where permitted.
- The downstream conversion export.
Keep this separate from the Google click identifier. One identifies a business event; the other supports advertising attribution.
Store event timestamps with explicit timezone information. Keep the acquisition time, submission time and qualification time distinct. Their meanings matter when investigating delayed or rejected imports.
Track accepted submissions, not interface activity
A button click does not prove that an enquiry arrived. Validation may fail, the network request may time out, or the CRM integration may reject the record.
Fire the enquiry event after confirmed acceptance. Depending on the application, this can use a success response, a controlled confirmation page or a server-side event.
Watch for common duplication paths:
- Refreshing a thank-you page.
- Installing the same tag through both application code and a tag manager.
- Importing a GA4 event while also counting the equivalent native Google Ads conversion.
- Retrying a backend request without an idempotency key.
Use the relevant platform’s supported deduplication fields and maintain your own processed-event records. Deduplication within one conversion action does not automatically prevent double counting across separate actions.
For lead-generation actions, review whether the “one” counting setting is appropriate. It can limit repeated conversions after an ad interaction, but it is not a substitute for identifying duplicate enquiries.
Telephone-link clicks should remain distinct from connected calls. Where call tracking is used, call duration can be a screening signal, but CRM qualification provides stronger evidence of fit.
Feed qualified outcomes back into Google Ads
When a CRM record reaches an agreed stage, export the corresponding conversion through a supported integration, scheduled upload or API process.
The export should include the required attribution data, conversion action, actual event time and any supported value, currency and deduplication fields.
Where appropriate, enhanced conversions for leads can support matching using first-party customer data processed according to Google’s requirements. This requires correct configuration, appropriate permissions and compliance with customer-data policies; hashing data does not make it anonymous.
Treat the integration like a production data pipeline:
- Validate records before sending them.
- Record submission and processing results.
- Retry transient failures without creating duplicates.
- Alert on authentication failures, stale exports and rising rejection rates.
- Reconcile eligible CRM events against accepted imports.
Check the applicable conversion windows and upload limits for the chosen method. A late sales outcome may be valid commercially but no longer eligible for advertising attribution.
Use defensible values. Confirmed revenue, expected contribution or historically supported stage values can be useful, but they measure different things. Do not present the full value of an uncommitted proposal as realised revenue.
Make consent part of the architecture
For a UK business, consider UK GDPR and PECR obligations alongside Google’s policies. Non-essential advertising storage and tracking generally require consent.
A consent management platform should control relevant tags and pass consent states correctly. Consent Mode communicates consent choices to Google tags; it does not collect consent or establish a lawful basis by itself.
Server-side tagging can improve control over collection and routing. It does not remove consent obligations or justify forwarding customer data indiscriminately.
Document collection purposes, retention periods and access permissions. Keep free-text enquiry content out of advertising and analytics payloads. Test acceptance, rejection and changed-consent journeys, with privacy or legal input where needed.
Validate the system before changing bidding
Run controlled test enquiries through the complete journey. Confirm that:
- An accepted enquiry produces the intended event once.
- Failed validation produces no enquiry conversion.
- The CRM retains the correct enquiry ID and permitted attribution fields.
- Qualification triggers the correct export.
- Google Ads accepts the record without duplication.
Reconcile systems using consistent date definitions. Some Google Ads reporting attributes conversions to the ad interaction date, whereas CRM reports commonly use the enquiry or stage-change date.
Do not expect exact agreement: consent, attribution rules, cross-device journeys and processing delays can create legitimate differences. Investigate unexplained changes in those differences.
Once the pipeline is reliable, move bidding towards the chosen quality signal. Monitor qualified lead cost, opportunity progression and commercial outcomes alongside enquiry volume. Avoid changing targeting, landing pages and conversion goals simultaneously if you need to understand what caused a result.
Practical takeaway
Start with one service, one agreed qualification rule and one traceable CRM-to-Google Ads conversion path. Prove that it works before expanding it. Better tracking will not create demand, but it will stop low-value activity being mistaken for business success.