Lead Gen News: Late October 2026 - Google's LSA Merger, Meta's Product Browsing Deadline, and New Channel Priority Controls

Five changes across Google and Meta this week directly affect NZ service businesses running paid lead generation. Google is retiring its standalone Local Services Ads dashboard and migrating LSA campaigns into Performance Max, with accounts receiving 14 days’ notice before their migration runs. Meta will automatically enable product browsing inside existing ads on 28 October unless you opt out first. New channel priority controls let you cap the share of daily budget flowing to Display Network and Search Partners. A Customer Match data pipeline change lands on 16 November. And a new Sequenced Events goal in Meta lead campaigns offers a way to qualify leads at the optimisation stage, though it remains undocumented.

Here is what changed, why it matters, and what to do before November.

---

Google Is Retiring the Standalone Local Services Ads Dashboard

This is the biggest structural change for service businesses currently running Local Services Ads.

Google is folding LSAs into Google Ads as a pay-per-lead Performance Max campaign. The standalone LSA interface, including its separate dashboard, category-level reporting, and manual cost-per-lead bidding, is being retired. Accounts migrate in phases, with Google providing 14 days’ notice before each migration runs.

The billing model stays the same: you pay per lead rather than per click. Ads continue to appear on Search and Maps. Campaigns remain keywordless. What changes is the management environment, the bidding system, and where your historical data lives after migration.

What you lose when your account migrates

The manual per-category cost-per-lead targets are gone. Google replaces them with a single campaign-level Target CPA set by the algorithm. If you have been using category-level CPL targets to separate high-value service types from lower-value ones, that granular control disappears.

For a business where an emergency call-out is worth $800 and a routine maintenance enquiry is worth $180, those are very different leads. The standalone LSA system let you set a different CPL ceiling for each category. The PMax version does not. You set one Target CPA across the whole campaign and the algorithm distributes budget across your service types as it sees fit.

The historical performance data in the standalone dashboard does not automatically transfer. When your account migrates, the old interface is gone. Lead history, dispute records, monthly spend by category, and cost-per-lead averages by service type disappear with it unless you export them first.

What to do before your account migrates

Export everything from the standalone LSA dashboard now, before you receive a migration notice. Lead history, monthly spend, dispute outcomes, and CPL averages by service category. This data becomes your baseline for evaluating the PMax version after migration, and it gives you the evidence you need if you need to dispute a lead charge after the transition.

For accounts that qualify, the shift to PMax bidding can improve efficiency over time, because the algorithm has access to a broader set of signals than the standalone LSA system did. But it takes time to learn, and the first two to four weeks after migration typically look worse than steady-state performance. Build that runway into your expectations and do not cut a campaign that is still in the learning phase.

For a full breakdown of when LSAs make sense versus standard Google Search campaigns for service businesses, see our comparison of Local Services Ads and Google Ads ROI.

---

Meta’s Product Browsing Default: Seven Days to Decide

Starting 28 October, Meta will automatically enable product browsing inside existing ads unless you opt out first.

When the feature is active, users who tap your ad may see a product browsing experience within Facebook or Instagram before they reach your website. Meta’s notice describes it as showing people “product info and personalised suggestions.” The feature came with a notice to advertisers in mid-October, but as of 15 October, Meta had not published a Help Centre page explaining exactly which campaign types it applies to or how the browsing experience is triggered.

The clearest account of what is happening comes from reporting on Meta’s advertiser notice. Meta claims an average of 3% more conversions in its tests. It does not define what conversion was measured or at what stage of the funnel the lift occurred.

What this means for service-based lead campaigns

The product browsing feature is primarily aimed at catalogue-based advertisers: businesses running Shopping-style ads against a product feed. If you are running a standard lead generation campaign for a service business with no product catalogue, the feature is unlikely to trigger. But the default is still switching from off to on across your account on 28 October, and Meta’s notice does not clearly specify which ad types are and are not included.

For a law firm, accounting practice, specialist medical clinic, or professional services firm, the product browsing experience is almost certainly not what you want. Your service is not something a user selects from a catalogue. The browsing layer adds friction between the ad and your intent, which is to get the user to a landing page where you can qualify them and capture their details.

For a trade or home services business with a defined set of recurring services, a cleaning company, or a landscaper with packaged offerings, this may be worth a deliberate test. A carefully monitored rollout is worth more than an accidental one.

How to opt out before the deadline

Use the opt-out button in the Meta account-level notice before 28 October. If you cannot find the notice, go to the Advantage+ creative enhancements and destination settings in any running ad and check the product browsing toggle. The setting can be turned off per ad.

Two things worth knowing: the notice may cover only one ad account, not an entire portfolio, so check each account separately. And if you duplicate an ad, the enhancement can switch back on in the copy. Check duplicates before publishing, both before and after the 28 October change.

---

Google Channel Priority Controls Are Now Live

Google rolled out channel prioritisation and budget allocation controls on 15 October, and they address something that has frustrated service-business advertisers for some time.

The feature lets you mark Search Partners or the Display Network as Low priority within your campaigns and set a percentage cap on how much of your daily budget they can consume. According to Google’s change tracker, Google will retire its existing channel-level controls in February 2027, so the priority settings replace them. If you are relying on current controls to manage Display spend, the clock is running on setting up the replacement.

Why this matters more than it sounds

Most service businesses running Google Ads generate their leads from Search. Display Network and Search Partners can produce legitimate leads at lower cost in some categories, but they can also absorb budget on low-intent placements without showing it clearly in headline reports.

The new controls let you define exactly what portion of your budget is available to those channels. Setting Display Network to Low priority with a 30% daily budget cap is not the same as switching it off entirely. It is a deliberate allocation: Search gets priority, Display gets a bounded share, and you know the ceiling rather than finding out retrospectively from a placement report.

For an account where Search is producing leads at an acceptable cost per lead and Display is producing clicks without qualifying behaviour, this is the right adjustment. You are setting a ceiling on what you are willing to spend in channels that are not converting well, without cutting them off entirely in case performance improves.

Find the Channel Priority section in your campaign settings. Mark Display Network as Low priority and set a percentage cap that reflects what you are willing to allocate. Review the placement report two weeks in to see whether the cap is being reached and whether leads from those placements are meeting your quality threshold.

---

Customer Match Hashing Change: Four Weeks to Check Your Pipeline

This one affects anyone with an automated or custom process for uploading customer lists to Google Ads.

From 16 November 2026, Google’s Data Manager will no longer require SHA-256 pre-hashed customer data. Data Manager will handle the hashing itself. If you have a pipeline that pre-hashes emails, phone numbers, or postal addresses before uploading them, that pipeline needs to be updated before the deadline. After 16 November, sending pre-hashed data through Data Manager will cause upload failures.

For most NZ service businesses uploading customer lists manually as a CSV, this changes nothing. If your uploads go through a CRM integration, a Zapier or Make workflow, or a custom script that applies SHA-256 before sending data to the API, check with your integration provider whether it needs updating.

The deadline is four weeks away. Test a small upload in the third week of November, immediately after the change takes effect, to confirm your pipeline still works. Do not wait until December to discover your audience lists have been silently failing to update for three weeks.

Good Customer Match data is the foundation for accurate audience exclusions and lookalike targeting. A broken upload pipeline produces stale audiences, and stale audiences produce targeting decisions based on data that no longer reflects your actual customer base.

---

Meta Sequenced Events: A New Lead Qualification Tool, With Caveats

Meta has quietly added a new optimisation goal to Leads campaigns that use Website as the conversion location: Maximise number of qualified leads.

When you select this goal, you choose two conversion events, and Meta counts the ad only if both events fire in order. The practical application for service businesses: set the first event as a landing page view and the second as a form submission, so Meta optimises toward users who both land and submit, rather than those who only reach the page. Or set the first event as a page view and the second as a phone call, if your business tracks calls as conversion events.

This directly addresses one of the persistent problems with website-based lead campaigns: the algorithm optimising to the top of the funnel because that is where conversion volume is highest. A campaign that optimises for form submissions will find more form submissions, including ones from people who are far from ready to buy. A campaign that requires a landing page view followed by a submission is looking for a tighter sequence of intent signals.

The honest assessment

Only Standard attribution appears to work with this feature at the moment. More critically, Meta has not documented it officially. A feature that is not documented can be modified, restricted, or removed without notice.

Test it in a new ad set alongside your existing campaign rather than replacing what is working. The two-event sequence produces thinner conversion data than a single-event goal, which means the learning phase takes longer to clear. A realistic test requires four to six weeks and enough budget to generate meaningful data volume. Define in advance what results would justify making the change permanent.

For more on how Meta’s Advantage+ setup connects to the learning phase and lead qualification, see our Advantage+ guide for NZ service businesses.

---

What November Is Setting Up

Three of the five changes this week involve platforms making decisions on your behalf with a short window to override them. Meta turns on product browsing on 28 October by default. Google migrates your LSA account on 14 days’ notice. Customer Match hashing expectations change on 16 November.

The pattern across Q4 has been consistent: the platforms are adding automation faster than most advertisers are reviewing their account settings. Every default that goes unchecked is a decision the platform made for you, and platform defaults are optimised for platform goals, not yours.

Service businesses that end Q4 ahead of where they started will be the ones treating these updates as inputs to act on rather than announcements to file. The cost of staying across it is thirty minutes a week. The cost of missing a default switch on a live lead campaign shows up much later and is harder to trace back to source.

---

If you want someone to stay across these changes and make sure your campaigns heading into November are actually configured for your goals, book a free strategy call with Lucid Leads.

---

Frequently Asked Questions

How much notice will I get before my LSA account migrates to Performance Max?

Google says it will provide 14 days’ notice before migrating each account. Export your historical performance data, lead records, dispute outcomes, and cost-per-lead averages from the standalone LSA dashboard before that notice arrives. Once the migration runs, the old interface is gone and that data goes with it.

Do I need to opt out of Meta product browsing even if I only run service-based lead ads?

You should make a deliberate decision before 28 October. If your campaigns are service-only with no product catalogue, the feature is unlikely to activate. But the default is switching to on across your account, and Meta’s notice does not clearly define which ad types are included. Confirming your settings takes five minutes and removes the risk of an unintended change affecting a running lead campaign.

What does the new Google channel priority setting actually do?

It lets you mark Display Network or Search Partners as Low priority and set a daily budget cap on their share of your campaign spend. Search gets first claim on the budget, and capped channels get what remains up to your defined percentage. Google’s existing channel controls will be retired in February 2027, so the priority settings replace them.

Will the Customer Match hashing change break my existing customer lists?

Only if you have a custom process that pre-hashes customer data before uploading it to Google Ads. If you upload lists manually as a plain CSV, nothing changes. If you use a CRM integration, a workflow automation, or a custom script that applies SHA-256 hashing before sending data to the API, check with your integration provider and test a small upload after 16 November to confirm it still works.

Is the new Meta Sequenced Events goal worth testing for a lead generation campaign?

It is worth a careful test if poor lead quality is a genuine problem in your current campaigns. Run it in a new ad set alongside your existing setup rather than replacing what is working. The feature is undocumented, so treat it as experimental: set a four to six week test window, allocate enough budget to clear the learning phase, and decide in advance what results would justify making it permanent.