.png){kind=small}
GTM Layer · Last updated 7 November 2026
The Revenue Leak Scan connects to your HubSpot portal read-only, finds where revenue is leaking, and emails you the report. Setup is one OAuth screen and takes under a minute; the scan itself usually finishes inside ten. This page walks through the whole thing, including what we access and how to uninstall.
You need a HubSpot account with permission to install apps (a super admin, or a user your admin has granted App Marketplace access). That is it. No forms, no card, no call.
Find the Revenue Leak Scan in the HubSpot App Marketplace and select Install app.
HubSpot shows the account picker, then the permissions screen. The scan requests read-only access to deals, contacts, companies, owners, pipelines and property metadata, plus leads if your portal uses that object.
Two things worth knowing as you look at that screen. The app has no write permissions, so it cannot change anything in your portal. And your raw records are never stored: each scan reads them through the connection, computes your report inside a temporary environment that is destroyed when the run ends, and we keep only the computed report. The full detail is in our Privacy Policy.
Select Connect app.
You land on your connection page at scan.gtmlayer.com. It confirms the install worked and updates live while the scan runs. Most portals take a few minutes; large ones can take longer, and you do not need to keep the page open.
When the scan finishes, the page flips to Your report is ready, and the report lands in the inbox of the person who installed, sent from reports@gtmlayer.com. The email link is private to your portal and does not expire.
If the email has not arrived within fifteen minutes, check spam and quarantine first, then email liam@gtmlayer.com and we will chase it down.
The scan re-runs automatically each month and emails you a fresh report, so you can see how the numbers move over time. No action needed from you between scans.
The headline is the value of open pipeline showing at least one leak signal, built only from signals your data can actually support. Where a field is too sparsely populated to trust (a common one is Next Activity Date), the report flags it and keeps it out of the headline instead of inflating the number. The data trust score tells you how much weight the rest of the report can bear, and fixing what drags it down is usually the fastest win on the list.
In HubSpot: Settings → Integrations → Connected Apps → Revenue Leak Scan → Uninstall. That revokes our access straight away and stops all future scans, and we delete the stored access tokens the next time the app checks in. Your existing report link keeps working, because the report is yours; email us if you would rather we delete it.
liam@gtmlayer.com. We are the team that built it, so replies come with answers rather than ticket numbers.