Contents 10
Lead quality is not an ad’s Quality Score
Lead quality means suitability for your business: the required service, eligible region, ability to fulfill the request and an agreed next step. Google Ads Quality Score evaluates different advertising-related factors. A higher score does not prove that sales managers receive more suitable customers.
Write a short definition with sales. Who marks an enquiry as qualified, and when? Which rejection reasons are recorded? How does an unsuitable request differ from a suitable person the team has not yet reached? Without those rules, CRM sends inconsistent labels and the advertising report does not become more dependable.
Lead, Qualified lead and Converted lead
A basic lead confirms an enquiry. Qualified lead means additional qualification outside the ad account. Converted lead means a completed, agreed stage that the business defines as a conversion. Do not call every such event payment: your model may use another milestone. Google documents these categories separately.
One person may pass through several stages. That supports funnel analysis but does not represent several independent customers. Label each event’s meaning, source and counting method. Check which actions are primary, which are observation-only and whether a campaign is optimizing towards contradictory goals at the same time.
| Event | What the business confirms |
|---|---|
| Enquiry | Request received; suitability not yet determined |
| Qualified lead | Request meets agreed criteria |
| Converted lead | A specific agreed stage is complete |
| Payment | Payment confirmed in business records; not inferred from another event’s name |
Source: Google: qualified and converted leads ↗
Agree the event contract before connecting CRM
Describe the event contract before choosing a tool. It needs a stable enquiry identifier, conversion name, timestamp with timezone, relationship to the ad interaction and value/currency if sent. Identify the data owner, delivery delay, retry policy and correction rules.
Click identifiers and permitted user-provided data are used according to the selected matching method. Do not fabricate a missing GCLID or send complete sales notes, call recordings or unnecessary personal information. Check appropriate permissions and Google’s customer-data requirements. Hashing does not automatically make information anonymous or replace the permission needed to use it.
- Who assigns the status, and what does it mean?
- Which event and conversion action receive the record?
- Which timestamp, timezone, value and currency are sent?
- How are duplicate counts prevented and corrections handled?
- How are missing and rejected records monitored?
Enhanced conversions for leads and the current import route
Enhanced conversions for leads supplement offline measurement with permitted user-provided data to support matching. This is not a universal connector for every CRM. Check eligible sources, field support and what your website already collects. Google documents setup through Data Manager; do not copy an old implementation guide without checking the current interface.
Documentation checked on October 12, 2026 describes a unified enhanced-conversions setting from April 2026 and API-import changes from June 15, 2026. For a new integration, use the current Data Manager API guidance and check the status of legacy methods. An old Google Ads API example does not prove that route will work for your developer token and account.
Source: Google: upgrading offline conversion imports ↗
Source: Google: Data Manager for enhanced conversions ↗
A controlled test from enquiry to diagnostics
Follow one test record through the entire path: enquiry, CRM record, agreed status, event creation, delivery and verification result. Use a safe permitted test scenario, not real customer data in screenshots. Record the test identifier, timestamp and conclusion. A ‘sent’ status alone does not establish acceptance and attribution.
Separately test a repeated delivery, status change, missing identifier, incorrect timestamp and temporary delivery failure. Compare the source test record with import diagnostics. Reporting delays and attribution rules may differ from CRM, so totals need not match instantly. Document which differences are explained and which remain unresolved.
- Retrying delivery does not add an extra conversion.
- Failures reach an owner rather than disappearing into logs.
- Server settings do not change timestamps or currency.
- Source, acceptance and attribution are checked separately.
Source: Google: enhanced-conversion diagnostics ↗
When is it safe to change the bidding goal?
First establish a usable, stable signal. Check the share of enquiries with a known status, qualification delay, import frequency and ability to recover missing events. Do not assign an identical arbitrary value to every status simply to enable target ROAS: business value needs a separate rationale.
Change bidding goals under an agreed plan. Check which campaigns use account-default goals, how the change affects learning and when outcomes can be evaluated. Preserve previous settings and rollback criteria. A qualified conversion describes the business objective more closely, but the integration itself guarantees neither lower CPL nor higher sales.
What should a manager’s report show?
Do not report only total conversions. Separate received enquiries, reviewed enquiries, qualified leads and completed stages. Show spend, period, source, status definition and outcome delay alongside them. Events whose quality is unknown remain a separate group rather than automatically counting as successful or unsuitable.
The conclusion should name what is known, what is missing and the next action: repair the form, CRM rules, import or campaign. This is a measurement plan, not a promise of one-click integration with any CRM. For an existing account, begin with a Google Ads audit and an anonymized example of your status structure.
CRM and offline-conversion questions
Is form-submission tracking enough?
A form confirms an enquiry, not the customer’s suitability or a sale. For a service or B2B business, the next outcome often appears later in CRM. Keep the form event for early-funnel analysis while defining qualification and completed stages separately. Before changing bids, check data stability, status delays and the conversion actions your campaigns actually use, rather than assuming every recorded event is a customer.
Can a hashed email be uploaded without other checks?
No. Hashing is part of technical data preparation, not automatic permission to use it. Check platform requirements, appropriate permissions, user notices and the consent signals needed for the particular process. Send only permitted necessary fields, not free-form notes or a complete customer profile. If processing conditions are unclear, resolve them with the data owner before connecting imports or sharing actual customer information.
Why do CRM and Google Ads show different totals?
Compare matching event definitions, periods, timezones and attribution windows. Some records may still await a status, delivery or matching; others may be rejected or unrelated to an ad interaction. Check specific anonymized control records and diagnostics rather than just aggregate totals. A discrepancy alone does not prove a fault: separate explained differences from real failures and record the unresolved ones in the report.
Sources and verification date
Documentation and copy checked on October 12, 2026.
- Google: enhanced-conversion diagnostics
- Google: upgrading offline conversion imports
- Google: qualified and converted leads
- Google: Data Manager for enhanced conversions