go-find-out
A tracking-health monitor for the plumbing between your ads and your CRM.
Ad platforms optimise against the conversions they are told about. When the
path from a click to a CRM record is broken — a click identifier that never
reaches the contact, a conversion that never travels back — nothing errors.
Campaigns keep spending, and the bidding quietly optimises against
incomplete data. go-find-out checks that path and reports what is broken.
What it checks today
- Whether the CRM has properties to store UTM parameters at all.
- Whether it has anywhere to store a Google click identifier.
- What share of recent contacts arrived with any source data attached.
- What share of paid-looking contacts arrived with a click identifier.
- Whether the ad account has a conversion action configured to receive offline conversions.
- Whether conversions are coming back against the click identifiers that were captured, or whether the loop is silently broken.
How it works
It reads. Two API connections — the CRM and the ad account — and a set of
rules that are pure functions over the evidence those connections return.
Nothing is written to either system, and nothing is added to your website.
What it deliberately does not do
- It does not repair anything. Detection and repair are separate problems, and only the first one is built.
- It does not load your pages. Problems that live in the browser — a tag included twice, a script a builder stripped out — are outside what API reads can see, and it says so rather than guessing.
- It does not assert a cause it cannot distinguish. Several different failures produce the same evidence; where that is true, the report names the candidates and stops.
- HubSpot and Google Ads only. Other CRMs and other ad platforms are not supported.
Status: in development. This is early work, not a
product you can buy yet. It has not been run against enough real accounts
to make claims about how well it performs, and this page deliberately
makes none.
Contact
YOUR_LAB_CONTACT_EMAIL