> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/tracking/javascript-tag-tracking/tracking-with-universal-tracking-tag-utt.md).

# Tracking with Universal Tracking Tag (UTT)

<a href="https://pxa.impact.com/student/activity/1117597?sid=0c0e3e5c-54c9-4435-9bee-ebcdccb7f292&#x26;sid_i=0?utm_source=app.impact.com&#x26;utm_medium=owned-platform&#x26;utm_content=tra-350&#x26;utm_campaign=help-center" class="button primary">Take the PXA course</a>

Placing the **Universal Tracking Tag (UTT)** in the head section of every page on your site is strongly recommended for most implementations. When deployed universally across your site, the UTT will provide the most comprehensive tracking information about the consumer journey, direct traffic, and conversion paths. The UTT uses first-party cookie tracking technology to build more accurate conversion paths and enhance impact.com's other cookie-less tracking methodologies, as well as expand the levels of data that can be received and displayed in reporting.

If you are not currently using the UTT and are interested in switching over, we recommend that you [contact support](https://app.impact.com/support/portal.ihtml?createTicket=true) so we can guide you through the migration process.

## Deprecating third-party cookies

With third-party cookies being [phased out in 2023](https://blog.google/products/chrome/updated-timeline-privacy-sandbox-milestones/), the UTT sets cookies in a first-party context, so it will remain unaffected by this phase-out. The most popular browsers, such as Chrome, Safari, and Firefox, still support the UTT in its default configurations.

**Learn more**

For additional reading on this change, see these articles:

* [What the New Google Chrome Privacy Updates Mean for You](https://impact.com/marketing-intelligence/what-the-new-google-chrome-privacy-updates-mean-for-you/)
* [Chrome 80 Is Here — Are You Ready?](https://impact.com/news/chrome-80-is-here-are-you-ready/)

## UTT Configuration

For the most accurate tracking, you must place the **UTT**, in the head section of every page on your site. The `identify` function should then be placed in the body section of every page on your site so that it is invoked after the UTT. The **Conversion Pixel**, also known as the `trackConversion` function, should be placed in the body section of the *Confirmation* or *Thank You* page.

{% hint style="info" %}
**Note:** **Direct Tracking** and **Advanced Crediting Rules** are not applicable to Standard edition accounts. [Contact support](https://app.impact.com/support/portal.ihtml?createTicket=true) if you are interested in either of these features.
{% endhint %}

## **UTT Example**

```programlisting
<script type="text/javascript">

(function(a,b,c,d,e,f,g)
{e['ire_o']=c;e[c]= e[c]||function(){(e[c].a=e[c].a||[]).push(arguments)};
f=d.createElement(b);
g=d.getElementsByTagName(b)[0];f.async=1;
f.src=a;g.parentNode.insertBefore(f,g);})
('//d.impactradius-event.com/A000000-40b8-4537-b9b1-7e64006431fd65535.js',
'script','ire',document,window);

</script>
```

{% hint style="info" %}
**Note:** The UTT is **account specific**. To get the UTT for your account, refer to your technical implementation plan or [contact support](https://app.impact.com/support/portal.ihtml?createTicket=true).
{% endhint %}

## Additional resources

* Read more about UTT JavaScript [Functions](/brand/what-would-you-like-to-learn-about/platform-features/tracking/javascript-tag-tracking/tracking-with-utt-javascript-functions.md) and [Parameters](/brand/what-would-you-like-to-learn-about/platform-features/tracking/javascript-tag-tracking/tracking-with-utt-javascript-parameters.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/tracking/javascript-tag-tracking/tracking-with-universal-tracking-tag-utt.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.