9 min read

How to Send Google Ads Leads to a Webhook with LeadSync

Luke Moulton
Luke Moulton · Published
Reviewed and updated
How to Send Google Ads Leads to a Webhook with LeadSync

Not every tool has a native LeadSync integration, and that’s okay. Webhooks let you send Google Ads leads to any system that accepts HTTP requests, from custom-built APIs to internal databases to third-party platforms. LeadSync handles the plumbing: we normalize your Google lead data, transform it into JSON, and POST it to your endpoint. You focus on processing the data your way.

Quick Start: Google Ads Leads to Webhook in 5 Steps

  • Prepare a webhook endpoint that accepts POST requests and returns HTTP 200
  • In LeadSync, create a Webhook connection with your endpoint URL, authentication method and JSON payload template
  • Go to Lead Forms > Add Lead Form > Google Lead Form, name the form, pick your Webhook connection and click Create notification
  • Paste LeadSync’s Webhook URL and Key into your Google Ads lead form
  • Click Send test data in Google Ads, confirm the request reached your endpoint, then click Save

Why Use Webhook for Google Ads Leads?

  • **Supports POST, PUT, PATCH, GET, and DELETE methods** with Bearer, Basic, or API Key authentication – pick the HTTP verb and auth type your endpoint expects
  • **Define your own JSON payload template** with placeholder tags that map to lead form fields – send exactly what you need, nothing more
  • **Connect to any API, CRM, or internal system** that accepts HTTP requests, no native integration? Webhook is the answer
  • **Works with lead forms from multiple platforms**: Google, Facebook, LinkedIn, and TikTok all feed into the same webhook
  • **Fast sync speed: 1-2 minutes** from lead capture to webhook delivery, keeping your sales team informed in real time
  • **No per-lead fees** – flat rate pricing means scale without surprise costs
  • **7-day free trial, no credit card required** – test webhook delivery risk-free before committing
  • Step-by-Step: Connect Google Ads Leads to Your Webhook

    Step 1: Prepare Your Webhook Endpoint

    Your webhook endpoint must be a publicly accessible URL that accepts POST requests. It should validate the incoming JSON payload, process the lead data (store in your database, trigger a workflow, etc.), and return an HTTP 200 response within 10 seconds. If your endpoint times out or returns a non-2xx status code, LeadSync will retry the delivery up to 3 times over 24 hours.

    If you’re building a simple endpoint, here’s a minimal example structure: accept the POST body, log the lead data, perform your business logic, and return 200. Most frameworks make this trivial – Express.js, Laravel, Django, Flask, all handle webhook routing natively.

    Step 2: Log in to LeadSync and Create a Webhook Destination

    In the LeadSync dashboard, navigate to Connections and click Add Connection. From the integration dropdown, select Webhook. You’ll see a configuration form with fields for URL, authentication, HTTP method, and payload template. Give your webhook connection a descriptive name, such as “Google Leads Webhook” or “CRM Inbound Webhook”.

    Step 3: Configure Your Webhook URL and Authentication

    Enter your webhook endpoint URL (e.g., https://api.yourapp.com/leads/inbound). Select your HTTP method – most webhooks use POST, but LeadSync also supports PUT, PATCH, GET, and DELETE if your endpoint requires a specific method.

    If your endpoint requires authentication, choose one of three options:

  • **Bearer Token:** Sends your token in the Authorization header as `Bearer YOUR_TOKEN`. Use this for APIs that expect OAuth-style tokens.
  • **Basic Auth:** Encodes username and password in the Authorization header. Use this for HTTP Basic authentication.
  • **API Key:** Sends your key as a custom header (you specify the header name). Use this for REST APIs that expect a key in a specific header like `X-API-Key`.
  • Step 4: Customize Your Payload Template

    In the JSON Payload Template box on the same form, you define the exact structure of data sent to your endpoint. Use placeholder tags wrapped in percent signs to reference lead form fields:

    %full_name%, %first_name%, %last_name%, %email%, %phone_number%, %company_name%, %job_title%, %city% and the other standard Google lead form fields. LeadSync will replace these tags with actual lead values. To include every field LeadSync received as one JSON object, use %all_fields%.

    A simple example payload:

    {"name": "%full_name%", "email": "%email%", "phone": "%phone_number%", "source": "google_lead_form", "timestamp": "%created_time%"}

    You can nest fields, add static values, include metadata, or structure the payload however your API expects. The template is pure JSON, no special syntax required beyond the %placeholder% tags. Click Update Connection to save the Webhook connection.

    Step 5: Add Your Google Lead Form in LeadSync

    LeadSync doesn’t sign in to your Google Ads account. Google sends each new lead to LeadSync through a webhook instead, so all you need is LeadSync’s webhook URL and a key.

    Click Lead Forms in the left sidebar, click Add Lead Form, then choose Google Lead Form. LeadSync shows a Webhook URL and a KEY that is unique to this form. This Webhook URL is LeadSync’s address for receiving Google leads, not your own endpoint. Copy both into a note now, because LeadSync moves to a different page when you save. You can find the key again later under Ad Accounts > Google Ads.

    Enter a Lead Form Name you’ll recognise (the name of your Google lead form works well), then select the Webhook connection you just created.

    LeadSync lists the standard Google lead form fields (email, name, phone, company name, job title, address and so on), each with a dropdown of the placeholder tags in your payload template. If your template already uses the Google field names, like %email% or %phone_number%, LeadSync fills those in automatically and you can leave the dropdowns empty. Use the mapping only when your template uses a different tag name, for example map Phone Number to %phone%. Custom questions you add to a Google lead form don’t appear in the mapping table.

    Click Create notification to save. LeadSync is now ready to receive leads sent with this form’s key.

    Step 6: Paste the Webhook URL and Key into Google Ads

    In Google Ads, go to Campaigns > Assets, select Lead form, hover over your form and click the pencil icon to edit it. Expand Export leads from Google Ads, then Other data integration options. Under Webhook integration, paste LeadSync’s Webhook URL into the webhook URL field and the KEY into the key field. Don’t save yet: you’ll send test data first.

    If several Google lead forms should go to the same endpoint, you can paste the same Webhook URL and Key into each of them. Add another Google Lead Form in LeadSync only when a form needs a different connection or field mapping.

    Step 7: Send Test Data and Check Your Endpoint

    Still in the Google Ads lead form editor, click Send test data. Google sends a sample lead to LeadSync straight away, and LeadSync forwards it to your endpoint using your payload template. Check your endpoint logs to confirm the request arrived, validate the JSON structure, and verify your business logic works. When it does, click Save in Google Ads.

    If nothing arrives, check that you clicked Create notification in LeadSync, that the Webhook URL and Key in Google Ads exactly match LeadSync, and that your endpoint URL and authentication on the Webhook connection are correct. Google confirms the test as soon as LeadSync receives the request, so check your endpoint for the request itself rather than relying on Google’s message. Fix the cause, click Send test data again, then click Save.

    Customizing Your Webhook Integration

    Webhooks are infinitely flexible. Here are common customization patterns:

    Payload Templates: Include only the fields you need to reduce payload size and simplify downstream processing. You can also nest fields, rename them, or add computed values (like a UUID or timestamp). The template editor supports any valid JSON structure.

    Authentication Options: If your endpoint uses a rotating token, update the authentication credentials in LeadSync, no code changes needed. For API keys stored in custom headers, specify the header name and value. For OAuth flows, use Bearer tokens refreshed by your API provider.

    HTTP Methods: While POST is the standard, some APIs prefer PUT (idempotent updates), PATCH (partial updates), or even GET with query parameters. LeadSync supports all five HTTP verbs, so adapt to your endpoint’s requirements.

    Error Handling: If your endpoint returns a non-2xx status code, LeadSync automatically retries the delivery (exponential backoff: immediately, 1 hour later, 24 hours later). If all retries fail, the lead is marked as failed in the dashboard. You can manually retry from the UI or check your endpoint logs to debug the issue.

    Monitoring: The LeadSync dashboard shows delivery status, timestamps, and response codes for every lead sent to your webhook. Click into a failed delivery to see the request payload and response body, helping you debug quickly.

    Go Beyond Webhook: Multi-Channel Lead Routing

    Webhooks are powerful, but sometimes you want to send leads to multiple destinations simultaneously. LeadSync lets you combine webhook with native integrations in a single workflow:

  • **Email:** Forward leads to your sales team inbox with a notification template. Learn more: [How to Set Up Google Ads Lead Email Notifications](https://support.leadsync.me/integrations/google/email-notifications/)
  • **Slack:** Post leads to a dedicated Slack channel with formatted summaries. Learn more: [Synchronized Google Ads Leads with Slack](https://support.leadsync.me/integrations/google/slack/)
  • **Google Sheets:** Append leads to a spreadsheet for team visibility and analysis. Learn more: [Google Ads Leads to Google Sheets](https://support.leadsync.me/integrations/google/google-sheets/)
  • **SMS:** Send text notifications to your team or the lead immediately after capture. Learn more: [Google Ads Lead SMS Notifications](https://support.leadsync.me/integrations/google/sms/)
  • For example, you could send each lead to your webhook endpoint (for CRM ingestion), simultaneously notify your sales team on Slack, and append to a Google Sheet for reporting. LeadSync orchestrates all three – one Google lead form extension, three destinations, zero manual work.

    Frequently Asked Questions

    What HTTP methods does LeadSync support for webhooks?

    LeadSync supports POST, PUT, PATCH, GET, and DELETE. Most webhooks use POST (the HTTP standard for submitting data), but some APIs prefer other methods. Choose the method your endpoint expects, and LeadSync will send requests accordingly.

    Can I use Bearer tokens, Basic auth, or API keys?

    Yes to all three. Bearer tokens go in the Authorization header as Bearer YOUR_TOKEN. Basic auth encodes username:password in the header. API keys can be sent as a custom header (you specify the header name and value). Pick whichever your endpoint requires.

    How do I define my JSON payload format?

    Use the JSON Payload Template box on your Webhook connection in LeadSync. Write valid JSON and insert placeholder tags like %full_name%, %email%, %phone_number%, etc. LeadSync will replace these tags with lead values before sending. You can nest fields, add static values, or structure the payload any way your API expects.

    How fast are Google Ads leads delivered to my webhook?

    LeadSync delivers Google Ads leads to your webhook endpoint within 1-2 minutes of capture. Google sends each lead to LeadSync as soon as the form is submitted, and LeadSync forwards it to your endpoint using your payload template. This rapid delivery ensures your sales team can act quickly on fresh leads.

    What happens if my webhook endpoint is slow or times out?

    LeadSync allows 10 seconds for your endpoint to respond. If it times out or returns a non-2xx status code, LeadSync will retry three times over 24 hours (immediately, 1 hour later, 24 hours later). Check your endpoint logs to diagnose performance issues. For high-volume scenarios, consider adding a queue (like AWS SQS or RabbitMQ) between your endpoint and your processing logic.

    How do I test my webhook before going live?

    Use Google’s Send test data button. With LeadSync’s Webhook URL and Key pasted into your Google Ads lead form, click Send test data. Google sends a sample lead to LeadSync, and LeadSync forwards it to your endpoint using your payload template. Check your endpoint logs to confirm the request arrived, validate the JSON structure, and verify your business logic works. Once the test passes, click Save in Google Ads and you’re ready for real leads from your Google campaigns.

    Can I send the same lead to multiple webhook endpoints?

    Yes. Create a Webhook connection in LeadSync for each endpoint URL. Then go to Lead Forms, click Add Lead Form, choose Google Lead Form, open the New Connection For Existing Form tab, select your Google lead form and pick the next Webhook connection. LeadSync will POST each lead to all endpoints attached to that form. This is useful for syncing data across multiple systems, e.g., your internal API, a third-party CRM, and a data warehouse.

    What if my webhook endpoint is temporarily down?

    LeadSync retries failed deliveries automatically. If your endpoint returns a non-2xx status code on the first attempt, LeadSync will retry after 1 hour and again after 24 hours. If all retries fail, the lead is marked as failed in the dashboard. You can manually trigger a retry once your endpoint is back online, or check the response body in the LeadSync UI to debug the root cause.

    How does LeadSync compare to Zapier for webhook delivery?

    Zapier is a general automation platform; LeadSync is purpose-built for lead routing. Zapier works well for simple integrations, but for high-volume lead delivery, LeadSync offers faster latency, better retry logic, built-in Google Ads integration, and lead-specific features (deduplication, field mapping, multi-destination routing). If you’re already using Zapier for other workflows, you can still use LeadSync for leads and connect them via webhook – both systems can coexist. For lead-only use cases, LeadSync’s native approach is faster and cheaper.

    Can I use webhooks for leads from Google, Facebook, LinkedIn, and TikTok forms too?

    Absolutely. Connect your Google, Facebook, LinkedIn, or TikTok lead forms to LeadSync using the same process. Each form sends leads to your webhook with the same JSON structure, payload template, and authentication. This is the power of a unified platform – one webhook endpoint handles leads from any source, normalized by LeadSync.

    Looking for a different destination for your Google Ads leads? These integration guides walk you through setup step by step:

    Start Sending Google Ads Leads to Your Webhook Today

    Webhooks unlock unlimited possibilities for lead routing. Whether you’re building a custom CRM, syncing to an internal tool, or connecting to a third-party API, LeadSync makes it simple: configure your endpoint, define your payload, and let us handle the delivery. No integration code required, just HTTP and JSON.

    Ready to try it? Sign up for a 7-day free trial of LeadSync and start routing Google Ads leads to your webhook today. No credit card required.

    Luke Moulton

    Luke Moulton

    Luke is the founder of LeadSync and, as a Digital Marketer, has been helping businesses run lead generation campaigns since 2016. See Full Bio ›

    Sync your leads in under 60 seconds

    Try LeadSync free for 7 days. No credit card required.

    Start Free Trial