A correct conversion should confirm a useful customer action, not merely a click that is easy to measure. If Google Ads counts a messenger click as a lead and the visitor closes the app, the account receives a positive signal even though the business received no contact. If a form is accepted but the event never reaches analytics, effective advertising may look unproductive.
Start by agreeing what every event means. Only then should you inspect Google Tag Manager, GA4 and imports into Google Ads. A technically valid tag still sends bad data when the underlying action is defined incorrectly.
Which actions should count as conversions
A website usually has several levels of interaction. They should not be merged into one goal because viewing contact details and submitting a verified enquiry have very different business value.
Supporting signals
Contact-page views, form starts, scrolling or opening a calculator. These actions help analyse behaviour but should not replace enquiries.
Intent to contact
A click on a phone number, Telegram, Viber or WhatsApp. The visitor shows intent, but a call or conversation is not yet confirmed.
Verified enquiries
A successfully accepted form, a call of sufficient duration, a started conversation or a lead recorded in the CRM.
All levels are useful for reporting, but Google Ads automated bidding should optimise primarily for actions close to a business outcome. Earlier signals can remain secondary conversions so they stay visible without controlling bids.
How strongly different events confirm a genuine enquiry
This chart is an illustrative diagnostic scale, not an industry benchmark. The closer an event is to a verified conversation or qualified lead, the safer it is as an advertising optimisation signal.
What to check in Google Ads
Review the source, status and campaign-goal participation of every conversion action. One enquiry can enter the account twice: directly through a Google Ads tag and through an imported GA4 key event. If both actions are primary, reporting is inflated and bidding learns from duplicates.
Check the counting setting. A lead action usually counts once after an ad interaction, while a purchase may count every transaction. Make sure action values reflect business value: a chat click should not receive the same value as a paid order.
Review the goals used by each campaign. Account-default goals may contain actions unrelated to the campaign. A consultation campaign should not optimise for page views or file downloads merely because those events were added earlier.
A sign of incorrect optimisation
Reported conversions rise and their apparent cost falls, while the business receives no additional calls, conversations or forms. This often means that an early interaction is the primary goal or one enquiry is recorded several times.
If you also need to inspect campaign structure, search terms and bidding, read the Google Ads launch and control guide or work with an SK Marketing PPC specialist.
How GA4 and Google Tag Manager work together
Google Tag Manager controls when tags fire, while GA4 receives events and parameters. First inspect the trigger: which element activates it, on which pages and after which outcome. Then confirm that the event reached the correct GA4 property and has a clear name.
GTM Preview shows the browser action and the tags that fired. GA4 DebugView and Realtime help verify reception. The presence of an event is not enough: repeat both successful and unsuccessful scenarios.
A useful form test includes empty fields, an invalid phone number, valid data and a repeated click. The conversion should appear only when the server accepts the enquiry. A click-based trigger counts validation errors and technical failures as leads.
Use stable, understandable event names and separate successful forms, phone clicks and messenger opens. Parameters can carry form type, page and button placement. This makes it possible to compare site elements without creating dozens of nearly identical conversions.
Read more about measurement design on the analytics setup page. Connecting advertising, website behaviour and lead quality requires the broader discipline of web analytics.
Forms, calls and messengers require different checks
Forms
A reliable signal is a successful server response or a unique thank-you page. For an AJAX form, a developer can push an event to the dataLayer after the record is confirmed. Tracking only a button CSS class is fragile and does not confirm acceptance.
Phone
A tel: click shows an attempt to call, not a completed conversation. Use call tracking, dynamic numbers or verified imports when call quality matters. Separate missed and very short calls from conversations recognised as relevant.
Telegram, Viber and WhatsApp
The browser sees a link click but usually cannot tell whether the visitor sent a message. Treat the click as contact intent and confirm an actual conversation through a CRM, enquiry log or an integration that receives message data.
This distinction matters for automated bidding. If a campaign produces many cheap messenger-icon clicks, the algorithm will search for similar users even when most never start a conversation.
Technical diagnosis of discrepancies
| Symptom | Likely cause | What to inspect | Remedy |
|---|---|---|---|
| Google Ads reports more leads than the business receives | Duplicate imports or click-based conversion | Action sources, GTM Preview and successful form response | Keep one primary source and move early actions to secondary |
| Forms arrive but conversions do not | The tag does not fire after success | dataLayer, DebugView, trigger rules and property ID | Send the event after server confirmation |
| An event appears several times | Repeated listener, two containers or multiple tags | Container count, event history and loaded scripts | Remove duplicates and prevent repeated sends |
| Some mobile events disappear | Redirect, messenger app or JavaScript error | Real devices, multiple browsers and error console | Fix the handler and test each contact button |
| Data arrives late | Normal processing or delayed import | Realtime, DebugView and report processing time | Do not compare incomplete periods |
| Data decreased after a consent banner | Consent Mode state changed | Consent state before and after the user choice | Correct tag order and preserve the user choice |
Consent Mode and browser restrictions
A consent banner affects identifiers and measurement completeness. Check the default state, the update after a choice and whether marketing tags run too early. Technical settings must reflect and preserve the user's actual decision.
Enhanced Conversions
Enhanced Conversions can match enquiries to ad interactions using transformed first-party customer data. They do not replace the main event or repair a false trigger. Establish a lawful basis, update privacy information and transmit only the intended fields.
Offline conversions and CRM
The most useful audit ends in lead records, not GA4. Saving the ad-click identifier and later importing a qualified lead distinguishes a submitted form from a real prospect. Even without a complex integration, regularly compare date, source, landing page and lead outcome.
Conversion tracking checklist
- Every event has a written definition of what it confirms.
- Primary and secondary conversions are separated by business value.
- One enquiry is not sent through two primary sources.
- A form is recorded after success, not on a button click.
- Phone and messenger clicks are not treated as verified conversations.
- Events are checked in GTM Preview, DebugView and Realtime.
- Names and parameters identify the form, page and channel.
- Tracking is tested on mobile devices and multiple browsers.
- Consent Mode reflects the user's choice.
- Ad-platform data is reconciled with forms, calls and CRM records.
If ads are running but no leads arrive, first make sure measurement is not creating a false picture. Then assess queries, the landing page and the offer. See why a website can receive traffic without generating leads.
When an external audit is useful
If several providers configured events, old goals accumulated in the account or Google Ads totals conflict with real enquiries, SK Marketing can audit the measurement path, document errors and prepare a prioritised correction plan.
Questions and answers
Why do Google Ads and GA4 report different conversion totals?
The platforms use different attribution models, conversion dates, windows and data processing rules. Compare the same actions over comparable periods and allow for processing delays.
Can a click to Telegram or WhatsApp be counted as a lead?
A click shows intent to open a messenger, but it does not prove that a conversation started. Use it as a secondary conversion and verify real enquiries through conversations or CRM data.
Should I import a GA4 event and also install a Google Ads tag?
A business action should normally have one primary conversion source. Sending the same result through two primary actions can create duplicates.
When should a form submission event fire?
After a successful server response or a unique thank-you page loads. A button click does not prove that validation passed and the enquiry was accepted.
How can I tell whether automated bidding is learning from the right data?
Review the primary conversion actions, their values, sources and match with genuine enquiries. Page views, form opens and accidental clicks should not train bidding.