> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iqrush.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Read AI referral traffic — HTTP

> Read sessions, users, and conversions attributed to tracked AI referral sources.

Read sessions, users, and conversions attributed to tracked AI referral sources.

**Method:** `GET`

**Path:** `/projects/{project_id}/ga4/ai-traffic`

Use the HTTP base for your authorized environment and an `Authorization: Bearer` header. See [authentication](/developers/guides/04-authentication) and [HTTP setup](/developers/guides/06-http-quickstart).

## Parameters

This table covers the standard read profile. It excludes internal application routes and advanced analysis controls.

| Name | Location | Type | Required | Default | Meaning |
| - | - | - | - | - | - |
| `project_id` | path | string | Yes | — | Project ID from list\_projects. Select the project in the intended workspace and environment. |
| `start_date` | query | string | No | `"30daysAgo"` | Start of the requested range, as YYYY-MM-DD or a relative value such as 30daysAgo. These reads select a stored snapshot; use resolved\_window for the dates actually served. |
| `end_date` | query | string | No | `"today"` | End of the requested range, as YYYY-MM-DD or today. Check resolved\_window rather than treating the requested dates as the served period. |
| `session_source` | query | string | No | `null` | Restrict rows to one AI referral source, such as a source returned by get\_ai\_traffic\_sources. Omit to leave source unrestricted. |

## Request example

Set `IQRUSH_API_BASE` and `IQRUSH_ACCESS_TOKEN` through secure configuration. Replace project/run IDs and sample selections with values returned by your account. JSON objects and arrays are encoded as query strings.

```bash theme={null}
curl --fail-with-body --silent --show-error --get \
  --header "Authorization: Bearer ${IQRUSH_ACCESS_TOKEN}" \
  --header "Accept: application/json" \
  --data-urlencode start_date=2026-09-01 \
  --data-urlencode end_date=2026-09-30 \
  "${IQRUSH_API_BASE%/}/projects/${IQRUSH_PROJECT_ID}/ga4/ai-traffic"
```

## Read the response

Returns source/medium rows, link information, and requested/resolved period information when available.

Use the `resolved_window` for the period actually served. Referral traffic is separate from measured visibility and does not prove a particular AI answer caused a visit.

### Fields to use

These selected fields explain the example and the result to preserve. Field presence depends on the response; this is not a complete response schema.

| Field | Meaning and use |
| - | - |
| `linked` | Whether a property link exists for this project. |
| `rows` | AI-referral source/medium records when available. The unlinked example is not evidence of zero traffic. |

Selected response fields from IQRush Dev. Lists are shortened and project/run IDs are placeholders; this is not the full response.

```json theme={null}
{
  "project_id": "PROJECT_ID",
  "linked": false,
  "rows": []
}
```

This observed example has no linked Google property. It demonstrates the unavailable-integration response; it is not a zero-traffic report.

MCP equivalent: [`get_ai_traffic_performance`](/developers/tools/get_ai_traffic_performance). Use the parameters and defaults on this page for HTTP.

### Fields when linked data is available

The Dev handler defines the fields below for populated responses. They are not populated in the unlinked example shown here.

| Field | Meaning and use |
| - | - |
| `requested_range` | Original start/end request. It does not describe the full period actually served. |
| `resolved_window.date_start` | Start date of the selected stored snapshot. |
| `resolved_window.date_end` | End date of the selected stored snapshot. |
| `rows[].source` | AI referral source for this row. |
| `rows[].medium` | Traffic medium associated with the source. |
| `rows[].sessions` | Session count in the selected snapshot and source scope. |
| `rows[].users` | User count in that scope. Do not assume users can be added across sources. |
| `rows[].conversions` | Stored conversion count for that source/medium. |

## If the result is unavailable

Check HTTP status and the response’s `error` field before using data. A successful empty response does not establish a zero value. Preserve `not_available`, `not_available_reason`, `unavailable_reason`, and `linked` where returned. [Errors and recovery](/developers/guides/13-errors) shows observed examples.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.