Google Lead Form Ads

Leads from Google Ads lead forms arrive in the CRM automatically over a webhook, ready to enrich and convert.

The MyVoipCRM Google Lead Ads integration pushes submissions from your Google Ads lead form campaigns into the CRM instantly over a webhook. Instead of manual data entry or spreadsheet tracking, leads are recorded automatically and your sales team can start calling the same day.

What it does

  • Automatic CRM records for name, phone, email and custom form fields from Google Ads lead forms
  • Verified data transfer with a company-specific Push URL (webhook) and security key
  • Lead list: search, sorting (newest / oldest), paging and column visibility
  • Lead detail: campaign ID, form ID, test-lead flag and every field-value pair on the form
  • One-click customer creation from the list (name and phone pre-filled)
  • Excel export with the current filters
  • Instant mobile/app notification when a new lead arrives
  • Google Lead Ads source breakdown in sales pipeline reports

Highlights

Instant transfer over webhook

When the form is submitted, Google sends the data to your MyVoipCRM webhook address. The lead appears in the CRM within seconds.

Secure key verification

If the key entered on the Google side does not match the google_key in the payload, the record is rejected; only the authorised integration is accepted.

Fast conversion to a sale

The create-customer button on the lead row carries the name/phone across automatically; your team moves straight to calling and follow-up.

Reporting and export

Bulk export to Excel and a Google-source breakdown in the pipeline lead report; measure campaign performance against CRM data.

How to set it up

  • In MyVoipCRM go to Sales Pipeline → Lead Ads → Integration → Google Lead (/ad-lead/google-lead-provide-webhook-url-and-key).
  • Copy the Push URL (webhook) and Key values. The URL is specific to your company; the key secures the integration.
  • In your Google Ads account open the campaign with the lead form; go to the webhook integration / data delivery section in the form settings.
  • Paste the Push URL into the webhook URL field and the CRM key into the key field.
  • Verify the integration with Google’s test lead. Once the test passes, real leads flow automatically.
  • View and manage incoming records under Sales Pipeline → Lead Ads → Google Lead (/ad-lead/google-leads).

Webhook address format (example):
https://messenger.myvoipcrm.com/api/AdLeads/webhook?id={companyId}&source=Google
The company ID is generated automatically in the CRM; use the copy button. The key value is shown in the CRM panel.

What you can do in the CRM

  • List: ad campaign ID, date, full name, phone; search and sorting
  • Detail: lead ID, form ID, test flag, created date and all form fields
  • Create customer: one step from the lead to a CRM customer record
  • Delete: clean up unnecessary or test records
  • Excel: export with the current filters
  • Report: Google Lead Ads counts in the pipeline lead report (alongside Facebook and site forms)

Who it is for

  • Sales teams collecting leads through Google Ads
  • Call centre / inside sales operations that want to call leads fast
  • Marketing teams measuring ad spend against real CRM leads and conversions
  • Companies running multi-channel lead management with Facebook Lead Ads and site forms

Frequently asked questions

Is Google OAuth or the Google Workspace module required?

No. Google Lead Ads works with the Google and Facebook Lead Form Integration module (google_facebook_lead); the webhook setup is enough.

Do leads become customers automatically?

No; leads arrive as separate records first. Use create-customer on the list to convert one with a single click.

Can I tell test leads apart?

Yes. The “Is test” field on the detail screen marks Google’s test submissions.

Is Facebook Lead Ads available too?

Yes. The same module package also supports Facebook Lead Ads and a third-party site form webhook, each with its own integration page.

How is authorisation handled?

The lead list, detail, deletion, Excel and webhook settings are governed by role-based permissions; only authorised users have access.