Google Local Services Ads Integration with Launch365

This guide explains how to connect Google Local Services Ads (LSA) to Launch365, verify reporting, sync message leads into the inbox, and reply through Launch365 Automations.

Audience: Launch365 company admins, agency admins, onboarding staff, and deployment owners
Last verified: August 3, 2026

What the Integration Does

Capability	Result in Launch365
LSA reporting	Shows leads, charged leads, calls, messages, bookings, impressions, cost, and campaign performance.
Message lead sync	Creates or updates the contact, adds the inbound message to the Launch365 inbox, and assigns the Google LSA channel.
Automations	Starts an automation when a new consumer message is found.
LSA replies	Sends a response back into the original Google LSA conversation. This is not an SMS.
Multiple accounts	Allows a company or agency to connect more than one LSA client account.

Google exposes Local Services lead and conversation data through the Google Ads API. The client account must contain a Local Services campaign before these resources return data. See Google’s Local Services campaigns API guide.

Account Structure

Use the manager account as the login account and the LSA account as the data account:

Google Ads manager account (MCC)
└── Local Services Ads client account
    └── Connected Launch365 company

• Manager customer ID / login customer ID: The 10-digit MCC ID used to access managed accounts.
• LSA client customer ID / account ID: The 10-digit account that owns the Local Services campaign, leads, and conversations.
• Do not select the MCC itself as the LSA data account.
• Launch365 removes hyphens from customer IDs before API calls.

When an API user reaches the LSA account through an MCC, Google requires the manager ID in the login-customer-id header. See Google’s API call structure.

Before You Start

Confirm all of the following:

• The business has an active Google Local Services Ads account and Local Services campaign.
• The LSA client account is linked beneath the correct Google Ads manager account.
• The person connecting Google can access both the manager and LSA client accounts.
• The Google invitation has been accepted; a pending invitation is not enough.
• The user can view LSA leads. Standard or administrative access is recommended when Launch365 will reply to leads.
• You know the manager customer ID and the LSA client customer ID.
• A Launch365 administrator can access Settings → Integrations and Automations.

Google account access is managed from Google Ads. See Google’s Local Services Ads account access guide.

Connect the Account in Launch365

Option A: Connect with the Business’s Google Account

1. Sign in to the correct Launch365 company.
2. Go to Settings → Integrations.
3. Open Google Local Service Ads.
4. Click Connect to Local Service Ads.
5. Sign in with the Google user that can access the MCC and LSA client account.
6. Approve the requested Google Ads permission.
7. Under Parent Account, select the manager account that owns the LSA client account.
8. Search for the business by account name or customer ID.
9. Select one or more LSA client accounts.
10. Click Connect Accounts.

If Google returns only one accessible account, Launch365 may connect it automatically.

Option B: Connect with an Agency Google Account

Use this option when the agency already has an active shared LSA authorization in Launch365.

1. Go to Settings → Integrations → Google Local Service Ads for the company.
2. Select the agency Google account.
3. Select the correct Parent Account or MCC.
4. Search for the LSA client account by name or customer ID.
5. Select the account and click Connect Account(s).

The selected client account must already be accessible through that agency Google account.

Configure the Integration

Open the connected account and configure these settings:

Setting	Recommended value	Notes
Login customer ID	MCC customer ID	Required when the LSA account is accessed through a manager.
Business-hours polling	5 minutes	Allowed range: 1–60 minutes. The production scheduler currently runs every five minutes.
After-hours polling	15 minutes	Allowed range: 1–180 minutes.
Enable integration	On	Disabling it stops reporting, lead polling, and replies for the connection.

Click Save Settings.

Verify Reporting

1. Click View Analytics Dashboard.
2. Select a date range that contains known LSA activity.
3. Confirm that Launch365 displays the expected account and at least some of the following:
   • Leads
   • Charged leads
   • Phone calls
   • Messages
   • Bookings
   • Impressions
   • Cost and campaign performance
4. Use the dashboard’s Sync action to verify the connection and refresh its sync status.

The Google Ads and Local Services dashboards can differ slightly because of reporting delays, date boundaries, lead credits, and Google-side updates. Compare the same account, time zone, and date range before treating a difference as an error.

Enable Message Lead Sync and Replies

An active automation with the Google LSA trigger is what enables message-lead polling for a newly configured integration.

1. Go to Automations.
2. Create a new automation.
3. Choose the trigger Google LSA message lead received.
4. Add any needed workflow actions, such as:
   • Assign to an employee
   • Add a tag
   • Notify the team
   • Update the lead status
   • Send Google LSA Reply
5. If using Send Google LSA Reply, configure:
   • A reply template, Nexus AI, or both
   • A fallback message
   • Initial response only or Reply to every inbound message
6. Activate the automation.

Use Initial response only for most workflows. It prevents an automated response from being appended after Launch365 has already responded to the same LSA lead.

When a new consumer message is found, Launch365:

1. Creates or updates the contact.
2. Marks the contact as a new lead.
3. Creates an inbound inbox message under the Google LSA channel.
4. Starts every active automation whose trigger is google_lsa_lead.
5. Appends a reply to the Google LSA thread if the workflow includes send_google_lsa_reply.

For additional implementation notes, see Google LSA Message Sync + Automations.

Test the Integration End to End

Use a recent real LSA message lead or generate a new message lead through the business’s ad.

1. Confirm the automation is active.
2. From the connected integration, click Sync LSA Leads Now or wait for the next poll.
3. Open the Launch365 inbox and confirm:
   • The contact was created or matched correctly.
   • The message appears under the Google LSA channel.
   • The message text and any attachment links are present.
4. Open the automation run and confirm the expected steps completed.
5. If the automation replies, open the lead in Google Local Services Ads and confirm the response appears in the same conversation.

Launch365 de-duplicates inbound LSA conversations by Google’s conversation resource name, so polling the same interval again should not create a second copy.

Important Behavior and Limits

• Launch365 polls Google for LSA messages; this flow is not instant. Normal business-hours latency is up to about five minutes.
• The inbox sync currently creates conversations for consumer messages with text or attachment links. Calls and bookings appear in analytics but are not created as inbox messages by this poller.
• An active google_lsa_lead automation is required for new message polling unless the connection still has the legacy lead-sync setting enabled.
• Sync LSA Leads Now can complete without importing anything when no qualifying automation exists, no new consumer messages exist, or the polling cursor is already current.
• LSA replies remain inside Google LSA. They do not consume or send a Launch365 SMS.
• Google may omit contact information from wiped-out leads and does not expose lead data for some healthcare categories.
• Disconnecting an account removes that company-to-account connection and stops its sync. It does not pause or delete the campaign in Google.

Troubleshooting

Symptom	What to check
No accounts found after Google sign-in	Confirm the Google user accepted access, can open the MCC and client account in Google Ads, and signed in with the correct Google profile.
The MCC appears but the business does not	Confirm the LSA client account is linked below that MCC and select the correct parent manager before searching.
USER_PERMISSION_DENIED	Set the connected account’s Login customer ID to the MCC ID and confirm the OAuth user has access through that MCC.
INVALID_CUSTOMER_ID	Verify both IDs are 10 digits. Remove spaces; Launch365 will remove hyphens.
Developer-token or test-account error	The Launch365 deployment needs a Google Ads developer token whose access level permits the target production account.
Google shows an unverified-app warning	The deployment’s Google Cloud OAuth consent configuration or adwords scope has not completed the required verification.
Connected but the dashboard is empty	Confirm the selected client account owns an LSA campaign, use a date range with activity, and check that the campaign is active.
Calls show but inbox messages do not	Inbox ingestion is limited to consumer message conversations with message text or attachments. Create and activate the LSA trigger automation.
Sync LSA Leads Now imports nothing	Confirm the integration and automation are active, then check whether the message is new enough for the polling window and has already been imported.
Automation starts but does not reply	Confirm the Send Google LSA Reply step is enabled, the integration is active, the trigger contains an LSA lead resource, and the queue worker is running.
Connection worked and later stopped	Reconnect Google if access was revoked. Deployment owners should also verify scheduled token refreshes.