Use cases → Reporting and data
Work out which sources actually produce customers
Join enquiry records to outcomes so spend goes where the revenue is.
| Who it is for | Anyone spending money on more than one acquisition channel. |
|---|---|
| APIs | Sheets API, Gmail API |
| Typical scopes | spreadsheets, gmail.readonly |
The problem
Channel reports count leads. Nobody joins those leads to who actually paid, so budget follows volume rather than value.
How it works
- Capture the source with the enquiry, at intake.
- Track the record through to outcome in one sheet.
- Report cost per customer by source, not cost per lead.
What changes
Spending decisions based on customers rather than form fills.
Questions people ask
What if attribution is partial?
Partial and honest beats complete and invented. Report what you can prove and label the rest unknown.
Want this built?
This is a pattern we run in production. We will set up the delegation and build this on top of it — $500 per hour, most of it working the same day.
Talk to us Or read the setup guideRelated use cases
Send a daily digest that catches problems early
One scheduled email that checks the things that fail quietly and reports only what changed.
Reconcile records between two systems automatically
Compare what your tracking sheet says against what the source system says, and report the differences.
Run automation from a spreadsheet non-engineers can edit
Keep rules, templates and routing in a Sheet so the operations team changes behaviour without a deploy.