Attribution Analytics

Attribution

Retrieve conversion attribution and filtered conversion correlations for attribution dashboards.

Audience: Analysts who need touchpoint credit allocation for conversion events.

Critical: Attribution is event-scoped via GET /api/v1/analytics/events/:eventId/attribution. Dashboard conversion discovery is provided via GET /api/v1/analytics/correlations/:siteId with optional date range filters.

Journeys Revenue Analytics Event Types

Who This Page Is For

Use this page when you need to discover conversions in a date range and inspect model-based credit for a selected conversion event.

Quick Start (2-5 Minutes)

Fetch conversion correlations

Query conversion groups with conversionProfile and optional startDate/endDate.

GET /api/v1/analytics/correlations/:siteId?conversionProfile=commerce&startDate=...&endDate=...

Call attribution endpoint

Request attribution with default or explicit model parameter.

GET /api/v1/analytics/events/:eventId/attribution?model=last_touch

Compare models

Run first_touch, last_touch, linear, time_decay, and position_based for scenario comparison.

model=first_touch|last_touch|linear|time_decay|position_based

Interpret touchpoint credits

Map returned credits to campaign, recommendation, or other entities.

Use credit distribution for spend and placement optimization.

Tie to revenue analysis

Cross-check attribution with revenue endpoints for allocation consistency.

See /analytics/revenue-analytics

Implemented attribution endpoint

GET /api/v1/analytics/events/:eventId/attribution?model=first_touch|last_touch|linear|time_decay|position_based

Implemented conversion discovery endpoint

GET /api/v1/analytics/correlations/:siteId?conversionProfile=commerce&startDate=ISO_DATE&endDate=ISO_DATE

Required Fields / Minimum Payload

Field	Required	Type	Used by events	Description
`eventId`	Required	`uuid/string`	Attribution endpoint	Tracked conversion event identifier.
`model`	Optional	`first_touch \| last_touch \| linear \| time_decay \| position_based`	Attribution endpoint	Attribution model selector. Defaults to first_touch if omitted/unknown.
`Authorization`	Required	`Bearer token`	Attribution endpoint	Authenticated analytics access required.
`startDate / endDate`	Optional	`ISO timestamp`	Correlations endpoint	Filters returned conversions by conversion event timestamp.

Example request

GET /api/v1/analytics/events/:eventId/attribution?model=position_based

Attribution response (v3 contract)

{
"model": "FIRST_TOUCH",
"conversionProfile": "commerce",
"conversionEventId": "evt_123",
"conversionEventAt": "2026-02-12T17:39:48.000Z",
"attributedTouchpoints": [
  {
    "entityType": "page",
    "entityId": "home",
    "firstTouchAt": "2026-02-12T17:39:28.000Z",
    "lastTouchAt": "2026-02-12T17:39:48.000Z",
    "touchCount": 10,
    "position": 1,
    "credit": 1,
    "creditPercent": 100
  }
],
"totalTouchpoints": 25,
"totalInteractions": 187,
"totalValue": 1,
"cacheVersion": 25
}

Legacy compatibility note:

totalTouches has been removed from the response.
Use totalTouchpoints for unique touchpoint count and totalInteractions for raw interaction volume.

Event or Endpoint Decision Matrix

Scenario	Use This	Why
Need credit for one conversion event	/analytics/events/:eventId/attribution	Canonical implemented attribution route.
Need conversion list for a date range	/analytics/correlations/:siteId	Returns conversion groups with conversionEventId and conversionEventAt.
Need first interaction credit	model=first_touch	Useful for awareness-oriented analysis.
Need last interaction credit	model=last_touch	Useful for direct response optimization.
Need equal multi-touch credit	model=linear	Simple shared-credit interpretation.
Need time-sensitive weighted credit	model=time_decay or model=position_based	Captures recency or first/last emphasis.

Common Errors and Fixes

Attribution response is null

Cause: eventId not found or inaccessible under current site access.

Fix: Validate eventId existence and user access to event site.

Model value ignored

Cause: Unsupported model string provided.

Fix: Use one of supported model names; unknown values fall back to default.

Credits differ from expected business report

Cause: Different attribution model used across reports.

Fix: Standardize attribution model at report definition level.

Request made to unsupported attribution route

Cause: Legacy non-implemented path usage.

Fix: Use only /analytics/events/:eventId/attribution.

Production Checklist

Conversion event IDs are preserved in analytics workflows for attribution lookups.Required
Attribution model default is documented for business stakeholders.Required
Revenue and attribution reporting use aligned date windows and filters.Required
Legacy unsupported attribution paths are removed from client tooling.Required
Attribution outputs are validated against sample journeys periodically.Required