Skip to content

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

Name
Type
Required
Description
to
string
—
Show only journey events at or before this instant (ISO). Omit for the whole history.
from
string
—
Show only journey events at or after this instant (ISO). Omit for the whole history.
model
string
—
Attribution model to explain the decision under; re-reads the same history, so switching it is free (default 'last_click').
profileId
string
•
The profile id (uuid)
lookbackDays
integer
—
How far back before the conversion a touchpoint may be credited, in days (default 30).

Response

Field
Type
Always
Description
journey
object
•
What this person actually did, in order.
decisions
array
•
Holds at most one entry: the decision for this person's originating conversion, present only when that conversion falls inside the requested window. Kept as a list for callers that already read it; `originatingDecision` is the same value at a bindable path.
profileId
string
•
The person this journey belongs to, echoed back from the request.
originatingDecision
object
•
The attribution decision for this person's originating conversion — the same value as `decisions[0]`, at a path a workflow can bind. Null means the decision is not in THIS window, not that the person never converted: a conversion before `from` or after `to` is excluded here while still being their originating one. Widen the window to see it.

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.

↑↓navigate↵select