Tracking

tracking_reports_source_people

List the people (profiles) behind one channel / UTM row from the revenue-by-source report, under the same model + window.

Tool

tracking_reports_source_people

List the people (profiles) behind one channel / UTM row from the revenue-by-source report, under the same model + window.

List the people (profiles) behind one channel / UTM row from the revenue-by-source report, under the same model + window. Keyset-paginated; each person carries their attributed lifetime revenue per currency.

Behavior

HTTP: GET /tracking/reports/source-people

Arguments

Name	Type	Required	Description
to	string	•	No description in the catalog.
from	string	•	No description in the catalog.
limit	integer	—	People per page (default 50, max 200)
model	string	—	No description in the catalog.
cursor	string	—	Opaque keyset cursor from a previous page
domain	string	—	No description in the catalog.
channel	string	•	Channel to drill into
utmNulls	string	—	Comma-separated dimension names (utmSource,utmMedium,utmCampaign,clickIdType) that must be IS NULL
utmMedium	string	—	No description in the catalog.
utmSource	string	—	No description in the catalog.
clickIdType	string	—	Native click-id type of the breakdown row to drill into (e.g. 'gclid'). Tri-state: omit for no filter (all click ids), pass a value to match it, or list 'clickIdType' in utmNulls to match the IS-NULL row.
utmCampaign	string	—	No description in the catalog.
lookbackDays	integer	—	No description in the catalog.

Response

Field	Type	Always	Description
cursor	string	•
people	array	•

Try it

List the people (profiles) behind one channel / UTM row from the revenue-by-source report, under the same model + window.

When to use

Example

Ask your agent something like this:

List the people (profiles) behind one channel / UTM row from the revenue-by-source report, under the same model + window.

The agent will invoke tracking_reports_source_people with these arguments:

{
  "to": "<to>",
  "from": "<from>",
  "channel": "<channel>"
}