Skip to content

Tracking

tracking_reports_attributed_journey

One person's journey with, for their originating conversion, the attribution decision explained (winning touchpoint + why) under the requested model and lookback window.

Tool

tracking_reports_attributed_journey

One person's journey with, for their originating conversion, the attribution decision explained (winning touchpoint + why) under the requested model and lookback window.

One person's journey with, for their originating conversion, the attribution decision explained (winning touchpoint + why) under the requested model and lookback window. Attribution is never locked in — changing model/window re-reads the same history.

Behavior

HTTP
GET /tracking/reports/attributed-journey/:profileId

Arguments

NameTypeRequiredDescription
tostringNo description in the catalog.
fromstringNo description in the catalog.
modelstringNo description in the catalog.
profileIdstringThe profile id (uuid)
lookbackDaysintegerNo description in the catalog.

Response

FieldTypeAlwaysDescription
journeyobject
decisionsarray
profileIdstring

Try it

One person's journey with, for their originating conversion, the attribution decision explained (winning touchpoint + why) under the requested model and lookback window.

When to use

One person's journey with, for their originating conversion, the attribution decision explained (winning touchpoint + why) under the requested model and lookback window. Attribution is never locked in — changing model/window re-reads the same history.

Example

Ask your agent something like this:

One person's journey with, for their originating conversion, the attribution decision explained (winning touchpoint + why) under the requested model and lookback window.

The agent will invoke tracking_reports_attributed_journey with these arguments:

{
  "profileId": "<profileId>"
}

Esc

Start typing to search the docs.

navigateselect