Automated Lead and Ad Reporting for a Leading University
A leading university in Bangladesh, running paid Meta campaigns for several departments and programs
Context
About this project
The university runs Meta ads for several departments and programs. Two teams had the same core problem: the data existed inside Meta, but the people who needed it did not see it in time. The program team behind an entrepreneurship program for women was recruiting through Meta lead forms, and the Computer Science department wanted to know how its ad budget was performing. The goal was simple, put the right numbers in the right inbox every morning, with no manual work.
Challenge
The challenge
- Recruitment leads sat inside Meta, so getting them meant logging in and downloading them by hand
- Meta only keeps lead form submissions available for download for 90 days, so the team had no permanent record
- Follow-up depended on someone remembering to check for new leads
- Department management had to open Ads Manager or wait for a monthly report to see how the budget was being spent
Approach
What I built
- 1
Lead capture into a client-owned sheet
Set up a Meta lead ad with an Instant Form collecting name, gender, phone, email and entrepreneurial status, whether the applicant already runs a business or wants to start one. Every submission syncs automatically to a private Google Sheet that the university owns, so lead data stays in a restricted sheet rather than a third-party tool.
- 2
A daily 10:00 AM lead digest
Every morning at 10:00 AM Dhaka time, an n8n workflow reads the sheet, keeps only the rows not yet sent and skips Meta's test leads. It builds one HTML email with a clean table and sends it through SendGrid to the program lead, with the wider team in CC. One digest a day, instead of one email per lead, lets the team work through new leads in a single sitting.
- 3
No duplicates, no empty emails
After sending, n8n stamps each row with a timestamp, so no lead is ever emailed twice. On days with no new leads, nothing is sent at all.
- 4
A daily ad account email for management
A second scheduled n8n workflow pulls the previous day's results from the Meta Marketing API, totals spend and results across the Computer Science department's ad account with a breakdown by campaign, and sends a short, readable summary to the department's management list.
- 5
Planned, built and tested with Claude
Used Claude to plan the campaign, write the lead form copy, design and code both workflows, test and debug them, and document them. The lead digest was tested end to end with dummy data before go-live, then the sheet was cleaned so only real leads remain.
Results
Outcome
- Lead access moved from manual downloads with a 90-day limit to an automatic daily email backed by a permanent sheet record
- Same-day follow-up on every new lead from the 10:00 AM digest, instead of whenever someone remembered to check
- Department management sees how the ad budget is being spent every day, not at month end, without logging in to Ads Manager
- Problems such as a paused campaign or a rising cost per result surface within 24 hours
- Marketing and management now discuss the same numbers, from the same source
- The pattern, capture, store, summarise, deliver, is reusable, so the next setup starts from a tested workflow
Key takeaways
- The data was never the problem, the delay between the data and the people who act on it was
- One good digest a day gets read, one email per lead gets ignored
- Keep the data where the client owns it, and let the automation only carry it
Project summary
- Category
- Marketing Automation & Paid Media
- Tools used
- n8nMeta Lead AdsMeta Marketing APIGoogle SheetsSendGridClaude
- Outcome
- New leads and ad performance land in the right inbox every morning, with no manual exports or Ads Manager logins
Have a similar challenge?
Let's talk through your situation and figure out the right approach.
Get in touchRelated case studies
Automated Occupancy Reporting for a Software Studio
Replaced a 25-35 minute weekly manual audit with a reusable analysis tool and a scheduled reporting workflow, after three separate automation attempts hit the same platform wall and the fix turned out to be a redesign, not a fourth attempt.
View case study →AI Engineering & Developer ToolingInternal AI-Agent Plugin for a Software Studio
Designed and shipped an internal Claude Code plugin that packages a software delivery studio's workflow into reusable skills and agents, including a deterministic on-page SEO auditor backed by a full automated test suite.
View case study →LinkedIn StrategyProfessional Safety Training Provider
Built a LinkedIn content and social strategy to strengthen brand visibility, grow professional presence, and position the business for B2B lead generation.
View case study →Related articles
Claude Code Plugins, Skills, and Agents: A Practical Guide for Engineering Teams
What a Claude Code plugin, skill, and agent actually are, how they fit together, and why packaging delivery workflow into agents pays off for an engineering team.
5 min read →AI & AutomationI Tried Claude First. It Was the Wrong Tool for the Job.
Connecting Claude to an ERP via MCP burned tokens, ate a 5-hour session limit in one pass, and gave different numbers every run. Moving the same job to a deterministic workflow fixed all of it, and taught a bigger lesson about tool fit.
3 min read →AI & AutomationHow to Actually Use Claude Code: The Power of Plan Mode
Why most Claude Code output looks like generic AI slop, and how switching into Plan Mode gives you back control of the process instead of just accepting or denying whatever comes out.
3 min read →