AHS Google Ads Lead Form → MarketSharp Zapier Integration
Overview
A technical integration failure is preventing leads captured via a Google Ads lead form from automatically syncing into [1]'s CRM (MarketSharp). As a workaround, leads are accumulating in a CSV export inside Google Ads — but that CSV cannot currently be downloaded without elevated permissions. A Zapier automation is being built to resolve this permanently.
This issue was surfaced during the [2].
The Problem
What's Happening
The Pmax campaign (a broad-reach Performance Max campaign running across AHS's services) is generating leads through a Google Ads native lead form. These leads never reach MarketSharp — they sit in a CSV inside the Google Ads interface.
Why It Matters
- ~10 leads were captured in the week following the January 23 budget increase
- All Pmax conversions during that period came through the broken lead form
- Leads cannot be acted on until manually exported and forwarded
- Sebastian currently lacks the Google Ads permissions required to download the CSV — Mark must intervene each time
"There's some leads that are just sitting there that I want to forward to you. And when we get that connection, they'll go straight into MarketSharp, which will be great."
— Sebastian Gant, 2026-01-29
Proposed Solution: Zapier Integration
Build a Zap that listens for new Google Ads lead form submissions and automatically creates a corresponding record in MarketSharp.
Trigger: New lead submitted via Google Ads lead form
Action: Create/populate lead record in MarketSharp
This eliminates the manual CSV export step entirely and ensures leads are actionable in real time.
Dependencies
- Mark (Asymmetric developer) needs to configure the Zap — Sebastian has flagged the requirement but needs to follow up
- Mark is currently transitioning off other projects and moving focus to AHS work, so timing is favorable
Interim Workaround
Until the Zap is live:
- Sebastian requests the lead CSV export from Mark (who has the necessary permissions)
- Mark downloads and sends the CSV
- Sebastian forwards leads to Gina manually
Note: Sebastian temporarily paused the lead form to avoid accumulating leads that couldn't be contacted. Consider whether to re-enable it once the Zap is confirmed working.
Related Context: Budget Increase & Campaign Performance
The lead form issue became more visible after AHS increased PPC budget on January 23, 2026:
| Campaign | Observation |
|---|---|
| Pmax | ~10 leads generated, all via the broken lead form |
| Mold Search | Impression share increased ~1% to ~27%; limited by low search volume |
Low search volume is attributed partly to severe winter weather keeping potential customers focused elsewhere. Sebastian plans to expand keyword targeting on the Mold Search campaign to increase reach independent of budget constraints.
Action Items
- [ ] Sebastian: Follow up with Mark to build the Zapier integration (Google Ads lead form → MarketSharp)
- [ ] Sebastian: Request the current lead CSV from Mark and forward to Gina
- [ ] Sebastian/Mark: Confirm lead form re-activation once Zap is live and tested
- [ ] Sebastian: Expand Mold Search campaign keywords to improve impression share
Related Articles
- [2]
- [3]
- [4]
- [5]