# Determine your Program's ITP Compliance

<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>

The Apple Safari browser (both desktop and mobile) includes *Intelligent Tracking Protection* (ITP), which blocks third-party cookies. In some instances, this can affect your program's tracking and attribution abilities. [Learn more about ITP](https://impact.com/marketing-intelligence/get-the-faqs-on-itp-and-know-youre-a-ok-on-impact/).

#### ITP & impact.com at a glance

* If you're tracking conversions via a legacy pixel, iframe, or image, ITP will affect your tracking — you'll need to migrate to an alternative impact.com tracking integration in order to be ITP compliant.
* If you're using API, FTP/Email, or an eCommerce plug-in tracking integration, you're already ITP compliant.
* If you’re using the Universal Tracking Tag (UTT) to track and report conversions, verify that your configuration matches with the instructions below.

#### Custom Tracking Domains

In most cases, *Custom Tracking Domains* are already ITP compliant if they're on the same domain as your site — third-party cookies aren't used for tracking. Follow the steps below to review your configured tracking domain.

1. From the top navigation bar, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-1183576591b45997efe4dc81a25024640591d02a%2F245137dc972a7a7f6165b59538fcdbac8fd5bd8fee4ba9f20c1a2982c5b58b57.svg?alt=media) **\[User profile] → Settings**.&#x20;
2. In the right column, go to the *Tracking* section and select [General](https://app.impact.com/secure/advertiser/tracking-settings/general-trackingsettings-flow.ihtml?).
3. On the *General Tracking Settings* screen, find the **Tracking Domain** line item.

   <div data-with-frame="true"><figure><img src="https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-e9ab136a2e1410d4e0848b65e42b2eb16dba79fd%2F2572badfcce63ccb6ea8e05586f73428d7b91afcd13e475b0a1fdc3a9084dad3.png?alt=media" alt=""><figcaption></figcaption></figure></div>

Custom domains URLs should be on the same domain as your site (e.g., `goto.example.com` for `example.com`), whereas impact.com domains will be short (e.g., `pxf.io`, `sjv.io`, etc.). If you have a custom tracking domain that matches your site's domain, ITP shouldn't affect your program.

#### Universal Tracking Tag (UTT)

If you're using UTT for your tracking solution, verify your *Program Tracking Template* has `irclickid = {clickid}` as one of the query string parameters that's appended to the landing page.

**Campaign Tracking Template**

1. From the top navigation bar, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-1183576591b45997efe4dc81a25024640591d02a%2F245137dc972a7a7f6165b59538fcdbac8fd5bd8fee4ba9f20c1a2982c5b58b57.svg?alt=media) **\[User profile] → Settings**.&#x20;
2. In the right column under the *Tracking* section, select [Gateway](https://app.impact.com/secure/advertiser/tracking-settings/gateway-trackingsettings-flow.ihtml?).
3. Find the *Program Tracking Template* line item. Confirm there's a query string parameter configured **exactly identical (case-sensitive)** to `irclickid = {clickid}`.
4. If you’ve made any changes, select **Save**; otherwise select **Cancel**.

**Verify the UTT is firing**

1. With your browser’s developer tools open to the Network panel/tab, copy your website's URL into your browser's URL and press **Enter**.
2. In the network panel, filter the list of requests for **Impact**.
3. If the UTT is firing, you’ll see a request with a 200 response code from `utt.impactcdn.com` with a uniquely named JavaScript file.
4. Navigate to other pages on your site and verify that the UTT is firing on those pages as well.
5. Repeat steps 1–4 with a different browser (if you have access to MacOS, try using Safari to verify the UTT is appearing).
