Know which Google Ads clients need attention.
Monitoring and client reports for consultants.
Website · Start a free trial · În română · Run locally
KeySend helps Google Ads consultants and freelancers see which client accounts need attention. It reads each client's Ad Account every day, writes a weekly assessment with the evidence behind each point, and produces a branded PDF report to send to the client.
Use the hosted application at keysend.app, or run the source locally. KeySend reads your advertising data. It does not send edit requests.
- See what changed. Daily updates explain movements in spend, clicks, impressions, and results. Review account changes alongside performance and investigate possible causes.
- Check the numbers. Switch between 7-day and 30-day trends. Compare each day with earlier matching weekdays, with the historical range explained beside the chart.
- Investigate wasted spend and opportunities. Review search terms, keyword quality, and available breakdowns. Search impression-share estimates show where budget or rank may limit visibility.
- Review recommendations before acting. Read the observation, its supporting data, and the proposed action. Make the changes yourself in Google Ads.
- Keep clients informed. Receive alerts and a weekly email, then export account or campaign reports as PDFs in English or Romanian.
- Work in your language. The application supports English, Romanian, German, Spanish, French, Italian, and Portuguese. The language selected in the header also controls PDF exports: Romanian for Romanian, English for other languages.
KeySend keeps tracking limitations visible. When conversion data is incomplete or too recent, reports explain what can be judged from the available data.
The screenshots and sample reports use fictional accounts and data.
- Sign in with Google using the login you use for Google Ads.
- Connect Google Ads and select the accounts you want KeySend to monitor.
- Read your updates, explore a campaign, and export a report when you need one.
The hosted application includes a 14-day trial with no payment card. See current pricing for the subscription and account allowance.
| keysend.app | This repository | |
|---|---|---|
| Getting started | Sign in and connect Google Ads | Install Rust and start the application |
| Hosting and updates | Managed for you | You operate and maintain the application |
| External services | Configured for the hosted application | Configure your own service accounts and credentials |
| Content | Published articles, guides, and tools | A sample content catalog |
This repository contains the application source, tests, and documentation under AGPL-3.0-only. It receives source snapshots. Production infrastructure, real credentials, and production editorial content are excluded.
Install Rust through rustup, then run:
git clone https://github.com/abpaul/keysend.git
cd keysend
cargo loco startOpen http://localhost:5150. The pinned toolchain is installed on the first Cargo command. SQLite stores application data and background jobs in keysend_development.sqlite.
Public pages work without credentials. Google sign-in needs your Google client ID and secret. Connected-account monitoring and other integrations need their service configuration. Read encrypted credentials for the supported settings and setup.
To explore signed-in pages with fictional data, use the seeded browser workflow. It needs no Google credentials. This checkout does not include a production deployment guide.
Run the shared checks before you commit:
scripts/check.shThe checks run formatting, vendored-source validation, Clippy, and the test suite with a separate temporary SQLite database. Tests use stubs for Google, Stripe, AI, and email. CI can be started manually.
| Read | For |
|---|---|
| Features | Application behavior, routes, and tests |
| Agent | Investigations: operations, evidence, checks, limits |
| Architecture | Modules, data flow, and background jobs |
| Database | Tables and relationships |
| Credentials | Environment settings and encrypted configuration |
| Contributing | How changes reach the public source snapshot |
| Project terms | Names used in the code and documentation |
| Architecture decisions | Reasons behind the implementation |
About the sample content catalog
The application loads content/seo/catalog.json at startup. This repository supplies fictional articles, guides, and tools. Each entry contains a path, title, SEO title, description, publication date, optional update date, kind, cluster, search intent, related paths, call to action, and HTML body. Future entries stay hidden until their UTC publication date. The catalog also contains the tool-page script.


