Intern
What you actually do
Stopwatch and the count match. Campaign field. You do not copy-paste from the agency email into GHL as the process.
Library / Wire / Google lead forms are not a CRM. Ingest them like a clock.
Google Lead Form extensions and lead form assets fail the same way Meta Instant Forms fail: ingest lag, mashed source tags, no phone clock, and a human who 'checks Google Ads in the morning'. Wire the form to GHL the same day, with campaign fields and a speed path that is not a weekly export.
Google Lead Form extensions and lead form assets fail the same way Meta Instant Forms fail: ingest lag, mashed source tags, no phone clock, and a human who 'checks Google Ads in the morning'. Wire the form to GHL the same day, with campaign fields and a speed path that is not a weekly export.
Treat Google lead forms with the same respect as a website form — they are paid demand. A 12-hour delay is not 'sync'. It is lost speed-to-lead.
Map questions to spec fields. Google’s default 'full name' still needs first/last if your CRM does. Phone format agreed.
gclid belongs on the contact when you have it, so offline conversion import is possible later. Do not skip identity work because 'we only care about calls'.
If an agency owns the Google account and the leads go to their inbox, you do not have a system. Ingest must land in your GHL.
Do not run Google lead forms and a website form as two uncompared sources. Both write the same pipeline with different source tags so you can see which clock is worse.
Intern
Stopwatch and the count match. Campaign field. You do not copy-paste from the agency email into GHL as the process.
Operator
Treat Google lead forms as paid phone-leads. Same clock discipline as Meta. Keep source comparable on one pipeline.
CEO
If Google Ads and GHL disagree on volume, you are managing folklore. Ingest match and speed-to-lead are the numbers, not the agency dashboard.
Google Ads lead form asset, webhook or native GHL Google integration, GHL contact, phone, source:google, campaign/ad group fields, gclid if present, opportunity, Conversations SMS, SLA clock.
Lead form submit → GHL contact in minutes; Google Ads is not the database
Campaign, ad group, form name → fields; source:google separate from offer
In-hours → SMS or call task inside the speed window
Webhook failure → alert to an owner; CSV is incident response, not the process
Native integration or one webhook to GHL. Remove 'email leads to the agency' as the primary destination. Agency can get a copy if they must — copy is not system of record.
Why: Agency inboxes are how leads get cherry-picked and how you cannot measure speed.
Done when: Test submit from the lead form appears in your sub-account.
Name, email, phone, extra questions, campaign, ad group, lead form asset name, timestamp, gclid.
Why: Without campaign fields you will scale the wrong asset. Without phone you cannot run the clock.
Done when: Test contact shows campaign and phone.
Same SMS workflow pattern, trigger on source:google or a Google-specific stage if the pitch differs. Do not copy-paste a Meta message that mentions Facebook.
Why: Wrong-network copy is how you look careless in minute one.
Done when: Google test lead gets Google-appropriate first SMS under the SLA.
If no leads in GHL while Google shows submissions, P1. Owner named. CSV only to recover an outage, then throw away the process.
Why: Silent token death is common. You will optimize ads on an empty CRM.
Done when: A written check: Google submissions vs GHL source:google this week.
Speed-to-lead and show rate for source:google vs site form vs meta. Do not blend.
Why: A blended CPL hides that Google lead forms are slow and website forms close.
Done when: Three rows, not one vanity CPA.
Submit the Google lead form with a unique phone. Time ingest and first SMS. Confirm campaign fields. Confirm the agency inbox is not the only copy. Compare timestamp in Google Ads vs GHL. If lag is hours, that is the ticket — not new ad copy.
More Google spend on lead form assets until ingest is minutes and the agency is not the system of record. Buying faster into a slow inbox raises CPA and nobody can see why.
Leads email to a shared inbox. VA copies into GHL when she can. Source is 'google' for everything including organic. No gclid. Speed-to-lead is 'we try to call same day'. Google Ads shows conversions that GHL never met. That is a vendor report, not an operating system.
One test lead: GHL in minutes, fields mapped, SMS under SLA, source and campaign separate. Weekly count: Google UI submissions vs GHL. Outage alert named. No CSV ritual.
If Google lead forms are already spending, they need a router now. A prettier site form does not justify a CSV lag on paid leads.
Then you cannot operate. You can share reporting. System of record is your GHL.
Usually no. Same jobs, different source. A separate pipeline is how definitions drift. Split with tags and fields.
This week
This week: ingest to GHL, field map, speed SMS, Google vs GHL count, agency inbox demoted. No extra lead form assets.
A full calendar and an empty pipeline is two databases.
Read ↗A high score in a CSV is not a qualified opportunity.
Read ↗If the thank-you does not change the contact, the page was a brochure.
Read ↗If paid lives in Stripe and the opportunity is still open, reporting is theatre.
Read ↗Working notes
The minimum CRM, pipeline, and nurture spec before you add more pages. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.