Google Local Services Ads (LSA) Integration

Respond to your LSA message leads quickly and easily with Hatch

How does the Hatch + LSA integration work?

When you integrate Hatch with Google LSA, you can automate an immediate response to your Google LSA leads, via text, email, and ringless voicemail. Here's how the flow works:

 

1. When a customer clicks on the "Message" button on your Google LSA ad, they will be brought to a window where they can provide their contact information and send a message.

2. Once they fill out the form, they'll see a thank you message from Google LSA.

3. Immediately (within one minute), they'll become a contact in Hatch and get entered into your designated Speed to Lead campaign. Which means they'll receive whatever message(s) you have created for that campaign. Here's an example below:

4. Once the lead responds to your message, they'll appear on your Workspace and you'll get notified.

5. You can then jump in to engage with the lead, or your Hatch AI bot can do it for you.  

6. The outcome of the conversation will then dictate which column that conversation card ends up on your Workspace. If you are manually handling the conversation, you will move the conversation card. If your Hatch bot is handling the conversation, it will move the card according to the rules you have set.

How do I set up the Hatch + Google LSA integration?

Activating your integration is a simple process!

1. Connect Hatch to Google LSA

1. Navigate to the App Marketplace within your Hatch account
2. Filtering by "Lead Source," you will find the Google LSA integration. Click the Connect button.
3. When you see the O-auth window, click to allow access to your Google LSA account. See the FAQ below for notes and clarification on what you're giving Hatch access to. 
   Note: you must authorize with a user that has permission to both read and write in the LSA account (the minimum permission level is Standard).
4. On the next screen, you will see a list of LSA business IDs associated with your user account. Select one.

2. Set up an autoresponder within Google LSA

The Hatch integration allows you to set up an auto-responder to the lead in your LSA account. It is important to set this up for two reasons:

1. This lets the lead know you've received the request and that you will be contacting them outside of the LSA messaging app (aka via your Hatch campaign).

2. Google displays your average response speed in your ad, and also ranks faster-responding businesses higher. However it only measures response times for messages sent within the LSA messaging platform. This auto-responder message occurs within the LSA platform so your immediate response time will be recognized.

Here is what we recommend for your autoresponder message:

FAQ

How fast will my message reach my Google LSA leads?

Hatch is syncing with Google LSA every 1 minute, but Google may not make the lead available immediately. It may take up to 20 minutes for your lead to reach Hatch and get launched into a campaign.  

Your leads from other sources may get a message instantaneously. This is because those sources offer what's called a webhook, which allows for real-time syncing. Google LSA does not offer a webhook integration, only "near real-time" syncing. 

Even so, integrating with Hatch may offer your team efficiencies through automation, especially if you have a hard time reaching leads quickly through Google LSA's options. 

Why are leads coming in without a first or last name?

Google LSA does not make the first or last name fields required on their form.  You may see these leads in your LSA notifications listed as "Potential Customer". 

Hatch is able to accept the leads without that information, but it may cause interference with your campaign if your campaign is utilizing the [[Contact First Name]] or [[Contact Last Name]] snippets. We recommend that you remove these snippets from the campaign you are using for LSA speed to lead. 

Why can I only select one of my LSA businesses to integrate with?

For the initial release, the integration is limited to a single LSA business in a single integration instance in order to guarantee stability in the connection. 

We will continue to explore the best implementation to support multiple LSA businesses. In the meantime, our support team can assist with setting up multiple integration instances in the product back-end. These will function the same to bring leads into Hatch, but the integrations themselves will not be visible to users in the app. 

Am I giving Hatch full access to my Google LSA account?

When setting up your integration, Google will show a consent window (also known as O-auth), indicating that "Hatch wants permission to do anything you [the user] can do in your Google LSA account."

Hatch doesn't actually want or need all of that permission; this is just the narrowest scope of permissions the Google Ads API offers for setting up integrations. So even though you're giving us permission to access your whole account, we will only access parts of it. 

Here's what that means.

Hatch will use its API access to do only the following:

• Read the data from the Customer resource associated with the user (to provide the business selection screen and confirm the timezone)
• Read the data from the Local Services Lead and Local Services Lead Conversation resources
• Write the auto-response message back to the Local Services Lead Conversation resource

Hatch will not use its API access to do any of the following:

• Read your performance data
• Create or edit any campaigns, ads, or ad groups
• Create or edit any settings, including targeting, bidding, or scheduling
• Set or change budgets
• Set, apply, or dismiss recommendations
• Edit billing information