Why this matters
Integrations are often the real activation moment for B2B and devtool products. A failed setup is not just a bug; it is a stalled customer.
What you get
- Setup failure rate by integration
- The step and error code causing the most blocked accounts
- A short list of accounts CS should help
- Engineering actions ranked by affected accounts
Walk through it
You
Which integrations are failing during setup?
Agent
I’ll compare setup starts, failures, and completions by integration and setup step.
POST /v1/projects/:project_id/analytics/query {
project_id: "default",
hogql: "SELECT properties.integration_type AS integration, properties.setup_step AS step, properties.error_code AS error_code, count() AS failures, count(DISTINCT properties.account_id) AS accounts FROM events WHERE event = 'integration_setup_failed' AND timestamp > now() - INTERVAL 30 DAY GROUP BY integration, step, error_code ORDER BY accounts DESC, failures DESC LIMIT 20"
}{
"rows": [
{ "integration": "salesforce", "step": "oauth_callback", "error_code": "invalid_scope", "failures": 42, "accounts": 17 }
]
}Agent
Salesforce OAuth scope failures are blocking 17 accounts. I’ll check whether any open cases match this pattern.
GET /v1/projects/:project_id/cases { project_id: "default", status: "open" }The output
The agent returns the integrations, setup steps, error codes, and affected-account counts that deserve action first. It should separate product-copy fixes from backend defects and CS follow-up.
Setting it up
Emit setup lifecycle events for each integration. Include the account, integration name, setup step, and normalized error code so failures can be grouped cleanly.
Variations
- “Which integration setup failures affect enterprise accounts?”
- “Show failed setup by integration version.”
- “Draft a CS follow-up list for blocked accounts.”