Google Ads for lead generation: three priorities before you change the budget

Choose the three priority checks

Lead-generation advertising connects two processes that often live in different systems. Google Ads records an attributed action. A person or a sales workflow then decides whether the enquiry can become useful business. A report can describe the first process accurately while saying very little about the second. That distinction matters when a campaign produces more forms, fewer appointments or a lower reported acquisition cost. Before treating the movement as a success, establish what the advertising account actually counted and what happened after the enquiry arrived.

Start with three priorities: the conversion definition, the intent and service scope of the traffic, and the working contact route. The first prevents a misleading denominator. The second checks whether the offer reaches people the business can reasonably help. The third checks whether interested visitors can actually contact the team and receive a response. These priorities give measurement, advertising and operations separate responsibilities. They also prevent every disappointing result from becoming an immediate bid or budget change.

The order is practical rather than absolute. A known broken enquiry form needs attention immediately. In an ordinary performance review, however, agreeing on the measurement first makes the later comparisons intelligible. You can then identify which findings are supported by account data and which need a website test or an answer from the sales team.

Define what the business calls a lead

Write a short definition before opening a performance table. For a commercial cleaning company, a lead might mean a submitted request for a recurring office-cleaning quotation. A recruitment application, supplier approach and request for household cleaning are different contacts. They may all arrive through the same website, but counting them together would answer a broader question than the owner intended. The definition should describe the action and the business context without requiring the reporting tool to infer either from a campaign name.

Separate an enquiry from a later judgement about it. A correctly submitted quotation request is an observable event. Whether the requester has a suitable budget, belongs to the service area or agrees to a contract can require other evidence. Calling the initial form a lead is reasonable if the team understands that boundary. Calling every recorded form a qualified opportunity would attach a conclusion that the tracking may never have established. The label in a report should be no stronger than the evidence behind it.

Also record the contact routes. A business may accept forms, telephone calls and appointments booked through an external service. Those routes can have different tracking and handling arrangements. A request for the total should explain which routes are included; a request about a specific form should select that form's conversion action. The account's broad Leads measure is not a substitute for defining an individual contact route when that is the question being asked.

A useful definition remains stable across weekly reviews. If the business changes it, record the effective date and explain why comparisons spanning that date require care. Otherwise a tracking reclassification can look like a marketing improvement even though the underlying enquiries have not changed.

Inspect primary conversion actions

Read the current action list rather than relying on the conversion names you remember from setup. Identify the primary actions, the category assigned to each and the action requested by the report. A quotation form, telephone conversion and imported outcome can coexist. They need not be an error. What matters is whether the selected set describes the intended performance measure and whether the account owner understands the signals being used.

The lead-generation conversion-setup audit in ppctor deliberately returns a manual review. It lists the primary and secondary roles without pretending that every lead account should have one identical configuration. A business with separate consultation and installation enquiries has a different decision to make from a business that tracks a page view and a successful contact form. The finding provides a readable inventory for that decision. Its review state does not prove that the setup is broken.

For the broad reporting measure, Leads aggregates the primary lead-category actions. It does not split the answer into a hierarchy of lead stages merely because Google exposes several category names. When you want a particular action, ask for it by name. The broader Conversions measure includes all primary conversions, so it can contain actions outside the lead categories. These are different denominators and should remain visibly different in the answer.

Secondary actions are excluded from the default primary aggregate. An explicitly requested secondary action can be examined separately, but it should not quietly enter the headline lead total. Likewise, several primary actions are added as configured; the reporting tool does not repair duplicate tracking by guessing which action represents the same person. Reviewing the setup is a separate job from reporting the recorded total.

Separate conversions from distinct people

A conversion count is not automatically a count of unique prospective customers. One person can make more than one contact, use different contact routes or trigger separately configured actions. Attribution and the conversion action's counting setup also influence the reported metric. A report titled “people who contacted us” requires a person-level definition and supporting evidence. A report titled “primary lead conversions” describes the account measurement without introducing that stronger claim.

Consider a fictional business that receives a quotation form and a follow-up telephone call from the same visitor. If both are primary and both are recorded, their inclusion in the aggregate may be intentional. The business may care about each contact route. That still does not establish two different people. Conversely, deciding that one contact should be ignored requires a measurement policy and implementation work; it is not a safe conclusion for an assistant to make from two action names.

Review the counting setting alongside the actual event trigger. A setting intended for enquiries cannot fix a form event that fires before submission succeeds. Nor can it establish whether two separate implementations describe the same contact. Test when the event occurs, inspect the defined conversion actions and ask the tracking owner to explain any overlap. Keep the performance report intact while that investigation happens so its meaning remains reproducible.

The audit can expose eligible counting settings for review, but eligibility and a recommended setting do not prove the entire tracking implementation. Use the conversion-counting guide for that narrower task. In lead generation, the important reporting habit is to name the counted action and avoid translating it into unique customers without the necessary evidence.

Understand what the call measurement records

Telephone enquiries deserve their own explanation because several different observations can be described casually as a call. Google documents measurements for calls from ads, website calls, clicks on telephone links and imported call outcomes. A click on a number is different from a completed conversation. Some call-conversion setups also use a minimum duration. Read the actual setup before explaining what the count means; Google's call-conversion documentation describes these distinctions.

In ppctor, primary call conversions can be reported as Calls, and recorded primary call value can also be available. A call conversion with value does not automatically represent money received. The account may assign a value for bidding or use an imported outcome. Say “recorded call conversion value” when that is the evidence. Reserve a claim about completed sales for a measure that actually records them and for a scope that makes the comparison meaningful.

The business process adds questions that the advertising metric cannot settle alone. Was the call answered? Was it about the advertised service? Could the caller be helped in the required area? Did a receptionist forward it correctly? An account report should not claim to know those answers from a conversion category. Ask the telephone or sales owner, then keep their findings clearly separate from the provider's recorded count.

When comparing a call measure with Analytics, select a specific corresponding event and explain what it observes. A telephone-link click can be useful evidence about contact intent, but presenting it as a confirmed conversation would misdescribe the source. The purpose of a comparison is to understand measurement, not to make unlike events agree by changing their labels.

Select the corresponding Analytics event

Google Analytics can help examine the website side of the enquiry, provided the event is identified. Google's recommended generate_lead event is one possible implementation for a generated lead. Sites can also use their own event names. The existence of a documented recommendation does not establish what your site sends, whether it sends it correctly or which contact route it represents.

Ask ppctor to list the observed events for the relevant period when the name is unknown. The assistant can suggest a likely correspondence from the names, but the selection needs confirmation. An event called “contact_submit” may sound suitable while still describing a different form. The tracking owner should explain the trigger if the meaning is uncertain. Absence from a dated observed-event list also does not prove that the implementation has never existed.

Once selected, the comparison can show primary Ads Leads against the confirmed event, or a named Ads conversion against a particular event. Preserve the period and the requested traffic scope. All-traffic website events include contacts outside Google Ads unless the request applies a narrower population. Such a total can be informative, but its difference from an advertising-attributed total does not by itself establish a tracking failure.

Give the two series descriptive labels and keep attribution differences visible in the explanation. If you wanted the form in one campaign, do not silently substitute every website lead event. If the selected field combination cannot be returned, the response should explain the unavailable evidence instead of supplying a convenient broader total. A precise question sometimes needs clarification before it needs another chart.

Keep offline outcomes visible and distinct

Some enquiries become useful only after a salesperson reviews them. An imported conversion action can bring a later outcome into Google Ads when the business has implemented that process. The reporting tools can inspect recorded offline or imported actions and their available metrics. They do not gain unrestricted access to the underlying customer database simply because an action has an offline source. Account evidence remains account evidence.

Use the action's name and configured role to describe it. A primary imported contract outcome can be included in the broad primary aggregate. It may also belong to a lead-related category. This means “offline”, “lead” and “primary” are overlapping descriptions rather than three independent totals to add. Ask for the selected action when you want to examine the imported outcome separately, and avoid summing categories that describe the same records.

An absence of recorded outcomes has several possible explanations that require investigation. The business may have had no such outcomes, the import may not have run, or the reporting period may precede the completed sales process. The tool should report the available count and scope. It should not label every missing imported result a rejected lead or a lost sale without evidence from the people operating the import.

Keep the initial-enquiry report and the later-outcome report understandable on their own. A weekly acquisition review and a longer sales review can complement each other without pretending they are interchangeable. Agree who checks the import schedule, who validates the business meaning of the action and who reviews recent cohorts after enough time has passed for outcomes to arrive.

Use cost per lead with a defined denominator

Cost per lead is spend divided by the selected lead count. The calculation is simple; choosing the denominator is the consequential part. All primary conversions, primary lead conversions, primary calls and one named form can produce different ratios from the same spend. Choose the ratio that answers the decision, label it accurately and keep the same definition in the comparison period. A cheaper value calculated from a broader action set does not demonstrate cheaper acquisition of the original enquiry.

For an invented example, a campaign spends 900 currency units and records 30 primary form leads. The cost is 30 per recorded form lead. If the same report instead includes 15 other primary actions, dividing by 45 produces 20 per primary conversion. Both calculations can be mathematically correct while answering different questions. Reporting the latter as the former would mislead the person deciding whether to increase investment.

Set the business's acceptable range using its own economics and sales evidence. A specialist consultation, an inexpensive service and a long procurement process cannot share a universal profitable lead price. If the account records assigned lead values, distinguish those from collected revenue. A conversion-value-to-cost ratio can be useful for the configured values without proving the business received that amount of money.

Zero leads and unavailable lead data also need different treatment. With positive spend and a verified zero denominator, cost per lead is undefined; it is not zero. With an unavailable read, even that conclusion is unsupported. A good answer shows the measured components, explains the ratio's state and identifies the next evidence needed rather than manufacturing a favourable number.

Review the service intent behind the traffic

After confirming the measurement, examine whether the advertising offer matches the enquiries the business wants. Campaign and ad-group names are useful navigation, but the actual service, advertisement and available search evidence matter more. A company selling managed IT support may receive students researching technical topics, job applicants and people requesting a single inexpensive repair. The presence of those possibilities does not prove they account for the spend; it gives the reviewer specific questions to investigate.

Use returned data to select a review population. For example, ask which Search keywords spent above an agreed amount with no primary lead conversions over a completed period. That creates a candidate list, not a universal instruction to pause every result. A keyword may have a long decision cycle or contribute to a contact route recorded elsewhere. Check the offer and the period before treating the filtered list as a diagnosis.

Search terms can provide more direct evidence of language and intent when available. Keep the coverage limits visible: a returned search-term report should not be described as every search behind every click. Read the actual examples and relate them to the service definition. A word that appears irrelevant in isolation can be part of a valuable request, particularly when the service has technical or regional terminology.

The useful output is a short set of findings with reasons: an unsupported service request, an ambiguous advertisement, a candidate exclusion or a need for more data. Distinguish each finding from a creative suggestion. The assistant can brainstorm more precise wording without calling a research API, but a claim that one phrase caused measured waste needs the relevant account evidence.

Inspect exclusions without inventing irrelevance

Negative keywords are one way to keep clearly unwanted intent away from a Search offer. They are also capable of blocking useful requests when chosen too broadly or placed at the wrong scope. Begin with the business definition and the available evidence rather than a generic list of words that every lead account should exclude. “Training” may be irrelevant for a repair company and central to a professional education provider.

The current negative-keyword audit checks whether enabled Search, Shopping and Performance Max campaigns have negatives through supported campaign, ad-group or attached-list sources. That is a presence check. A passing result does not certify that the negatives are appropriate or complete. A missing result does not quantify wasted spend. The audit points to a review task, and the account's actual traffic and offer determine what should follow.

Inspect both the proposed text and its target. An exclusion intended for a recruitment campaign can be wrong for a customer-acquisition campaign, and an account-wide choice can affect more than the immediate enquiry. Review shared relationships where they apply. A readable proposal should name the campaign or group and the exact action so that the owner can evaluate those consequences before any supported edit is sent.

A useful sequence is to collect candidate terms, explain why each conflicts with the service, check the intended scope and request a proposal for the agreed changes. Preserve terms that remain ambiguous for human review. See the negative-keyword workflow for the more specific implementation boundaries. The lead-generation goal is better intent alignment, not a larger negative list for its own sake.

Connect location settings with service coverage

Service geography can be a commercial constraint rather than just a report dimension. A contractor may work within a defined area; a consultancy may serve clients remotely. Write down the area the offer can support before reviewing targeting. Then distinguish the campaign's configured targets from the locations observed in a performance report. Those views answer related but different questions and should not be substituted for each other.

Google's advanced location guidance distinguishes presence from presence-or-interest targeting. The setting influences the population an advertiser is trying to reach. Location identification uses provider signals and is not guaranteed to be perfectly accurate. A presence setting is therefore not a promise that every resulting enquiry belongs inside a strict service boundary.

Ask for the current settings of the selected campaign before proposing a change. If the business specifically wants people in its service area, that intent should be explicit. If it accepts enquiries from people planning a move or arranging work for a property elsewhere, interest in the area can have commercial relevance. The right choice depends on the service; applying one default to every lead advertiser ignores that difference.

Evaluate performance with the same discipline as other segment reports. A small location row with no leads may need more time, and a large row can still contain unsuitable requests that the account metric does not identify. Bring any confirmed out-of-area enquiry evidence into the review as business context. Do not infer a visitor's eligibility from a campaign label or claim that an Ads read supplies a complete customer address history.

Keep separate offers understandable

A single business can advertise several services with very different enquiry values. Emergency assistance, planned maintenance and a large installation quotation may all reach the same office, yet they have different response expectations and sales cycles. An account-wide cost per lead can hide that mix. Organise the review around the relevant offer and compare like populations before deciding that one campaign should inherit another campaign's budget.

This does not require splitting every possible phrase into a new campaign. The practical question is whether the current structure lets the team understand the offer, budget and conversion measure. A group covering one coherent service can be easier to review than a collection of unrelated requests under an attractive generic name. Conversely, excessive fragmentation can leave each row with too little evidence for a meaningful performance decision.

Read the advertisement and landing page together. If the advertisement invites a free consultation but the page opens with an expensive purchase requirement, the enquiry path may confuse visitors. If the offer is deliberately selective, make that selectivity clear rather than judging its smaller response volume against a much broader offer. Creative ideas can help communicate the distinction, but the assistant should not attach measured uplift to a rewritten headline without evidence.

When the owner asks for a comparison, name the campaigns and the selected action set. “Installation quote forms versus maintenance quote forms” gives the team a workable decision. “Best leads” without a definition invites the report to infer commercial quality it cannot observe. Preserve the business distinctions while keeping the broad Leads total available for questions that genuinely concern the aggregate.

Test the actual contact route

The contact route is the third priority because a valid click and an eligible advertisement do not establish that the visitor can submit an enquiry. Test the advertised destination in a browser. Follow the actual route from the landing page to the form, appointment service or telephone option. Check it on the devices that matter to the audience rather than assuming the desktop experience describes every visitor.

A form test should establish more than whether fields appear. Can the visitor understand the request? Does submission succeed? Is the confirmation truthful? Does the business receive the enquiry in the intended destination? Use an agreed test procedure with the website and sales owners so that test contacts are recognised and handled appropriately. Avoid adding real customer information to a public Slack thread while explaining the findings.

Look for points where the service promise and the contact process diverge. A form might require an unavailable appointment date, reject an ordinary telephone format or omit the service advertised. A booking page might display no appointments after the ad invites immediate availability. These are concrete observations for the website owner. They cannot be diagnosed reliably from a falling conversion rate alone, although that movement can justify inspecting the journey.

Keep the tracking check adjacent to the functional test. Successful submission without a recorded event and a recorded event without successful submission are different problems. Document which one you observed, when you tested it and which route was involved. The distinction gives the next owner an actionable task instead of a vague instruction to improve the landing page.

Distinguish destination findings from form tests

A destination-policy finding and a live enquiry test are complementary evidence. The current Links command reads Google's published destination findings across the supported advertising surfaces. It can identify provider-reported problems and preserve which surfaces were read. It does not crawl the entire website or submit its forms. A clean provider-finding result therefore cannot certify that the business's contact process works today.

The distinction also matters when a site changes. A newly broken form may not yet have a corresponding provider verdict. An older destination issue can remain relevant to policy review even after a human observes that the page loads. Use each result for the job it performs. The policy evidence helps explain advertising eligibility; the browser test helps establish the visitor's current experience.

If a provider surface cannot be read, the answer should name the missing coverage. Do not turn that absence into “no problems found”. Similarly, do not count every affected advertisement as a different broken website. Several ads can point to one destination, and one site can have several distinct contact routes. The useful handoff identifies the actual URL or route, the reported issue and the owner who can investigate it.

For a fuller explanation of the command's evidence, use the destination-check guide. In a lead-generation review, pair that provider check with an explicit live contact test whenever the enquiry path is in doubt. This avoids both false reassurance and unsupported claims that every delivery problem was caused by the form.

Include the team that handles enquiries

An advertising review should include the people who receive the contacts, especially when the recorded lead volume and the business's experience diverge. Ask for a short, structured account of what changed: response capacity, opening hours, routing, unanswered calls or the suitability of the requests. These observations provide context for the Ads results without pretending that the assistant independently inspected the business's telephone system or customer records.

Keep the questions specific. “Were installation enquiries answered during the promotion?” is easier to verify than “Are these good leads?” “Did the new form reach the same inbox?” can uncover a routing problem without requiring an advertising change. “How many requests concerned a service we do not provide?” may justify an intent review when the sales owner can supply an appropriately scoped summary.

Handle that summary at the right level of detail. A team can discuss aggregate categories and confirmed operational issues without copying names, addresses and personal messages into an account channel. The reporting tool's role is to analyse the available advertising measures and incorporate stated business context, not to create an unnecessary public copy of the contact database.

Agree the response owner before increasing enquiry volume. If the business can handle only a certain level of urgent work, spending more may create contacts it cannot serve. That is an operational constraint to consider alongside the account data. It does not mean the conversion count is wrong, and it does not justify labelling the entire campaign unsuccessful. It identifies the condition that must change for additional advertising to be useful.

Allow enough time for the sales process

Select a period that fits the decision. Yesterday's completed spend can help monitor a sudden disruption. A longer window may be necessary to examine a service with a slow enquiry or sales process. A current partial day and a completed prior day are different populations. State the dates and the account context so that the reader can understand why a recent figure may still change.

Do not confuse an acquisition window with an outcome window. A lead generated this week may produce an imported sale later. Looking for that sale immediately can understate the eventual result. Conversely, an imported outcome recorded this week can relate to an earlier advertising interaction. Preserve the requested date basis rather than moving dates until the totals appear to agree.

Use a fair comparison when days of the week or operating schedules matter. A business that handles enquiries during working hours can have a different pattern from one offering emergency service. A holiday closure, promotion or website release belongs in the explanation if it is confirmed. It is context for interpreting the data, not permission to claim causation from a single coincident movement.

Record the timing of configuration changes too. If a new primary action started halfway through the period, the aggregate before and after does not represent a completely stable measure. Report that boundary and select an appropriate follow-up window. The team can still monitor spend in the meantime, but should avoid a confident lead-efficiency verdict based on a denominator that changed during the comparison.

Work through a fictional weekly review

The following illustration is invented and is not a customer result. A business called Cedar Office Services reviews two Search campaigns over the same fourteen completed days. Office Cleaning spends 1,200 currency units and records 40 primary quote-form leads. Window Cleaning spends 800 and records 10. The first question is whether those named actions represent the same kind of submitted enquiry in their respective services.

With the definitions confirmed, the ratios are 30 and 80 per recorded quote-form lead. This makes Window Cleaning a candidate for further review, not an automatic instruction to pause it. The services may have different contract economics. The account also contains telephone conversions, but the question selected forms; they should not be silently added to make one campaign's ratio look more attractive.

The reviewer checks the service intent and finds returned examples that request residential work in the commercial campaign. The reviewer then asks the sales team whether that mismatch appeared in actual enquiries. Separately, a mobile test reveals that the window-cleaning form sends a confusing confirmation after successful submission. These observations create two specific tasks: review the evidenced intent mismatch and fix the contact-page message.

Neither task establishes that the entire difference between 30 and 80 has been explained. The next report uses the same form-action definitions, keeps the comparison period visible and records when the website correction happened. If a supported exclusion is proposed, the campaign target and exact term are shown for approval. The business can then evaluate a bounded change rather than allowing an assistant to rewrite the account based on a headline ratio.

Ask focused questions in Slack

Once the service and measurement are understood, Slack can make the review easier to carry out. Ask “Show primary lead conversions and spend by campaign for the last fourteen completed days” when you want the broad acquisition picture. Ask for a named quotation action when the review concerns one form. Ask for Calls separately when the telephone route is the decision. Ordinary language can express each of these scopes without exposing query syntax to the team.

The assistant's reporting framework discovers available fields, validates the requested plan and retrieves the selected data. It can carry forward an explicit scope in a follow-up, but a missing business definition still needs a question. “Show the same campaigns for the previous period” is a presentation of a preserved population. “Now compare with our website leads” needs a corresponding Analytics event and an agreed traffic scope before the answer is meaningful.

Creative work is a separate conversational use. Ask for clearer form copy, a headline that distinguishes commercial work or a description that sets expectations for response. Such requests do not inherently need Keyword Planner or another account read. If you ask for measured keyword volume, recorded performance or a live edit, the appropriate tool evidence becomes necessary. Keep creative suggestions visibly distinct from measured recommendations.

For broader examples of question structure, see asking account questions in plain English. A good lead-generation request names the outcome, the offer and the period. A good answer then reports the available evidence and identifies any remaining business question rather than filling the gap with a plausible story.

Use reports and charts for the decision

A campaign table often answers a review question more directly than a chart. It can keep spend, the selected lead count and the corresponding cost visible beside each campaign. A chart helps when the question concerns movement over time. Choose the format for the decision and keep units clear. Spend and lead counts are different measures; putting them together should not erase that distinction or imply that they can be added.

Request a daily chart when daily detail matters. For longer periods without an explicit daily requirement, the current native rendering flow can use a coarser breakdown to keep a single chart readable. Native charts have bounded series and point counts. If explicit detail needs consecutive panels, the answer should explain that presentation rather than suggesting the date range was split into unrelated reports.

When a returned dataset already contains the necessary points, the renderer can reuse it for the requested visual. A new segmentation or an unreturned period needs new evidence. This distinction keeps a follow-up such as “make that a line chart” from being treated like an unrelated data investigation while still preventing the tool from inventing daily points from an aggregate total.

Use saved Reporting for a stable recurring review when that is useful, with a deliberate source, target, period and schedule. A scheduled account summary complements the specific questions asked in conversation. It does not replace the manual assessment of enquiry suitability or the live contact test. The reporting guide explains those workflows without treating every presentation as a new advertising action.

Review a supported change before execution

A finding should become an edit only after the intended action is clear. “These enquiries are unsuitable” is business context, not a complete mutation request. The next step may be a more precise advertisement, a reviewed exclusion, a location-setting change or a website correction. The supported action depends on the asset and setting. The existence of an audit finding does not mean the application can automatically fix every underlying cause.

For a conversational advertising edit, ppctor prepares a proposal before sending the live change. Read the exact target, any relevant parent context and each operation. The campaign or ad-group name should be understandable without forcing the owner to interpret internal resource identifiers. If the proposal includes a dependent creation sequence, the steps should explain what will be created and what existing scope will receive it.

Confirmation authorises the reviewed execution, not an open-ended optimisation programme. The current proposal expires after fifteen minutes, and relevant settings and authorisation are checked again before execution. A visible result should distinguish a verified change from an acknowledgement or a result that could not be fully verified. An uncertain outcome should not be blindly repeated merely because the desired message has not appeared.

After a supported change, revisit the same business measure at an appropriate time. Record the changed setting and any concurrent website or handling work. This makes the follow-up interpretable without claiming the edit alone caused every later movement. The confirmation workflow gives the detailed review process; lead generation adds the responsibility to keep the enquiry definition and operational context stable.

Build a repeatable review routine

Use the three priorities as a compact routine rather than a sprawling checklist that nobody finishes. Start by confirming the selected primary actions and any measurement changes. Review traffic against the actual service and area. Then check the contact route and the team's capacity to handle the resulting enquiries. Each part should end with a finding, an owner or a clear statement that no action is justified by the current evidence.

Keep a small decision record: the period, selected action set, important observations, agreed changes and next review date. This allows a colleague to repeat the analysis without rebuilding the meaning from a long message thread. It also helps distinguish an advertising edit from a tracking repair or an operational adjustment. Those activities can occur together while still needing different owners and verification.

Set monitoring around a measure the team can respond to. A sudden absence of primary leads can justify checking tracking and the contact route. A spend threshold can identify exposure before the review happens. Neither alert supplies a complete diagnosis, and unavailable data should not become a verified zero. Choose thresholds from the business's normal activity and decision needs rather than copying another advertiser's numbers.

Escalate to deeper analysis when the evidence calls for it. An unexplained form discrepancy needs event and submission checks. A service mismatch needs traffic and offer review. An increase in unanswered calls needs the telephone owner. By keeping those responsibilities distinct, the account review remains useful even when its next action belongs outside Google Ads. The goal is a working path from relevant interest to a handled enquiry.

Lead-generation questions

Does a lower cost per lead always mean better performance?

No. Confirm the selected actions, service scope and business economics. A broader conversion set can lower a ratio without improving acquisition of the intended enquiry.

Does ppctor separate different lead stages automatically?

The broad Leads measure groups the primary lead categories. Ask for a named action when you need a specific recorded outcome. Business quality still needs evidence that actually records it.

Can primary calls have conversion value?

Yes. Recorded primary call value can be reported, but its meaning depends on the configuration. Assigned value is not automatically collected revenue.

Can Ads Leads be compared with a website event?

Yes, with the corresponding Analytics event selected and its scope understood. The assistant can suggest a likely event name; confirmation establishes the intended comparison.

Does the Links command prove the enquiry form works?

No. It reports Google's published destination findings. A live browser and submission test is a separate check of the contact route.

Can the assistant decide whether every enquiry was suitable?

Not from an advertising count alone. Use the available recorded outcomes and a scoped summary from the people handling enquiries. Do not treat a category name as evidence of individual customer quality.