Can smaller Google Ads budgets keep some leads flowing to nonpremium marketplace users in each city?

Smaller budgets can keep campaigns running at a lower spending level, but they cannot reliably give each nonpremium marketplace user a small, steady supply of leads. A budget controls how much you spend seeking visitors. The marketplace needs a separate, enforceable rule for who receives the inquiries those visitors create.

If you need to make each city's spending decisions separately, keep that control at campaign level. Before consolidating campaigns or changing bidding, establish whether the shortage is in incoming inquiries, delivery to particular users, or your ability to see either one. Those problems call for different actions.

Two cities, eight leads, two very different results

Suppose your marketplace has four eligible nonpremium users in each of two cities. For this illustration, a lead means a genuine customer inquiry delivered to one suitable provider; the users stay eligible and on the same plans throughout the week. Each inquiry could have been served by any of the four providers in its city.

Both cities receive four leads. Looking only at the totals, the campaign arrangement seems to be doing its job:

City A has enough inquiries to have reached all four users in this example. Its distribution leaves half of them with no experience of the benefit, while one receives most of it. Cutting City A's ad budget to stop that user receiving so much would also reduce opportunities for the two users who received nothing.

More traffic might eventually reach them. It might also give the same recipient more leads. The budget has no instruction saying, “This provider has had their introductory benefit; offer the next suitable inquiry to someone else.”

If the marketplace controls the handoff before an inquiry reaches a provider, the first change to examine is how it distributes City A's existing suitable inquiries. Recording recipients after delivery does not create that control. Redistributing those suitable inquiries can improve the intended experience without buying another click. It does not establish that one lead per week is the right nonpremium allowance, or that withholding more would increase subscriptions. Those are product decisions; lead counts alone cannot settle them.

Now change one fact: City B receives no inquiries. Redistribution cannot create a lead there. You need to inspect acquisition or accept a quieter period. And if City A's inquiries require a specialty that only its busiest provider offers, the apparent allocation fix disappears too. A lead is useful only if the recipient can serve it.

Build the count that can reveal the difference

Start with the marketplace's intake and delivery records, using a period that matches the benefit you intend users to experience. A week is only the illustration above. Define what qualifies as a lead and which users are eligible before counting.

For a small marketplace, existing form records, CRM entries or sent-lead records may be enough for a manual reconciliation. You need to connect:

• A distinct inquiry ID and the city where the customer needs the service.
• Whether the inquiry is valid and suitable, and when it arrived.
• Each actual recipient, when delivery occurred, and that recipient's plan and eligibility at the time.

Then take the eligible-user list for each city and count deliveries against it, retaining users with zero deliveries. An export containing only people who received something cannot reveal the missing half of City A. If eligibility changes during the period, retain those dates so a user who joined yesterday is not treated as having waited all week.

Count inquiries and deliveries separately. If one inquiry goes to three providers, that is one inquiry and three recipient deliveries—not three independently acquired leads. In the table, each inquiry had one recipient, so those counts happened to match. Include unresolved and undelivered inquiries too: they may explain why intake looks healthy while users receive nothing.

This count answers whether users received the benefit, regardless of whether a lead came from ads, organic search or elsewhere. Evaluating paid acquisition needs a different connection: the inquiry must be attributable to the relevant paid traffic. Do not divide ad spend by every marketplace lead and call the result paid cost per lead. A city-named campaign also does not establish the service city of a particular inquiry; use the customer's service requirement.

If recipient history does not exist, there is no reliable historical distribution to optimize. Start recording it prospectively at intake and delivery, using existing records where possible. That can happen while budgets stay reduced or campaigns are paused. A new log will explain future delivery; it will not recover recipients the marketplace never recorded.

Why half the budget can feel like no leads

For a Search campaign using Maximize Clicks, Google seeks clicks within the budget. It does not optimize for a chosen number of leads. Click prices and available traffic also vary, so €10 buying ten clicks on one day does not make €5 an order for five clicks on the next. Google's own Maximize Clicks guidance describes the click objective and warns that results fluctuate.

Even if you did receive exactly half the clicks, the leads would not arrive in neat halves. Suppose, purely for illustration, each independent click has the same 10% chance of producing a lead. Ten clicks have about a 35% chance of producing zero leads; five clicks have about a 59% chance. The calculation is 0.9¹⁰ versus 0.9⁵. The assumed rate is not a benchmark or an estimate for your account.

This explains how a smaller stream can have more empty stretches without any deterioration in the assumed conversion probability. It does not diagnose a particular stop. If clicks disappeared, inspect ad delivery. If clicks continued but only the Ads conversion column went quiet, inspect actual inquiries and measurement before declaring that leads stopped.

Also check the campaign type before applying this explanation. Performance Max uses conversion or conversion-value bidding; it does not offer a Maximize Clicks configuration. Google's PMax bidding instructions describe those choices. A mixed Search/PMax account therefore cannot be diagnosed as one Maximize Clicks campaign, and a budget cut alone does not show that a conversion-based bid strategy has restarted learning.

Choose the advertising control for the job it can do

Smaller, separate city budgets make sense when you need to keep spending decisions separate and can tolerate uneven lead arrival. They preserve a financial boundary between cities; they do not guarantee that either city spends its budget or produces a minimum number of leads.

Remember that an average daily budget is an average. For most campaigns, the daily spending limit is twice that amount, and the day you reduce it still uses that day's highest average daily budget to calculate the daily limit. Check the budget report when money is tight; lowering the setting is not an immediate exact cap on today's bill. See Google's spending limits and budget-change rules.

A shared budget allows compatible campaigns to use one pool, moving unused budget to campaigns that can use it. That flexibility is useful when you accept that one city may receive more advertising than another. It does not reserve a lead supply for every city. Returning to the example, extra results in City A would not compensate the City B users for a week with none. Google excludes Performance Max from shared budgets.

One campaign with city-named ad groups also gives up the former separate campaign budgets and location settings. Naming an ad group after a city does not recreate them. Google explicitly recommends separate campaigns when you need different budgets or location targeting. Consolidate only if sharing those controls fits the business requirement.

Pausing is appropriate when you need to stop buying more traffic from a campaign. It creates a deliberate break in acquisition, so it cannot maintain a continuous trickle. Google documents that pausing stops the campaign's ads from showing. People who clicked earlier may still inquire later; pausing does not cancel their visits or control who receives their leads.

A CPC limit or a different bid strategy changes how you compete for traffic. Neither assigns an inquiry to a marketplace user. Do not use a bid-strategy change as the proposed cure for the 3, 1, 0, 0 distribution.

Measurement and allocation have different jobs

If most real leads are missing from Ads, first check what is being recorded and which report includes it. In Google Ads, primary actions generally appear in Conversions when their goal is used, while secondary actions appear in All conversions. Secondary actions normally stay out of bidding, with a custom-goal exception. That distinction lets you separate observation from optimization without pretending an event did not happen. See Google's primary and secondary conversion guidance.

For a tracked action, also allow for the time between the ad interaction and the conversion. Google's Days to conversion procedure uses an older date range to examine that delay. It cannot reveal missing recipients or repair events that were never recorded. A gap between Ads and the marketplace is something to reconcile, not evidence that leads were deliberately hidden or that the campaign needs more budget.

Reliable outcome measurement can support a later decision about conversion-based bidding. The marketplace's delivery rule must still decide which eligible users can receive each lead. Accurate measurement does not require unlimited nonpremium delivery, and limiting delivery does not require inaccurate measurement.

What if you cannot control delivery?

Before choosing marketplace allocation as the answer, verify three capabilities: you can identify recipients, determine their subscription status, and actually route or withhold a lead before it reaches them. Records alone satisfy only the first part.

If inquiries pass through a central inbox before dispatch, an affordable first step may be a manual check of suitability, plan entitlement and prior deliveries before sending the next one. Record the delivery and ensure every dispatch route uses that check. Define what happens to excess inquiries—such as a suitable premium recipient or another agreed customer-serving route—rather than letting them disappear. This is feasible only if the marketplace controls that handoff.

If visitors contact providers directly, the marketplace may have no such handoff. A spreadsheet or lower budget cannot enforce a recipient allowance. You can keep a smaller city budget to limit financial exposure and accept uneven delivery, or change the contact path so allocation becomes possible. Until then, the nonpremium benefit must describe what the service can actually deliver rather than promise a regular allocation it cannot enforce.

For City A, confirmed suitable inquiries plus unequal deliveries point first to distribution. For a city with no inquiries, examine the acquisition and measurement evidence before spending more. With neither dependable records nor a controllable handoff, protect the budget and build the missing capability before treating “some leads for each user” as an advertising setting.