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: [1] — a Performance Max campaign generated ~135 untracked leads that never reached MarketSharp. See [2] 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:
- In Google Ads, navigate to Campaigns → Assets → Lead Forms
- Locate the lead form asset (look for high interaction rate — e.g., 35% interaction rate, 680 clicks is a signal)
- Click the Download / CSV icon to export all submissions
- 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 [1] 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
- Log into Zapier (use the team account at asymmetric.pro domain)
- Create a new Zap; search for the Google Ads → MarketSharp template
- Authenticate both the Google Ads account and MarketSharp
- Map fields: name, email, phone, GCLID, campaign name
- 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:
- Tighten geographic targeting in the campaign settings — only serve ads to users physically located in the target market
- 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
- 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
- [1]
- [3] (if exists)
- [4] (if exists)
- [5] (if exists)