treg's ad conversion tracking — what breaks, and what "verified" actually means

treg records three conversions against the ad click that produced them: signup, first successful call, first top-up. A click id lands in a first-party cookie, is persisted on the Org, three server chokepoints write rows into the AdConversion outbox, and a background worker uploads them to Google's Data Manager API.

Every failure this system has had was invisible to the obvious check. Green tests, HTTP 200s and dry runs were all reported while nothing worked. The rule below is the whole skill.

The rule

A layer is verified when you have observed real data at that layer in production. Not a mock, not a dry run, not a status code, not an agent's report.

The verification ladder

Climb it in order. Each rung has failed in production at least once.