Choose the event your team can apply consistently
A qualified-lead conversion is a later sales milestone connected to an advertising interaction where the platform can match it. It should represent a meaningful change in readiness or fit, not merely a form submission renamed in the CRM.
Write the rule in ordinary language and test it against example records. Include the date the milestone was reached and a stable internal event reference. Different team members should reach the same conclusion from the same evidence.
CRM event
Qualification has a documented meaning.
Eligible record
Required context and permissions are present.
Delivery result
Accepted or rejected is observable.
Reporting result
Matching and use are checked separately.
Do not equate an HTTP success response with a useful optimization signal.
Qualified lead or completed job: decide from the process
| Candidate signal | Check before using it |
|---|---|
| Raw inquiry | Useful for understanding intake, but it does not establish service fit or a customer. |
| Qualified lead | A definition operators apply consistently, with recorded evidence and sufficient usable history. |
| Completed job or converted customer | A meaningful downstream outcome, with sales delay, available identifiers and reporting coverage understood. |
Do not switch to the deepest event only because a Reddit comment recommends it. Assess consistency, available event volume and sales delay with the account specialist. Google’s current documentation distinguishes primary biddable conversion actions from secondary observation actions; inspect the actual account goals and settings rather than assuming an imported event changes bidding.
Keep lead-stage facts separate from amounts. A quote value is not received revenue, and a zero-value unclosed lead is not a confirmed completed job.
Confirm the current Google setup
Google’s enhanced conversions for leads documentation describes using first-party information to improve measurement of later outcomes. Other supported paths can use advertising click identifiers. The correct implementation depends on the account, data and current provider requirements.
Before following a tutorial, check the official setup and migration guidance. Upload routes and API support change over time. This guide deliberately describes the verification process rather than giving an old endpoint or a universal code sample that might no longer fit your account.
Build a verification set before relying on the signal
Choose a small set of records that exercise the connection’s actual rules. Include an eligible qualified inquiry, an ineligible record, a duplicate delivery attempt and a corrected outcome. Use a safe validation method appropriate to the destination; do not manufacture customer outcomes in a live advertising account.
Record what the CRM says should happen and what the destination reports. A rejected delivery usually needs a different investigation from an accepted event that does not match. A record excluded by your eligibility rule is a third case and should remain visible rather than disappear from the totals.
Before using the event to steer a campaign, the marketing and sales owners should agree that the definition is stable and that delivery quality is understood. Otherwise a change in CRM habits can look like a sudden change in advertising performance. Keep platform-specific setup instructions tied to the current official documentation linked below.
Document the operational handover
- Event definition, allowed source stages and required record fields.
- Eligibility exclusions and the responsible person for incomplete records.
- Delivery history, duplicate handling and the process for corrections.
- Destination diagnostics and the distinction between delivery, matching and campaign use.
Build the mapping before sending data
| Mapping field | Question to resolve |
|---|---|
| Conversion action | Which defined business event does it represent? |
| Source identifiers | Were the required identifiers captured and retained through intake? |
| Event time | When did the CRM milestone actually occur? |
| Value | Is it a real defined value or an estimate, and how is it labeled? |
| Event identity | How are repeated delivery and duplicate records handled? |
| Permissions and settings | Is the intended data path supported and appropriately configured? |
Do not reconstruct missing attribution by guessing which campaign probably brought a customer. If records lack the required evidence, mark them ineligible or unresolved and fix the capture path for future inquiries.
Validate more than a successful request
- Confirm a controlled record has the expected milestone and permitted matching data.
- Use the supported delivery route for the configured conversion action.
- Inspect the provider’s acceptance and error diagnostics.
- Reconcile attempted, rejected, accepted and attributed events separately.
- Verify duplicate handling and document exception ownership.
A successful transport response does not establish that every record was matched or included in campaign reporting. Processing delays and provider diagnostics matter. Keep the evidence at each step so the operator can investigate a missing result without repeatedly sending the same event.
Diagnose missing Google Ads offline conversions
If a Google Ads offline conversion upload succeeded but the report is empty, start with offline data diagnostics. A successful upload confirms receipt of data. Matching an eligible ad interaction and showing it in a report are separate steps.
| What you see | First check | What to do |
|---|---|---|
| The import has errors | Look at rejected rows and the error reason in diagnostics. | Check conversion action, account, identifier and event time. Fix the affected records and retry only where appropriate. |
| Accepted rows do not match | Confirm eligible ad interactions and the original lead identifiers or permitted matching data. | Check the configured conversion window and correct account. Some unmatched rows are expected with mixed lead sources. |
| Diagnostics show receipt but the report is empty | Check processing time, date range and the conversion action segment. | Compare the standard column with Conversions (by conv. time), using the CRM event date and the account time zone. |
| The event appears in All conversions only | Check whether the action is secondary and which goals the campaign uses. | Confirm the intended measurement setup before changing settings used for bidding. |
| Fewer conversions are counted than were sent | Check for duplicate event or order IDs and the action’s count setting. | Keep one stable ID per intended event where supported. Compare like-for-like records before replaying uploads. |
Example: someone clicks an ad on Monday and qualifies on Thursday. A standard conversion report can credit Monday, while a report by conversion time can show Thursday. Check both dates and trace the same CRM record before assuming the event was lost.
Open Google Ads troubleshooting for offline conversion imports.
Keep low volume and sales delay in view
Later-stage outcomes can be sparse for a service business. A stricter event is not automatically a better bidding signal if it arrives rarely or with long delay. The event should retain business meaning, and the campaign decision should reflect the available amount and timeliness of evidence.
Growth Control scopes the milestone, supported connection and validation process before implementation. It does not assume that every CRM already has a working Google Ads upload or promise that connecting one will immediately improve campaign performance.
How Hunter and the sales agents support the signal
Hunter reviews connected campaign evidence and available CRM outcomes, proposes a conversion-goal or campaign change, and waits for the required approval. Figaro helps collect a usable inquiry brief. Cyrano can help a human confirm the facts learned on a sales call. The team owns the qualification definition and the recorded outcome.
For a fictional Stretch Tent inquiry, a valid date and suitable service request may support qualification after review; a prepared quote, a custom-sale signature and a received deposit remain separate milestones. Choose and map the intended event explicitly. Atticus’s custom-sale integration is planned, so it cannot be used as evidence of an already functioning conversion feed.
An integration owner must still validate the upload, customer match, timestamps, duplicates and diagnostics. Enhanced conversions for leads has a diagnostics report; an accepted request is not proof that every event matched or appeared immediately.
Review Hunter’s decision and campaign scope.
Write an event contract before connecting the upload
An event contract is a shared definition for the marketing operator, CRM owner and integration maintainer. It describes the business milestone and the evidence required to emit it. It is not a legal contract or a universal payload format; the destination’s current documentation determines the technical mapping.
| Definition | Question to settle |
|---|---|
| Business milestone | What exactly happened, and who is authorized to record it? |
| Eligibility | Which records meet the definition, and which are excluded or unresolved? |
| Occurrence time | When did the milestone happen, rather than when did the export run? |
| Identity and source | What evidence links the opportunity and advertising context? |
| Value interpretation | Does the number represent a stated estimate, order amount or another defined measure? |
| Correction ownership | Who handles an incorrect outcome or repeated delivery through the supported process? |
Figaro and Cyrano can help prepare context and reviewed facts in their supported workflows. They do not replace the business definition or enable a live offline-conversion feed on their own. Hunter’s analysis depends on available, appropriately mapped outcomes.
Work through one qualified event without confusing later milestones
Fictional Stretch Tent event-mapping exercise. It does not upload a conversion or describe a live Atticus integration.
A request has an identifiable customer, event date, location and requirements that the owner considers within scope. That evidence may satisfy the business’s defined qualification milestone. The team records the decision and when it occurred. If a required source identifier is missing, keep the attribution gap visible rather than guessing a campaign.
A quote is later prepared. The customer may then accept an offer, complete required signatures for a custom sale and pay an issued invoice. Those are separate milestones with different evidence and timing. An invoice proposal is not received revenue, and an unanswered quote is not a completed job with zero sales value.
Choose which defined event the account should use for the intended decision. Review the primary/secondary configuration and relevant campaign goals with the account specialist. Do not prescribe a blanket switch to the deepest event when downstream observations are sparse or delayed.
Classify missing events before retrying them
| Observation | First investigation |
|---|---|
| Record intentionally excluded | Check eligibility and whether the exclusion is correct. |
| Delivery rejected | Inspect the destination’s reported reason and the supported mapping. |
| Delivery accepted but not visible as expected | Check matching, reporting dates, processing state and current diagnostics. |
| Repeated event or changed outcome | Review event identity and the supported correction/recovery process. |
Keep source, attempted delivery and destination reporting distinguishable. Blindly retrying every missing row can create confusion instead of better coverage. The integration owner resolves delivery and identity; the marketing owner checks what the report means before using it to steer spend.
The official enhanced-conversions diagnostics report is a source for implementation issues. Continue to use the current Google documentation below for provider-specific requirements, rather than treating this operating checklist or Reddit advice as an API specification.
Questions and answers
Should I send only closed deals?
Not automatically. Choose a meaningful milestone suited to the business and available evidence, then assess volume and delay. A later event is not always the most useful immediate feedback signal.
Can I upload old leads without identifiers?
Do not assume they can be matched. Eligibility depends on the data and current provider requirements; review the records before committing to an upload.
Does accepted mean attributed?
No. Keep transport acceptance, matching and attribution distinct. Provider diagnostics and reporting establish different parts of the result.
Where are the exact API instructions?
Use the current official Google documentation linked below. Verify the supported route for your account before implementing an example from a third-party tutorial.
Sources and further reading
Put the process into practice
Growth Control implements the tools, workflow and team handoff around an agreed business result.
Explore connect qualified CRM outcomes to your advertising platforms