---
title: Google Ads Lead Forms → Zapier → MarketSharp Integration
type: article
created: '2026-04-05'
updated: '2026-04-05'
source_docs:
- raw/2026-01-13-weekly-call-w-sebastian-113980639.md
tags:
- integrations
- google-ads
- lead-forms
- zapier
- marketsharp
- performance-max
- lead-tracking
- gclid
layer: 2
client_source: null
industry_context: null
transferable: true
---

# Google Ads Lead Forms → Zapier → MarketSharp Integration

## Overview

When a Google Ads campaign uses **native Google lead forms** (as an asset on Search, Performance Max, or other campaign types), form submissions are stored inside Google Ads itself — they do **not** automatically route to a landing page form handler or CRM. This creates a silent lead-tracking gap: Google Ads reports conversions, but the CRM receives nothing.

This pattern documents how to recover existing leads via CSV export and how to wire up ongoing sync via Zapier.

**Discovered via:** [[clients/ahs/index]] — a Performance Max campaign generated ~135 untracked leads that never reached MarketSharp. See [[meetings/2026-01-13-weekly-call-sebastian]] for full context.

---

## The Problem

Google's native lead form asset stores submissions in a Google-hosted CSV, separate from any website or CRM. Key symptoms:

- Google Ads **Conversions** report shows lead form completions (e.g., "Google hosted lead form" conversion action)
- CRM (MarketSharp) shows **zero** corresponding records
- The form's submission message simply says "We'll contact you soon" — there is no webhook or redirect configured by default
- GCLIDs are captured by Google but never passed downstream

This is easy to miss because the campaign appears to be converting normally in Google Ads reporting.

---

## Immediate Fix: CSV Export

To recover leads already collected:

1. In Google Ads, navigate to **Campaigns → Assets → Lead Forms**
2. Locate the lead form asset (look for high interaction rate — e.g., 35% interaction rate, 680 clicks is a signal)
3. Click the **Download / CSV icon** to export all submissions
4. The CSV includes: submit timestamp, full name, email address, phone number, and **GCLID** (Google Click ID)

The GCLID enables retroactive attribution — you can match each lead back to the campaign, ad group, keyword, and device that drove the click.

> **Access note:** You need **Admin or Standard** access to the Google Ads account to download lead form CSVs. If the account was set up under a personal Gmail (e.g., a contractor's account), you may need to request admin access from the account owner before you can export. See [[clients/ahs/index]] for the specific access issue encountered.

---

## Long-Term Fix: Zapier Integration

Zapier has a native trigger for Google Ads lead form submissions. The recommended Zap:

| Step | Detail |
|------|--------|
| **Trigger** | Google Ads — New Lead Form Entry |
| **Action** | MarketSharp — Submit New Lead |
| **Description** | "Submit new Google Ads lead entries to MarketSharp for efficient lead management" |

### Setup Steps

1. Log into Zapier (use the team account at asymmetric.pro domain)
2. Create a new Zap; search for the Google Ads → MarketSharp template
3. Authenticate both the Google Ads account and MarketSharp
4. Map fields: name, email, phone, GCLID, campaign name
5. Test with a live submission before activating

> **Note:** Zapier domain access controls may block personal Gmail accounts from authenticating under the team Zapier org. Use the team Google account where possible.

---

## Lead Quality Considerations

Native lead forms lower friction for the user (no redirect to a landing page), which can increase volume but may also widen the geographic spread of leads.

**Signals to watch:**
- Phone number area codes inconsistent with target service area
- Email addresses with no local indicators

**Mitigation options:**

1. **Tighten geographic targeting** in the campaign settings — only serve ads to users physically located in the target market
2. **Add a zip code field** to the lead form — zip code is low-friction for users and immediately surfaces out-of-area leads without requiring address entry
3. Review lead quality with the client (Gina at AHS) after delivering the CSV; adjust targeting if too many leads are outside the service area

---

## Related

- [[clients/ahs/index]]
- [[knowledge/integrations/zapier-overview]] *(if exists)*
- [[knowledge/paid-search/performance-max-best-practices]] *(if exists)*
- [[knowledge/crm/marketsharp-lead-intake]] *(if exists)*