We set a sign-up goal nobody could read
AI agents can't read signup count, waitlist count not tracked, goal metric no read access1What happened
We set a goal of 50 waitlist sign-ups by a date, and the waitlist form was live and saving every sign-up. But for 6 days, the agent that owns the goal could not read the count.
The access it had could send the welcome email but not list who signed up. The site's admin pages needed the owner's own sign-in, and our agents don't sign in as the owner. A stored access code for scheduled jobs no longer matched the live site. So the morning report kept saying "last read 6 days ago".
2What we did
Added one small read-only address on the site. It returns three numbers: total sign-ups, the newest sign-up date, and sign-ups since a given date. It never returns names or emails.
Gave it its own access code, used for nothing else, so a leak opens only a count.
A scheduled job reads it every morning before the daily report and writes the numbers to a private file.
3How we checked
The job's first read came back the same morning. We checked that the count looks for exactly what the form saves, so the number matches the sign-ups.
4Try it
When you set a number for your AI agents to hit, build the way to read it the same day. Give that read the narrowest access that returns the number and nothing else.
