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

# Link Deep-Dive Analytics

> Rule-level, condition-level, traffic-flow, and click-path analytics for a single link

# Link Deep-Dive Analytics

Use these endpoints for per-link debugging and drilldowns.

## Endpoints

* `GET /api/analytics/:linkId/rules`
* `GET /api/analytics/:linkId/rules/:ruleId/conditions`
* `GET /api/analytics/:linkId/traffic-flow`
* `GET /api/analytics/:linkId/click-paths`

## Common behavior

* `:linkId` is validated in workspace scope.
* Soft-deleted or out-of-scope links return `404`.
* `days` is supported for range filtering on most endpoints.

## Click paths parameters

<ParamField query="limit" type="number" default="200">
  Row count cap (server bounded).
</ParamField>

<ParamField query="start" type="string">
  Optional explicit start date.
</ParamField>

<ParamField query="end" type="string">
  Optional explicit end date.
</ParamField>

<ParamField query="filterType" type="string">
  Optional path filter. Supported values include source/destination/rule/condition.
</ParamField>

<ParamField query="filterValue" type="string">
  Required when `filterType` is provided.
</ParamField>

## Traffic-flow response model

`/traffic-flow` returns graph-ready payload:

* `nodes` with source/rule/destination classes
* `links` with edge values and percentages
* `totalClicks`

## Click-paths response model

`/click-paths` returns row-oriented traversal events:

* timestamp + click ID
* source and matched rule
* destination host/URL
* optional matched conditions hash/details
* geo/device/browser fields

## Notes

* Default first-page click-paths views are cache-optimized; filtered/page>1 variants are treated as deep drilldowns.
* These endpoints are the preferred source for rule-routing diagnostics and path attribution QA.