We build software that reads ad accounts and tells the truth about them.
vboom is a software company in the Netherlands. We make one product, Vector: an analysis platform that watches Google Ads accounts, finds what is quietly costing money, and refuses to give advice when the underlying data cannot be trusted.
Vector connects to Google Ads read-only. It never creates, edits, pauses or deletes anything in an advertiser’s account.
The product
An agency specialist can properly audit a handful of accounts a week. The rest drift, and the problem usually surfaces when the client notices first. Vector is the thing that keeps looking.
It reads every account daily and reports only what is worth someone’s time.
Vector pulls performance reports from the Google Ads API into its own warehouse, runs deterministic checks over that data, and writes up what it finds in language a specialist can send to a client. Every figure is traceable to the query and date range it came from.
- Finds wasted spend — search terms, keywords and budgets nobody has opened in months.
- Checks measurement integrity first, and withholds conversion-based advice when tracking is broken.
- Measures what happened after a change was applied, against what the rest of the account did.
How we build
Read-only, enforced in code
Google publishes no read-only variant of its Ads scope, so the guarantee is kept in our own code: the provider implements no write operation, and the build fails if one is added.
Silence has to mean something
An empty report must mean “nothing is wrong”, never “we did not look”. Vector states what it checked, what it could not see, and why.
No invented numbers
Every figure in a recommendation is validated against the data it came from before it is stored. A number that cannot be reconciled is not published.
Data and privacy
Where it runs
Infrastructure, backups and logs are in the EU. Advertiser data is isolated per organisation at the database level, not by application logic alone.
What we hold
Advertising performance data and the OAuth token needed to read it, stored encrypted. No end-consumer personal data is stored. Search-term text is encrypted and kept out of logs.