GA4 can show what visitors do after they reach your website. Google Search Console can show many of the Google queries that produced impressions and clicks. Your CRM should show which enquiries became qualified opportunities or customers.
For a US service business, the practical setup is to use Search Console for organic search demand, GA4 for on-site behavior, and the CRM for lead quality and revenue. You cannot reliably connect every organic query to a named individual, but you can connect search demand, landing-page behavior, successful lead actions, and downstream sales outcomes well enough to guide marketing.
What GA4, Search Console and your CRM each measure
| System | Best question it answers | Important limitation |
|---|---|---|
| Google Search Console | Which Google queries and pages earned impressions, clicks, click-through rate and average position? | It does not identify the individual who searched, and some queries are withheld or truncated. |
| GA4 | Which channels and pages led to events such as form submissions, calls or booking actions? | An event does not prove lead quality or revenue unless later outcomes are connected. |
| CRM | Which enquiries were contacted, qualified, converted or lost? | Source data is only useful when campaign fields and stages are captured consistently. |
Google describes GA4 as an event-based measurement system. Its recommended events include generate_lead, qualify_lead, working_lead and close_convert_lead for lead-generation journeys. Search Console’s Performance report separately records Google Search queries, pages, countries, devices, clicks, impressions, CTR and position.
The evidence comes from the platforms. The recommendation is to give each system a clear job instead of forcing one dashboard to answer everything.
Build a GA4 event plan around business actions
Start by listing the actions that matter commercially. Do not begin with every button on the website.
A useful lead-generation plan could include:
| Visitor action | Suggested measurement | Make it a key event? |
|---|---|---|
| Views a service or case-study page | page_view plus page path | Usually no |
| Starts a form | form_start | Usually no |
| Successfully submits an enquiry | generate_lead | Yes |
| Clicks phone, email or WhatsApp | A clearly named contact-click event with method and page | Usually secondary |
| Opens an external booking tool | booking_started or an outbound-click event | Usually secondary |
| Reaches a confirmed booking | booking_completed | Yes, after verification |
| Becomes sales-qualified | qualify_lead, normally sent from the CRM | Yes if consistently defined |
GA4’s enhanced measurement can collect events such as outbound clicks and form interactions without custom page code. That is helpful for diagnostics, but an automatic form_submit event is not always the same as a successful enquiry. Validation errors, spam blocks, duplicate triggers or a form that fails after the browser event can inflate the count.
Our recommendation is to send generate_lead only after the server or application confirms that a valid enquiry was accepted. If a booking uses Calendly or another external system, distinguish “opened booking page” from “booking confirmed.” A click shows intent; it does not prove completion.
This same principle applies to paid media. Our Google Ads offline conversion tracking guide explains why a form submission and a qualified lead should remain separate outcomes. For social campaigns, see how Meta lead ads and CRM feedback work together.
Use parameters that help decisions—not personal data
Use decision-ready parameters such as form name, page path, service category, contact method, button location and tool name.
Do not send the visitor’s name, email address, phone number, WhatsApp number, message or form answers to GA4. Google’s PII guidance says customers must not pass personally identifiable information that Google could recognize. Keep contact details and sensitive form content in the secure enquiry system or CRM.
Avoid high-cardinality parameters such as unique message text or record IDs in standard reports. They create noisy reporting and rarely improve a marketing decision.
Where can you see the keywords people searched?
For organic Google searches, use Search Console—not GA4’s general traffic-source report.
After linking Search Console to GA4, the Search Console collection can add a Queries report and a Google organic search traffic report. Google’s connection instructions note that the collection is unpublished by default, so an Editor may need to publish it from the Reports Library.
Use the reports to identify non-branded US service queries, landing pages with clicks but few useful actions, and commercial topics that later contribute to enquiries.
A practical monthly review is to filter Search Console to the United States, compare branded and non-branded query groups, then inspect the landing pages behind those clicks. In GA4, review organic traffic to those pages and compare engagement and lead events. In the CRM, check whether enquiries from organic search became qualified.
Search Console does not provide a complete, person-level keyword trail. Google’s query documentation states that some queries are omitted for privacy and that the table does not show every row because of data limits. Those missing queries can still contribute to chart totals. This is why Search Console clicks and GA4 sessions should not be expected to match exactly.
A simple example of joined-up measurement
Consider a hypothetical US B2B company. Search Console shows that a service-comparison page received 420 Google clicks during a month. GA4 records 18 confirmed generate_lead events from organic traffic landing on that page. The CRM shows that seven met the written qualification rule and two became opportunities.
The useful ratios are:
- confirmed lead rate: 18 ÷ 420 = 4.3%;
- qualified-lead rate from confirmed leads: 7 ÷ 18 = 38.9%;
- opportunity rate from qualified leads: 2 ÷ 7 = 28.6%.
These figures are illustrative, not benchmarks or client results. They show why rankings or clicks alone are insufficient. A page can attract traffic while failing to generate suitable enquiries, or produce fewer leads that are commercially stronger.
Verify events before relying on reports
Test each key action on desktop and mobile:
- Submit a valid enquiry and confirm exactly one
generate_leadevent. - Trigger form errors or spam protection and confirm blocked submissions do not count.
- Test email, phone and WhatsApp clicks with their method and page parameters.
- Open the booking tool without completing it, then confirm a completed test booking remains a separate event.
- Confirm the CRM uses one written definition for “qualified.”
Google recommends using Realtime and DebugView to verify incoming events. Standard reports can take longer to process, so do not use an empty same-day report as proof that tracking failed.
Turn measurement into a weekly decision
A useful report does not need dozens of charts. Review:
- top US organic queries and landing pages;
- leads by source, page and action;
- contact-click versus confirmed-submission rates;
- qualified leads and opportunities by source;
- pages with traffic but no meaningful next step;
- duplicate events, unexpected referral sources and sudden tracking changes.
Then choose one change: improve a high-impression title, fix a form failure, clarify a service page, strengthen qualification questions, or connect a missing CRM stage. Measure the result before making five more changes.
You can build a free marketing action plan with three priority improvements, recommended channels and practical next steps, plus an optional free consultation.
Need help implementing GA4 events, Search Console reporting, CRM lead stages and conversion measurement? Discuss your tracking setup with SW SOFTTECH. Share the actions you need to measure and the point where attribution or lead quality currently becomes unclear.
Primary Google documentation checked October 12, 2026. Platform labels, report availability and integration requirements can change. The workflow recommendations above are practical guidance, not a promise of rankings, lead volume or revenue.