# Tracking ID

> A tracking ID is a GUID used to group all executions of OneFuse modules

---

Site [llms.txt](/llms.txt)

---

A tracking ID groups executions of OneFuse [Modules](/docs/onefuse/concepts/module/). It is:

- Set on the OneFuse API request headers using the key `Tracking-Id`:

  | Request header key | Value |
  | --- | --- |
  | `Tracking-Id` | `<tracking_id>` |

- Generated automatically if none is provided: OneFuse generates a unique one and associates it with the resulting [Managed Objects](/docs/onefuse/concepts/managed-object/). Reference it using the field key `jobTrackingId`.
- Used to associate multiple [Jobs](/docs/onefuse/concepts/job/) together.
- Accepted as an optional parameter by most methods in [upstream provider](/docs/onefuse/concepts/upstream-providers/) integrations.

<div class="alert alert-info" role="alert">


For example, when deploying a VM using OneFuse Naming, IPAM, and DNS modules, pass the tracking ID returned from the first policy execution (Naming) to the subsequent modules (DNS and IPAM). This links all policy runs, jobs, and managed objects together under a single tracking ID.
</div>