RiskSignal checks the conversion tracking on your client sites, every day, using only what any visitor's browser can see. No access, no credentials, nothing installed.
When a client's tracking stops working, you get an email naming the client, what broke, and when it was last seen working. Once a week you get a short note confirming how many of your sites were checked and anything we could not reach.
RiskSignal is built and run by Jarvis Price.
It started as a tool for surfacing technical problems on commercial sites. The turning point was noticing which of those problems actually cost someone money: conversion tracking that fails silently. Nothing errors, the dashboards keep producing numbers, and the numbers are wrong. An agency reporting on twenty-five client accounts is the party that eats it, and is the least likely to catch it in time.
When you reach out, you talk to us directly. The contact form on the homepage comes straight to us. You can find us here:
RiskSignal produces structured external scan output and the verified alerts built on top of it. It is honest about where that output ends.
A daily check of publicly observable conversion tracking on your client sites, run on both desktop and a real mobile viewport, where most of the revenue and most of the breakage actually is.
A record of what each client's tracking looked like on every previous day, which is what makes "this changed" a fact rather than a guess.
An email when something breaks, confirmed by a person first, and a weekly note stating how many sites were checked and anything that could not be reached.
Not financial, legal, or investment advice.
Not penetration testing, implementation work, or automated monitoring.
Not a guarantee of revenue impact or conversion outcomes. Findings describe what a visitor's browser can observe from outside, and nothing beyond that.
The full boundaries live in the Scope & Limitations page.
Every client site is scanned by Ægis, our diagnostic engine, which loads the site the way a visitor would and records which conversion tracking actually runs.
We detect two things: a tracking tag that is absent, and a tag that is present but sends nothing on a passive visit. That is the whole detection surface, and we state it plainly because the boundary matters.
A difference is only treated as real after two consecutive scans agree, and a person opens the site and watches the tag before any alert is sent.
We cannot see conversion event values, deduplication, or consent-mode configuration, because none of those can be observed without completing a purchase. The honest claim is that a tag is gone or silent, never that a client's tracking is correct.
The method, exclusions, and refund policy are defined in full in the Scope & Limitations page.