Google Ads reports plenty of conversions, but your inbox and phone tell a quieter story. Before increasing spend or rewriting the adverts, check what those conversions actually measure. A visit to your contact page, a click on a telephone link and a successfully received enquiry are different actions.
For a lead-generation Search campaign, browsing activity can be useful evidence without being the outcome you ask bidding to pursue. The investigation has three parts: what triggers each conversion action, whether it is primary or secondary, and which goals the campaign uses. Changing just one setting can leave the wrong action eligible for bidding.
First, establish whether page views really are the problem
Start with one campaign and a completed reporting period. In its reporting table, add Conversions and All conversions, then segment the figures by conversion action. Write down the actions contributing to the total before changing anything.
Google distinguishes these columns in its Results Reporting guidance: Conversions reflects the actions in the goals the campaign optimises towards, including the custom-goal exception discussed below. All conversions includes primary and secondary actions, even when the campaign is not actively optimising towards their goals. Results is another measure, covering primary actions within standard goals; it is not interchangeable with either column.
If page visits appear only in All conversions, the alarming headline may be a reporting choice. Check campaign settings before assuming bidding is pursuing them. Ask whoever prepares your report to label enquiry measures separately from browsing measures.
A page-view trigger can still represent a genuine enquiry
Do not judge an action by its name alone. A conversion called “Page view” might fire on a confirmation page reached after successful submission. An action called “Lead” might fire whenever somebody opens the contact page. Inspect the actual rule or implementation.
Ask your developer to demonstrate the trigger in a test session. Does it happen on arrival, on a button click, after validation, or only once the website accepts the enquiry? Does opening the confirmation URL directly produce the same event? The answer determines whether you need a measurement repair, a goal-setting repair, or both.
Check primary status and campaign goals together
Google’s primary and secondary conversion guidance explains the usual arrangement: a primary action is included in Conversions and used for bidding when its standard goal is selected by the campaign. A secondary action is normally observed in All conversions. Primary status alone does not establish that a particular campaign is optimising towards the action.
For a business seeking quote requests, a sensible starting recommendation is to keep general browsing interactions as supporting measures and use a dependable enquiry milestone as the main outcome. Choose that milestone from evidence:
- A contact-page visit shows interest, but does not establish that somebody contacted you.
- A telephone-link click shows an attempt to call, but does not establish a connected conversation.
- A successful form submission establishes a received request only if the website and delivery process have been checked.
- A qualified enquiry requires a consistent assessment by your business, rather than a more impressive conversion name.
These are business definitions to agree with the team handling enquiries. A useful primary action should mean something specific enough that somebody can explain what happened after it was recorded.
Account defaults do not describe every campaign
Open the campaign’s settings and inspect Conversion goals. Record whether it uses account-default goals or campaign-specific goals, and list the goals selected. Google confirms that campaign-specific goals override account defaults. A correction to the defaults therefore does not settle the question for every campaign.
Check other campaigns using the same action before editing it. If a page visit has an intentional role in a separate campaign, resolve that purpose explicitly rather than applying a blanket account-wide change.
The custom-goal exception matters
A secondary action included in a custom goal can still be used for bidding when the campaign uses that custom goal. Google’s campaign-specific guidance makes this explicit: actions within a custom goal are used regardless of primary or secondary status.
That explains a frustrating situation: somebody marks a contact-page visit as Secondary, yet it remains part of the campaign’s bidding objective. Inspect the custom goal’s membership as well as the action setting. If the browsing action should not be pursued, review its inclusion in that custom goal and confirm the intended replacement before saving.
Make the smallest correction that fixes the cause
Keep a record of the current action settings, campaign goals, bid strategy, targets and budget. Give the proposed change an owner and a clear reason. A useful instruction is “stop using contact-page visits for this lead-generation campaign”; “improve tracking” leaves too much open to interpretation.
Google’s conversion-summary instructions describe the editing route: open Goals, Conversions and Summary, find the relevant goal, choose Edit goal, then review Conversion action optimisation. Where appropriate, choose Secondary (observe only) for a browsing action. The same guidance warns that changing an action’s usage affects the places where its goal is used.
If the problem lies in campaign-specific or custom-goal selection, correct that selection too. Reopen the campaign afterwards and verify the saved result. Do not delete a useful diagnostic measure simply because it should not be a bidding objective.
Keep trigger repairs separate in your change record. Renaming a contact-page event “Successful enquiry” does not alter when it fires. Equally, selecting a better goal will not repair a form that fails to deliver requests.
Changing the count setting solves a different problem
Google’s conversion counting options let you choose One or Every for an action. One can suit lead generation, while Every can suit separate sales. The setting applies per conversion action; it does not merge several different actions into one customer. Changes apply to future conversions, not past data.
Setting a contact-page visit to One therefore does not turn it into an enquiry. Establish the right event and bidding role first, then choose a counting method that matches the event’s purpose.
Plan the bidding transition before removing a major signal
If most reported conversions are easy browsing actions, removing them changes what the campaign is being asked to achieve. Check that the replacement enquiry measure works reliably before relying on it. An action with no recent records needs investigation; its absence is not a reason to promote an unrelated page visit.
Google’s guidance on changing Smart Bidding goals says goal and action changes can require learning, usually over one to two conversion cycles. A cycle depends on conversion delay, so do not promise that every account will settle within the same number of days. Record an affordable budget and a review date suited to the business’s enquiry journey.
There is a more specific route when staying on Target CPA and moving from an upper-funnel action to Purchase, Qualified lead or Converted lead. Google’s lower-funnel transition instructions recommend correctly categorising the new action, marking it primary without yet selecting it for bidding, and collecting it for at least two to three conversion cycles before the switch. They also call for a CPA target appropriate to the new outcome. This is a particular migration process, not a universal instruction to make every observed event primary.
A target based on cheap page visits is not a useful cost benchmark for qualified enquiries. Ask your campaign manager to explain the proposed target using evidence for the new milestone. Avoid bundling the repair with unrelated budget, advert and landing-page changes that make the outcome harder to assess.
Verify the customer journey and the saved settings
Use a short test plan with expected results agreed beforehand:
- Browse without enquiring. Open the landing and contact pages. Confirm that this does not trigger the action intended to mean successful submission.
- Try an incomplete form. A validation error should not produce the successful-submission event.
- Submit a clearly identified test enquiry. Confirm acceptance on the website and receipt by the intended inbox or CRM. Ask the developer to show the matching event in the diagnostic tool.
- Check the campaign configuration again. Verify the selected goals, primary and secondary settings, and any custom-goal membership.
- Review subsequent reporting by action. Confirm which events contribute to Conversions and which remain supporting measures in All conversions.
A direct test can establish that an event fires and an enquiry arrives; it does not establish that Google Ads will attribute a conversion to an advert. Keep implementation testing and campaign-attributed reporting as separate checks. Allow for reporting delay before judging the latter.
Expect the headline total to look different if its definition changes. Compare subsequent spend with confirmed enquiries and their quality, and annotate the date of the correction so future reports explain the break. Our guide to connecting conversion reporting with qualified enquiries and sales covers that wider commercial review.
If Google Ads reports leads your team cannot recognise, contact BuzzBoost Digital to discuss checking the website trigger, campaign goals and enquiry handover together. The useful result is a clear account of what each conversion means and why the campaign should pursue it.
Featured image: AI-generated editorial artwork, not a photograph of a real BuzzBoost office, client or result.
