We check your clients' conversion tracking every day and tell you the day it breaks. Every client site you report on. A person confirms every alert before it reaches you.
Conversion tracking fails silently. A deploy drops the pixel, a tag manager container changes, a consent banner starts blocking events, and nothing errors. Reporting keeps producing numbers, they are just wrong, and spend gets optimised against them for weeks. You can see it in Events Manager. The question is whether anyone checks all twenty-five accounts, every day, before the client does.
Send a list of your client domains. No logins, no access, no pixel to install, no integration. We work entirely from what any visitor can see.
Which client, what stopped working, when it was last seen working, and what to check. Short enough to read on a phone and forward to whoever fixes it.
Ten seconds to read: how many of your sites were checked, every day, and anything we could not reach. It carries no findings and no dashboard, so the day a real alert lands it still stands out.
You already have twenty-five dashboards. This is one message, sent the morning something breaks, short enough to read on a phone and forward to whoever fixes it.
Priced by roster size. Tell us how many client sites you have and we will quote it.
By submitting you confirm all domains are provided for legitimate business purposes.
Scope & Limitations apply: risksignal.io/scope
Nothing. You send a list of domains. There are no logins, no credentials, no pixel to install and no conversation with the client, because everything we read is what any visitor's browser already sees.
Because a person opened the site and watched the tag before you got the email. Two agreeing scans raise a finding, and then it is confirmed by hand. You are not being handed a queue to triage.
Anything behind a login, anything that only fires server-side, and the contents of what a tag sends. We report whether conversion tracking is present and transmitting, not whether the values inside it are correct. The full boundary is on the Scope and Limitations page.
The next morning's scan catches it. Findings are compared against that site's own previous scans rather than against a standard, so a deploy that drops a tag shows up as a change on the day it happens.
Whenever your book changes. Pricing is banded by roster size, so swapping one client for another costs nothing and only the band matters.
Neither. It is an external scan and an alert. It does not test security, it does not give legal advice, and it does not fix what it reports.
You send client domains and nothing else. No logins, no access, no pixel to install. The first check runs the same week and you hear from us the day something breaks.
Checked daily · A person confirms every alert
Agencies that hold client retainers.
If you run paid media, analytics or growth for a book of clients, their conversion tracking is your reporting.
When it breaks, your numbers are wrong and the conversation lands on you.
Here is how that plays out depending on what kind of agency you are.
Your optimisation is only as good as the events coming back.
A dead pixel does not stop a campaign. It quietly starves the algorithm and the spend keeps going out.
Every client's conversion tags checked daily, on a schedule that runs whether or not anyone notices a number looks off.
You hear about it before the monthly report, rather than during it.
One less thing to find out about from the client.
You already audit this. Now it stays audited.
A tracking audit is accurate the day you run it and stale a week later.
The same checks you would run by hand, run every day across the whole book.
Findings arrive as a specific tag on a specific page, not a score.
The audit becomes a standing state instead of a project.
You inherited their setup. You still own the reporting.
Most client tracking was installed by somebody else, years ago, and nobody has looked since.
You find out what is actually firing across every client site you are accountable for.
Breakage after a client's own dev deploys gets caught in days.
No access or credentials needed from any of them.
The site ships clean. Then someone edits it.
Tracking that worked at launch is a different question from tracking that works this month.
Post-launch monitoring on every site you built, without a support retainer.
You are the one who tells them, rather than the one being told.
A cheap reason to stay in contact after a build ends.