Get rule-based conversion-tip insights for payment pages
The 4 MVP rules from operations/analytics-and-insights.md §A4 (rule-based, no LLM): high view→checkout drop, high attempt→paid drop, expired-unviewed rate, and doc-email-bounce alerts. Shaped like InsightDto (the same contract as GET analytics/insights/dashboard), returned as its own endpoint for this Wave (not yet merged into that aggregator — see the Wave 5 report).
Business API key, e.g. vuz_ab12cdef... Created via Settings → Integrations → API Keys. Unlike partner keys, a public API key's STRING does not encode its environment — isolation instead comes from a completely separate sandbox database: a key minted on the Sandbox server (above) only ever reads/writes sandbox data and can never see or affect production, regardless of what the key looks like.
In: header
Response Body
application/json
curl -X GET "https://example.com/analytics/payment-pages/insights"[ { "id": "string", "type": "cash_flow", "category": "cash_shortage", "title": "string", "titleEn": "string", "description": "string", "descriptionEn": "string", "priority": "critical", "score": 0, "relatedEntityType": "client", "relatedEntityId": "string", "relatedEntityName": "string", "actionLabel": "string", "actionLabelEn": "string", "actionUrl": "string", "metrics": [ { "key": "string", "labelHe": "string", "labelEn": "string", "value": {}, "trend": "up", "unit": "string" } ], "icon": "string", "generatedAt": "string", "expiresAt": "string", "dismissedAt": "string", "isAiGenerated": false }]