You can’t send every Google Local Services Ads lead to GoHighLevel with one switch. HighLevel (the company behind GoHighLevel) is on Google’s list of LSA booking partners, so bookings can land straight in a HighLevel calendar. Phone calls reach HighLevel if the business number in your LSA profile is a HighLevel number. Message leads are the gap: there is no native sync, so you either pay a connector such as LSArespond ($0.50 per message lead and $0.20 per answered call lead, checked October 29, 2026) or build your own on the Google Ads API.
How this guide was made: it is research, not a hands-on test. We read Google’s Local Services and Google Ads help pages, the Google Ads API documentation, HighLevel’s support portal and the connector’s pricing pages on October 29, 2026. We have not run these setups on a live LSA account, so there is no score, and you should test each route with a real call and message before you trust it. If you also want to know which ad drove each call, start with how to track Google LSA calls after the move to Performance Max. Some missed calls now count as billable leads too, so read our note on LSA missed-call charges before you set up call forwarding.
What HighLevel connects to on its own, and what it doesn’t
HighLevel’s only official link to Local Services Ads is booking. Google’s “Local Services Ads Booking Partners” page lists HighLevel, and HighLevel’s support article “Setting Up Reserve with Google for Local Services Ads” (modified August 3, 2026) explains how to publish your calendars to Google. Nothing in that article mentions calls or message leads.
Don’t confuse it with HighLevel’s Google Lead Ads integration. That one creates a contact whenever someone submits a Google Ads lead form, and its help article does not mention Local Services Ads at all. LSA leads are a different lead type with their own inbox, so a lead form connection will not pick them up.
Zapier is no shortcut either. When a user asked the Zapier community for a Google Local Services trigger in 2022, Zapier staff replied that it “isn’t an available app” and had no workaround to offer. Services that do offer an LSA trigger on Zapier today are third parties sitting in the middle, like the connector covered below.
Which route carries which lead
Pick the route by lead type, because no single one carries all three.
| Route | Calls | Messages | Bookings | Cost and main catch |
|---|---|---|---|---|
| Google Organic Booking feed from HighLevel calendars | No | No | Yes | Included in HighLevel; US only; Google takes about 1–2 weeks to review feeds |
| HighLevel phone number as the LSA business phone | Yes | No | No | HighLevel phone usage; test caller ID and ring time before going live |
| Connector (LSArespond) | Answered and missed | Yes | Not listed | $0.50 per message lead, $0.20 per answered call lead; only leads after signup |
| Email alert parser into an Inbound Webhook | Alert only | Varies by alert | No | $0.01 per premium run after 100 free; alerts don’t always include the message |
| Your own code on the Google Ads API | Yes, with recording link | Yes, with text | Lead record | API access and a developer; you maintain it |
Sources: Google Local Services Help, Google Ads Help, Google Ads API docs, HighLevel Support Portal, lsarespond.com (listed at the end). Prices checked October 29, 2026.
Bookings: publish HighLevel calendars to Google
Booking leads come into HighLevel natively once your calendars are published to Google and your Business Profile is linked in Google Ads. Google’s help page on booking leads says you opt in through one of its booking partners and then manage appointments and availability in that partner’s account, while the booking lead still shows in your LSA leads.
Google’s conditions, from “About booking leads in Local Services Ads”:
- You are a verified Local Services Ads provider.
- Your Google Business Profile is linked to your Local Services Ads account.
- That profile has a booking link managed by a supported partner.
- Booking is US only, some categories only in California and Florida, and not for health care or tax specialists.
Many tutorials still show the 2022 path (Settings, Integrations, “Reserve with Google”, then a status that turns Connected after 48 hours). HighLevel’s current article uses a different path:
- In the sub-account, open Calendars › Calendar Settings › Connections and pick the staff user if asked.
- Open the Google Organic Booking tab.
- Set the Primary Action Feed to a Service Menu or Calendar Group, and the Services Feed to the calendars you want bookable, then click Upload.
- In Google Ads, go to Tools › Data Manager › Connected products › Google Business Profile › Manage & link and link the right profile and location.
- Wait. HighLevel says Google typically takes one to two weeks to verify and publish the feeds, and the two feeds can be approved separately.
Business name and address must match between HighLevel and Google. Each time you change services, calendars or the menu, upload the feeds again.
Calls: make LSA ring a HighLevel number
Call leads reach HighLevel when the phone number in your LSA profile is a HighLevel number. Google gives your ad a forwarding number, and its “Manage leads and jobs” page says calls to that number are forwarded to your actual business number. If that business number lives in HighLevel and forwards on to your team, every LSA call is logged in Conversations and can start a workflow, such as a text to callers you missed.
Three things to check before you switch:
- Caller ID. Place a test call through your live ad and confirm HighLevel shows the caller’s number, not a Google number, before you build a text-back on it.
- Ring time. HighLevel forwarding adds a hop. Make sure the call still reaches a person fast enough that callers don’t hang up.
- Recordings stay with Google. In the US and Canada, Google records inbound calls through its forwarding number. You listen to those in Google Ads; HighLevel only has its own call log.
Don’t put a separate tracking number in front of the LSA number at the same time without checking how they chain. Our Nimbata vs CallRail comparison covers tools that already import LSA call data, if attribution matters more to you than the CRM. For the text-back itself, our missed call text back setup guide walks through the message wording and setup.
Message leads: the hard part
Message leads are hard to pipe anywhere because Google keeps them inside its own system. Google’s Performance Max lead help says it “routes messages through anonymized proxy numbers and email aliases to protect consumer and business privacy.” So even if you copy a lead into HighLevel, replies usually have to go back through Google’s thread, or you call the customer.
You have three ways to get them in:
1. A connector. LSArespond connects to your LSA account through a Google Ads manager invite (its FAQ says the invite is sent by hand, so it can take time) and lists GoHighLevel among its integrations. It auto-replies to message leads with follow-ups, texts missed callers, and recaps answered calls. Its pricing is inconsistent across its own pages: the homepage says “$19/mo + usage fees based on lead flow”, while its GoHighLevel page says “No monthly fee”. Both list 50 cents per message lead and 20 cents per answered call lead, and a 30-day free trial. It only pulls new leads after signup, not your history. It says it is not affiliated with Google.
2. Parse the alert emails. Google emails you about new message leads, and you can send those emails through a parser into a HighLevel workflow that starts with an Inbound Webhook trigger. It is cheap: Inbound Webhook is a premium trigger, and HighLevel’s free premium tier charges $0.01 per run after 100 free lifetime runs. It is also fragile. Users on Local Search Forum reported in 2024 that some alerts include the lead’s name and message and others only say a potential customer has inquired. A parser can’t add what the email leaves out.
3. Build on the Google Ads API. The local_services_lead resource returns lead type (call, message, booking), contact details, status and charge status. The local_services_lead_conversation resource returns call duration and a recording link, and message text. Write access is limited to appending a conversation and giving lead feedback. Contact details come back empty once a lead is wiped out, health care leads are not available, and recording links only open for someone signed in with access to the Ads account. This route gives you the most data, but you need API access and someone to run and maintain the sync.
What the Performance Max move changes for your sync
Google is moving Local Services Ads into Performance Max campaigns with pay-per-lead goals. Its migration article says the first phase started in August 2026 for select US home and storefront service advertisers, wider groups follow in late 2026, and other countries and categories in 2027. Accounts with custom bidding or booking setups are in a later phase.
For a HighLevel setup, three changes matter:
- The Leads page under Conversions in Google Ads replaces the LSA lead inbox. Reply to message leads from there.
- Email alerts for call and message leads are managed under Admin in Google Ads, and at least one user must stay opted in. If you rely on email parsing, check that the inbox you parse still receives them after the move.
- The API resources above work for both Local Services campaigns and Local Services Performance Max campaigns, so a connector or script built on them should keep working. Re-test after your account migrates anyway.
What it costs each month
Take a home service business with 60 message leads and 40 answered call leads a month from LSA. Here is what moving those leads into HighLevel adds, on top of the HighLevel plan (Starter $97 a month, Unlimited $297) and your ad spend.
| Route | Math | Per month |
|---|---|---|
| LSArespond, homepage pricing | $19 + 60 × $0.50 + 40 × $0.20 | $57.00 |
| LSArespond, if there is no monthly fee | 60 × $0.50 + 40 × $0.20 | $38.00 |
| Email parser + Inbound Webhook | 100 runs × $0.01, once the 100 free runs are used | $1.00 + parser cost + upkeep |
| Bookings via Google Organic Booking | Included in HighLevel | $0 |
| Calls to a HighLevel number | HighLevel phone usage | Usage-based |
Sources: lsarespond.com and lsarespond.com/gohighlevel; HighLevel pricing page and “Workflows Pro Plan” help article. Prices checked October 29, 2026.
The webhook route looks almost free, but the real cost is time: each Google alert format change can break the parser. For a single business, a connector is usually worth the money once message leads are more than a handful a week. Agencies with many LSA clients are the ones for whom building on the API pays off. If you also send those clients a monthly report, our AgencyAnalytics vs DashThis vs Reportei comparison shows which dashboard tools can pull in LSA data.
A setup order that avoids lost leads
- Bookings first. Upload the Google Organic Booking feeds and link the Business Profile; it takes the longest to approve.
- Calls next. Point the LSA business number at a HighLevel number and make one test call from a phone that isn’t yours. Check caller ID, ring time and the Conversations log.
- Then messages. Start a connector trial or an email parser, send yourself a test message lead if you can, and confirm the contact, the message text and the source tag arrive in HighLevel.
- Tag the source. Add a tag such as “LSA” on every route, so HighLevel reports can separate LSA leads from other sources.
- Keep answering in Google. Respond quickly where the lead lives too, so leads don’t go cold while the sync catches up.
More guides like this sit in our agency CRM and automation section. How we research and test is explained on how we test.
Sources
- Google: Local Services Ads Booking Partners
- Google: About booking leads in Local Services Ads
- Google: Manage leads and jobs
- Google Ads Help: Local Services Ads moving to Performance Max
- Google Ads Help: How leads work in Performance Max
- Google Ads API: Local Services campaigns
- HighLevel: Setting up Reserve with Google for Local Services Ads
- HighLevel: Google Lead Ads integration
- HighLevel: Workflows Pro plan pricing tiers
- HighLevel pricing
- LSArespond pricing and LSArespond GoHighLevel page
- Zapier Community: Google Local Services trigger question
- Local Search Forum: what LSA lead alerts include
