7 minute read · Practical marketing guidance
On this page 7 sections
Your Google Ads report shows conversions, but your team has fewer inquiries to discuss. Before calling that a campaign problem, check what each conversion action measures. A quote-button click, an accepted form request and an inquiry received by your staff are different events.
For a Las Vegas or Henderson business, a useful conversion tracking review connects the action name to its exact trigger, the evidence behind it and the campaign that uses it. The name “Lead” does not establish that a customer contacted you, qualified for your service or booked work.
Define the business event you want to understand
Start with the person who reviews inquiries and the person who manages measurement. Agree on the distinction between:
- Interest: someone clicks a quote button or begins a form.
- Accepted request: the website successfully accepts the submitted form.
- Received inquiry: your business finds the matching request in its intended inbox or working system.
- Qualified opportunity: the team checks the request against its actual service, coverage and other acceptance conditions.
These are working definitions for your review, rather than automatic Google Ads classifications. Write down how your business verifies each stage. A website success event cannot establish staff receipt or service fit on its own; a received inquiry can still concern work you do not offer.
Choose the stage appropriate to the campaign’s objective and the measurement you can support. You may need visibility into several stages. Keep their meanings separate instead of adding them together and calling the result “leads.”
Inventory actions before changing settings
Open Goals → Conversions → Summary and inspect each relevant action. Then check the campaign’s Conversion goals settings. Google’s conversion goals documentation explains that goals group actions, and campaigns can use account-default or campaign-specific goals. The campaign’s Conversions reporting reflects its selected goals.
Copy the following record for each action. If a fact is unknown, assign someone to investigate it; do not fill the gap from the action’s name.
| Inventory field | What to record |
|---|---|
| Action identity and source | Exact action name and its source, such as website measurement or an imported event. Identify the relevant page or system. |
| Exact trigger | What causes the measurement: button click, successful acceptance event, confirmation-page load or another verified condition. Include what must happen first. |
| Business meaning | The event this establishes, what it does not prove and the separate evidence needed for received or qualified inquiries. |
| Counting | The action’s actual One or Every setting, with the reason it suits the intended event. Do not assume a default. |
| Goal and reporting role | Primary or secondary designation where available; standard or custom goal; which reviewed campaigns use it and why. |
| Duplicate risk | Other actions measuring the same request, repeat triggers, confirmation-page revisits or parallel implementations to inspect. |
| Test evidence | Test conditions, time and time zone, observed trigger behavior and matching business record. Separate debug observations from Ads report evidence. |
| Decision and owner | What needs clarification or correction, who approves the business definition, who handles implementation and when to retest. |
The inventory is deliberately about meaning as well as technical behavior. An action can fire reliably every time someone clicks a button and still be the wrong evidence for a completed request.
Check reporting and bidding together
Google’s primary and secondary action guidance says primary actions appear in Conversions and are used for bidding when their standard goal is used for bidding. Secondary actions normally appear in All conversions for observation rather than bidding. The custom-goal exception matters: When a campaign uses a custom goal, the actions included in it are used for reporting and bidding regardless of their primary or secondary label.
Record both the designation and the campaign’s goal selection. Changing an action to secondary does not establish that a custom goal has stopped using it. Likewise, finding a primary action in the account does not explain its role in every campaign.
Observation data can be useful. A form-start measurement might help you examine the path to submission. It should retain that meaning in your reporting. Do not treat an observation label as proof that the underlying trigger is accurate, or delete an action simply because it represents an earlier stage.
Understand what One and Every count
Google’s counting guidance applies the setting to each conversion action. Every counts each conversion for that action after an ad interaction; One counts one conversion for that action per ad click. One does not mean one unique person across the account or one inquiry across different actions.
If two distinct actions measure the same request, selecting One for each does not combine them into a single business inquiry. Investigate the overlapping definitions and campaign goals. Also distinguish repeated firing of one action from two different actions firing: those are separate questions.
A counting change applies to future conversions, rather than rewriting the action’s historical data. Preserve the previous setting and change date so later comparisons have context. Choose a setting that describes your objective; do not change it solely to make a report total resemble an inbox count.
A hypothetical request measured twice
Consider an invented Las Vegas window-covering consultation business. Its website, action names, settings and observations below are hypothetical. This is a diagnostic demonstration, not real account data, a client case study or a claimed campaign result.
The example campaign uses a standard goal containing two primary actions, both set to One:
- Consultation request accepted: triggered by the form system’s verified successful acceptance event.
- Consultation thank-you visit: triggered when the success page loads after that acceptance.
One controlled test submits one request. The website accepts it, the success page loads and the business finds one matching inquiry record. Debug evidence shows both action measurements firing. They describe two observations of the same request, rather than two separate customer inquiries.
With both actions primary and their standard goal selected, each can contribute conversion credit separately. Setting each to One does not prevent that overlap. The debug session establishes the observed firing behavior; it does not guarantee an immediate pair of attributed conversions in the Google Ads report.
The next decision is which measurement reliably represents the intended request and what role the other should serve. Have the account and website owners inspect the definitions, implementation and campaign goals together. If an action fires on an incorrect event, changing its reporting role alone does not repair the trigger.
Test the action and a case that should not trigger it
Use clearly labeled sample information and a test contact address you control. Save the page, conditions and time so the website owner can trace the observation. Avoid clicking your own live ad to run the test.
Work through four cases:
- Page visit: open the form without submitting. Does a request action fire merely because the page loaded?
- Failed submission: leave a required field empty and confirm validation prevents acceptance. Record any measurement that nevertheless fires.
- Successful request: complete one test and compare the measured event with the form’s acceptance and the matching business record.
- Confirmation revisit: where applicable, reload or return to the success page. Check for repeat measurement without a new request.
Google’s Tag Assistant troubleshooting guidance describes connecting to a website, triggering an action and reviewing the diagnostic results. Its Google Ads workflow supports actions with statuses such as Unverified, Tag inactive or Needs attention. Use the testing method appropriate to the action’s actual source; a website tag check does not verify every imported or later business event.
Keep the evidence precise: “Both measurements fired during this test” is different from “Two conversions received ad attribution.” Compare debug results, the business record and relevant reporting separately. Missing evidence is a reason to investigate, not a reason to invent a match.
Leave a definition your team can use next month
After a correction, repeat the relevant successful and unsuccessful cases. Save the approved definition, settings, change date and observations. Revisit the record when forms, confirmation pages, integrations or campaign goals change.
If the website accepts the request but your team cannot find or answer it, use our website inquiry handoff guide. Once you understand the conversion evidence, the Google Ads search terms audit helps assess whether queries fit the advertised work.
A measurement review can be discussed within Rank.Vegas’s digital advertising service, with access, implementation work and deliverables agreed in the scope. Email sales@rank.vegas with your website, advertised service, the action name and what you believe it measures. Leave passwords and private customer records out of the introductory message.