# Connect funnel and connection outcomes

> Connect funnel and connection outcomes: CustomDomain™ API reference in the analytics group. Covers parameters, request body, responses and error codes.

Source: https://docs.customdomain.ai/docs/api-reference/analytics/getConnectAnalytics

## `GET https://api.customdomain.ai/v1/analytics/connect`

The widget funnel (sessions, how many entered a domain, were offered a one-click or sign-in rail, were shown records to copy, succeeded, where the rest stopped, per provider and root versus subdomain) and connection outcomes (live rate, time to live, per provider and method, why the rest are stuck), plus a daily series. `audience` counts the widget sessions by device type, country, browser, operating system and embed (no address, no city, no session listed), `install` whether the widget was seen in the builder's own product or only in the console's tests (per application), and `secure_sign_in` the cloud browser sessions started in the window: the funnel per provider, the failures by reason, and the same with and without a vendor proxy. Both are scoped like the rest, to the key's workspace and `app_id` when given. API key; any member role.

### Authentication

`apiKey`

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `days` | query | integer | no |  |
| `app_id` | query | string | no |  |

### Responses

| Status | Description |
| --- | --- |
| `200` | Analytics |
| `400` | Error envelope: {code, title, details}. |
| `401` | Error envelope: {code, title, details}. |
| `404` | Error envelope: {code, title, details}. |

### `200` response body

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `window` | object | yes |  |
| `widget` | object | yes |  |
| `connections` | object | yes |  |
| `daily` | array of object | yes |  |
| `audience` | object | no | Who opened the widget, from the session each widget open records (sessions from before this was recorded have none). Each list counts sessions, how many reached a finish screen (`succeeded`) and how many of their domains are live (`went_live`). Countries, browsers and systems list the eight busiest, then `other`; `unknown` is last. |
| `install` | object | no | Whether the widget has been seen in the builder's own product, per application, from the session each widget open records. A session is a console test when its token's end user is `console:<member>` (the console's Try it live and welcome domain step); every other session is the product's. The console's design preview opens no session. Counts are sessions. `application_id` narrows it like the rest; an application with no session is not listed. |
| `secure_sign_in` | object | no | The cloud browser sessions started in the window. `failures` is keyed by the failure taxonomy (bot_wall, captcha, region_blocked, vendor_error, user_cancel and the rest); `proxy_sensitive` marks the four a proxy in the customer's country could change. `proxy` has one row for the sessions without a vendor proxy and one for those with one, when there were any. |
| `truncated` | boolean | yes |  |

The full specification is served at `GET https://api.customdomain.ai/v1/openapi.json`.
