Build Your Lead-Gen AI Analyst in ClaudeGA4, Google Ads, Meta and your lead listGA4, Google Ads, Meta and your lead list

Real Leads, Not Reported Leads In-depth guide to building your own AI analyst in Claude that combines GA4, Google Ads, Meta and your lead list - and where it breaks.

all three count spam

What you get (+1 bonus)

Three platforms, one Claude Project.
How to connect GA4, Google Ads and Meta to one Claude Project, from Meta's own connector to plain CSV exports, with the developer-only steps boxed so you can hand them over.
A lead list with no names.
Add the Meta instant-form leads GA4 never sees, mark each lead real, junk or duplicate in your own tool, then strip the list to 11 columns with no names, emails or phone numbers.
Rules Claude reads first.
Paste-ready project instructions, a definitions file on how each source counts a lead, and a settings file for time zones, to teach Claude to count only the leads you marked real.
15 prompts, labelled by trust.
From what a real lead costs to where the spam comes from: four SAFE lookups, eight VERIFY prompts that say what to check, and three that won't work without joined data.
A 20-minute trust test.
Five questions on one closed week, checked against each platform and your own list, with a score that tells you whether to rely on Claude's cross-source answers yet.
Where it breaks.
Spam all three platforms count, UTC exports that put enquiries made near midnight on the wrong day, a form event firing twice that looks like a great month, and a Meta connector that can edit campaigns.
+1 bonus
An AI skill for Claude, ChatGPT, Gemini or Copilot
that helps you set up the project and strip your lead list, then runs the trust test and the monthly check on your own numbers.

Free · about 15 seconds

Who it's for, and who it's not for

The owner of a small service business compares four different lead counts for the same month, written on a notepad next to an open laptop and a phone.

Who it's for

Businesses that collect leads through website forms, calls, bookings or Meta and Google lead forms, such as clinics, trades, agencies and B2B services, and run Google and Meta ads.
Whoever runs their marketing, in-house, at an agency or freelance, who has to answer "how many real leads did we get, and from where?"
Anyone whose ad platforms report more leads than the inbox shows, and who wants Claude to compare the tracking with the enquiries that reached them.

Who it's not for

Businesses that already follow every lead from ad click to deal in a report they trust - you'll know most of what's in here.
Anyone without access to the ad accounts and the lead list - you need both to connect the platforms, mark the junk and run the trust test.

What's inside

PDF · About 45 min read

Honest note

Passing the trust test proves Claude reads your sources accurately. It can't prove your tracking is right. Stripping the lead list is good data minimisation, but under GDPR pseudonymised data is still personal data; uploading counts only avoids the question. Claude only sees the phone and walk-in enquiries you log in your list. Google's own GA4 and Google Ads servers need a developer. All hours are our estimates: three to five a month, most of it the lead list.

Free · about 15 seconds