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.
Google's native lead form asset stores submissions in a Google-hosted CSV, separate from any website or CRM. Key symptoms:
This is easy to miss because the campaign appears to be converting normally in Google Ads reporting.
To recover leads already collected:
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.
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" |
Note: Zapier domain access controls may block personal Gmail accounts from authenticating under the team Zapier org. Use the team Google account where possible.
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: