Skip to main content
GET
/
api
/
analytics
/
conversions
/
details
Conversion Analytics
curl --request GET \
  --url https://api.linquid.io/api/analytics/conversions/details \
  --header 'X-API-Key: <api-key>'

​
Conversion Analytics

Conversion analytics routes expose conversion summaries and tab-specific views used across workspace, campaign, and link analytics pages.

​
Core endpoints

  • GET /api/analytics/conversions/details
  • GET /api/analytics/leads
  • GET /api/analytics/leads/timeseries
  • GET /api/analytics/leads/breakdown
  • GET /api/analytics/sales
  • GET /api/analytics/sales/timeseries
  • GET /api/analytics/sales/breakdown
  • GET /api/analytics/composite
  • GET /api/analytics/funnel

​
Shared filters

​
days
number
default:"30"
Date-range window.
​
campaignId
string
Optional campaign scope.
​
linkId
string
Optional link scope.
​
timezone
string
Optional timezone for time-bucketed responses.
​
currency
string
Display currency on conversion details where applicable.

​
Conversion details extras

/conversions/details also supports:
  • pixelId (legacy pixel conversion scope)
  • granularity (day or month)
  • limit (recent rows / by-rule slices)
Response includes:
  • summary
  • breakdown
  • timeseries
  • by_rule
  • recent_conversions

​
Lead and sale semantics

  • Lead analytics represent non-revenue conversions.
  • Sale analytics represent revenue-bearing conversions.
  • Funnel responses include monotonic normalized stages (clicks >= leads >= sales) plus raw stage counts.
  • Composite response returns clicks + lead + sale totals in one payload.

​
Typical failures

  • 500 CONFIG_ERROR when analytics backend is unavailable
  • 500 INTERNAL_ERROR on upstream query failures
  • 403 when permission or plan access is insufficient