tracking_profiles_export

Tool

Export a person as JSON: profile + identity signals + full journey (capped at 50k events; truncated flag set if exceeded).

Name	Type	Required	Description
profileId	string	•	The profile id (uuid)

Field	Type	Always	Description
journey	array	•	The complete history, newest event first, capped at 50000 events — check `truncated` before treating it as complete.
profile	object	•	The person themselves: their handle, how far they have come, and when they were seen.
signals	object	•	Everything known about who this person is: the addresses they have been identified by, the ad clicks they arrived by, and the sites they were seen on. Every part of it is a list, and none of the lists names a primary.
truncated	boolean	•	True when the history hit the 50000-event cap and older events were left out. False means this export is everything held.
exportedAt	string	•	When this export was produced, ISO 8601 UTC — the as-of date to put on a subject-access response.
acquisition	object	•	First touch: the campaign that brought this person in, frozen at their earliest event and never overwritten by later visits. Null for a person with no events at all.

Export a person as JSON: profile + identity signals + full journey (capped at 50k events; truncated flag set if exceeded).

When to use

Export a person as JSON: profile + identity signals + full journey (capped at 50k events; truncated flag set if exceeded).

Ask your agent something like this:

Export a person as JSON: profile + identity signals + full journey (capped at 50k events; truncated flag set if exceeded).

The agent will invoke tracking_profiles_export with these arguments:

{
  "profileId": "<profileId>"
}