Quick Answer: Broad match doesn't burn budgets on its own. Dirty conversion data does. When smart bidding learns from form submits instead of qualified leads, it optimizes for form submitters. Fix the signal you're sending Google and broad match traffic quality changes.
Everyone Told You to Switch to Broad Match
Google reps pushed it. Blog posts endorsed it. The pitch made sense: let the algorithm find intent signals you'd miss with exact and phrase match. Feed it enough conversion data and it'll figure out who your customers are.
So you made the switch. Turned on smart bidding, set a tCPA, and waited.
A few weeks in, your search terms report is full of junk. CPCs are up. You're adding negatives all day and barely keeping up. The algorithm that was supposed to do the heavy lifting is spending your budget on people who have no business clicking your ad.
The instinct is to blame broad match. But broad match isn't the problem.
What Smart Bidding Is Actually Optimizing Toward
Smart bidding is a learning machine. It runs on one input: whatever you told Google was a conversion.
If your conversion action fires when someone submits a contact form, the algorithm goes out and finds more people who submit contact forms. Not buyers. Not qualified leads. Form submitters.
Broad match makes this worse faster. Wider reach means more impressions, more clicks, more data fed back into the system. But if the signal is wrong, more data just means the algorithm gets better at finding the wrong people.
This is what practitioners mean when they say you need “clean conversion data” or the right “tracking architecture.” The algorithm isn't broken. It's doing exactly what you trained it to do.
The Setup That Looks Fine But Isn't
Most accounts have a conversion action that fires on a thank-you page or a form submit event pulled from Google Analytics. That looks like proper tracking. The conversions show up in the dashboard. The campaign has conversion data to learn from.
But those conversions include:
- People who submitted a form and never answered the phone
- Duplicate submissions from the same person
- Bot fills and spam
- Leads that were immediately disqualified
Google doesn't know any of that. It recorded a conversion, and it's going to find more people who look like that conversion.
The result is a campaign that's technically “converting” but generating leads your client can't close.
Fix One: Audit What's Actually Firing
Before changing any bid strategy or match type, go into your conversion actions and verify what triggers each one.
Step 1: Check your primary conversion actions
In Google Ads, go to Goals > Conversions > Summary. Look at your primary conversion actions, the ones smart bidding is actively optimizing toward. Note the source for each one (Google Ads tag, imported from GA4, etc.).
Step 2: Test the trigger
Submit a real test lead on your landing page and watch whether the conversion fires in Google Tag Assistant or the real-time events view in GA4. Then check: does a conversion also fire if you navigate directly to the thank-you page URL without submitting anything?
If yes, your conversion is counting page views, not submissions.
Step 3: Fix or replace the conversion action
A form submit conversion should fire on a confirmed form completion event, not a page load. If you're using GA4, make sure the event is tied to a form_submit trigger in GTM that fires only on actual submission, not on URL change.
Fix Two: Send Google What Happened After the Lead
The biggest upgrade you can make is offline conversion tracking.
Instead of letting Google count every form fill, you push conversion data back to Google after something real happens. A lead gets marked qualified in the CRM, a call gets booked, a deal closes. You tie that outcome back to the original click using the GCLID that was stored when the person first came from the ad.
Step 1: Store the GCLID at form submission
When someone submits a lead form, capture the GCLID from the URL and store it alongside the lead record in your CRM. This is the bridge between ad click and business outcome.
Step 2: Define what counts as a qualified conversion
Work with your client to define the trigger. Common options: lead marked “qualified” in CRM, appointment booked, deposit paid. This is your conversion event.
Step 3: Import the conversion back to Google Ads
When that event fires, upload the GCLID plus conversion time plus conversion name back to Google via the API or a CSV import. Google matches it to the original click and counts it as a conversion.
Now smart bidding knows what a real customer looks like. Not just a form submitter.
What Changes When the Signal Is Clean
Once qualified offline conversions are feeding the algorithm, a few things shift.
The search terms report gets quieter. Not because broad match got tighter, but because the algorithm is matching based on who actually converted. Your tCPA becomes meaningful. Previously it was a target applied to a noisy mix of junk leads and real ones. With qualified signals, the algorithm is chasing the same outcome you are.
Broad match starts doing what it was supposed to do: finding demand you didn't know existed, from searches that wouldn't have matched on phrase or exact.
The Honest Caveat
Offline conversion tracking takes setup time and requires cooperation from your client's CRM or sales process. It's not a one-afternoon fix.
But if you're running smart bidding without it, you're asking the algorithm to optimize for a goal that isn't your actual goal. Every dollar of budget you put behind broad match before fixing the signal is a dollar that teaches Google the wrong lesson.
Want to Set This Up Step By Step?
The OCT Setup Checklist walks through the full offline conversion tracking process, from GCLID capture to CRM setup to importing back to Google Ads. It's free at freak.marketing/members/downloads/oct-setup-checklist.