Your campaign lowers form-submission cost, but sales says most inquiries are unsuitable. Before looking for a new audience, ask whether measurement knows which inquiry became a serious opportunity. If not, a step is missing between the ad dashboard and the sale.
A CRM—customer relationship management system—records what happens after registration. Google supports Qualified leads and Converted leads goals for later sales stages using business data. Start by defining those stages, not connecting a tool. [1]
1. Define “qualified” with sales
Agree criteria the team can apply: company size, market or a request for an available service. Specify who approves qualification and records the reason. Definitions cannot vary by sales rep while results are compared as equivalent.
Distinguish a lead, sales opportunity and completed sale. Each stage has its occurrence date, value and source where available. Expected opportunity value is not collected revenue, and editing a CRM note is not a new stage transition.
2. Map the data before building the connection
Define source, destination, permitted fields, matching and data protection. Google documents conversion management, import and monitoring paths. The developer selects the appropriate route and version after reviewing current permissions and requirements. [2]
Preserve the original stage date separately from delivery or record-update time. Design retries so a failed delivery followed by another attempt does not create two conversions. Do not send free-text sales notes to the ad platform; they may contain details unnecessary for matching.
Practical example: four acceptance cases
These fictional IDs can form an integration acceptance log.
| Fictional internal ID | CRM state | What the integration checks |
|---|---|---|
| demo-lead-01 | Qualified once | One stage event under the agreed design |
| demo-lead-01 | Internal note updated | No new conversion for the note alone |
| demo-lead-02 | Qualified stage, then sale | Separate stage definitions without misleading aggregation |
| demo-lead-03 | Delivery failure, then retry | Outcome log preserving event identity |
Record whether each case was sent, accepted and represents the correct stage. Technically accepted events are insufficient if every edit triggers another conversion.
Agree logs for rejected, retried and delayed cases, without emails, phones or tokens in public reports. Test records must be synthetic or authorized within team access rights.
3. Check the campaign uses the intended outcome
An action appearing in the account does not establish that bidding uses it. Review campaign goals and primary/secondary actions, including the exception where custom goals can use a secondary action for bidding. [3]
Then discuss stage volume, delivery delay and sales follow-up completeness. Do not replace a goal in one click without a review plan: the data may be too sparse or incomplete for the intended question.
4. Demonstrate connection quality before promising performance
Deliver a stage dictionary, field map, test log and counts or rates of unmatched cases from your own data. Assign owners for delivery interruptions and changing sales definitions.
Once data is accepted, commercial evaluation is a separate step. The connection makes sales stages available for measurement under the configuration; it does not prove better lead quality or profitability. Start with a clear question and ensure the data answers it.
Official sources
- Google Ads: qualified and converted leads
- Google Ads API: conversions
- Google Ads: primary and secondary conversion actions
Source documentation reviewed: 16 October 2026. Features and eligibility may change; check the linked documentation before implementation.
