Four of the tools I run on client accounts, public and MIT licensed.
None of these started as a side project. Each one exists because an account was quietly losing money in a way the interface never showed.
One command prints where a Google Ads account leaks money. Conversion integrity comes first on purpose: a lead action counting every click inflates the CPA and every number built on top of it inherits the error. Read-only against the API, no AI anywhere inside, markdown out.
View on GitHubSends real closed revenue back into Google Ads from a CSV: calls, clicks, or enhanced conversions. Its actual job is refusing the upload that Google accepts and then records as nothing, the silent failure that leaves an account showing zero offline conversions for a year. Dry run by default.
View on GitHubMonth-to-date pacing for every account under a manager account, delivered as one HTML email that survives both Gmail and Outlook. Google enforces a daily budget; the client contract is monthly. The guard only ever lowers budgets to hold the envelope, never raises them. 41 offline tests, and a demo mode that renders the report without credentials.
View on GitHubSelf-hosted call tracking on a Cloudflare Worker: a pool number is lent to each visitor, the carrier webhook records who called and for how long, and the qualified calls upload back as offline conversions. Not a free CallRail. The part nobody publishes is the glue between a phone call and the bidding signal. 44 tests, verified end to end on the real runtime.
View on GitHubAnyone can claim they understand conversion integrity. Fewer people will hand you the file that decides what counts and let you argue with it.
The scan prints the finding. Deciding which finding matters this month, on this budget, in this market, is the part you hire for.
Everything installs on your infrastructure with your credentials. When we stop working together, the code stays and keeps running.
Nothing here writes to an account until you pass an explicit flag. You can point any of them at a live account today without risk.
Four of the tools I run on client Google Ads accounts are public. They work on any account, they are MIT licensed, and none of them phone home. Clone one, point it at an account you own, and judge the work without talking to me first. That is the whole point of publishing them.
Send read-only access to one account and I run the same checks myself.
In writing, within 48 hours, and if it is clean I say that too.