Plausible
The current Stats API is POST /api/v2/query, which tlly will not call with a stored secret.
What you can track
Visitors, pageviews, bounce rate, visit duration and goal conversions, after a script that holds the key writes one number a day to the sheet or the push address.
Credential
A Stats API key, Bearer, team-scoped. Create it: account name → settings → API keys → New API key → Stats API. It is shown once. Owners, admins, editors and billing can create one; viewers cannot. The key queries sites owned by that team, not sites where the person is only a guest.
Host, if you ever call Plausible yourself: plausible.io. Suggested name: PLAUSIBLE_KEY. Do not put it in a tlly fetch job.
Where to get it
Stats API. The documented query is:
POST https://plausible.io/api/v2/query with Authorization: Bearer and a JSON body (site_id, metrics, date_range). Metrics include visitors, pageviews, bounce_rate, visit_duration, events. Rate limit: 600 requests per hour by default.
That POST is not allowed with a stored secret. An older GET /api/v1/stats/aggregate was not on this docs page. Do not invent a v1 job.
tlly job
Sheet or push. Not a Plausible URL.
Gotchas
- bounce_rate is a percentage. visit_duration is seconds.
- Revenue metrics need a revenue goal configured in Plausible. The response shape is an object, not a bare number. Unverified as a tlly extract path because we do not call the API.
Alert ideas
Red when visitors fall under half of the usual weekday. Yellow when the signup goal (events filtered to that goal) is zero.
Verification
Checked 2026-10-26 against the Stats API page: POST /api/v2/query, Bearer, key creation steps, 600/hour, and the metric names listed above. v1 GET is unverified and not recommended.