Analytics
Broken targets
GET
/analytics/healthNeedsanalytics.viewTooltips and tour steps whose target element wasn't on the page — usually a selector broken by a UI change. Most affected first, at most 200.
Authorization
secretKeyheader
AuthorizationBearer <sk_…>A secret API key from Settings → API keys. It acts with its creator's role.
Query Parameters
days?integerTime window in days.
Default
30Value in
73090Response Body
OK
application/json- response
range*items*array<>Shell
curl -X GET 'https://app.cueston.com/api/analytics/health'Example Response
JSON
{
"range": {
"from": "2026-10-26T09:30:00Z",
"to": "2026-10-26T09:30:00Z"
},
"items": [
{
"contentType": "tour",
"contentId": 42,
"name": "Onboarding tour",
"stepIndex": 1,
"stepId": 311,
"stepTitle": "string",
"selector": "#export-button",
"targetMissing": 3,
"affectedVisitors": 0,
"lastSeenAt": "2026-10-26T09:30:00Z",
"sampleUrls": [
"string"
]
}
]
}Holdout experiment resultsGET
Goal conversion of visitors who saw the item vs. the holdout group that didn't: a two-sided two-proportion z-test, significant at p < 0.05. Rates are 0–1 fractions.
Would this person see it?POST
Explains which published guidance a visitor would get on a URL and why each item would or wouldn't show (domain, URL, schedule, audience, frequency). Read-only: nothing is recorded.