# Set Up a Custom Tracking Domain

You can set up your own custom tracking domain for your Performance or Creator program within your account's technical settings. You’ll need to configure, verify, and activate your custom tracking domain. If you have an Advocate program, learn how to [set up a custom domain for Advocate](https://help.impact.com/brand/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/set-up-a-domain-for-advocate).

#### Configure a custom tracking domain

![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-ce68cfb317a0bdf2b9e82f3df63b400f7764cbf2%2F6b9ec025210c2878ab8e126697a41af04cef94403a452d5dee89cf87e9f2cf2d.svg?alt=media) This feature is only accessible to specific impact.com editions or add-ons. [Contact us](https://app.impact.com/support/portal.ihtml?createTicket=true) to upgrade your account and get access!

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**. 
2. On the left, under *Account Settings* → *Technical*, select **Tracking Domains**.
3. Select **Create Tracking Domain**.
4. In the **Domain** field, enter the subdomain you want to use, e.g., `goto.yourcompany.com`.
5. Optionally, below *Redirect Malformed Requests* select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-d2954616dc486c3e12c9211e20ff376bda0ab1af%2F7586e04e82e7c7203e5c82320dd417f8ac564cae5035024fdf0eb2ed017e6376.svg?alt=media) **\[Checkbox]** to redirect to a default landing page if a malformed request was made.
   * Enter your default landing page's URL.
6. Select a **Configuration Type**.

{% tabs %}
{% tab title="Custom Proxy Configuration:" %}
(Recommended) Set up a proxy through the network serving your website, ensuring the tracking domain shares the same IP address range as your website. This method is recommended for brands wanting improved tracking reliability.

**Custom Proxy Configuration instructions**

Follow our guided steps to configure a CNAME record and establish a proxy connection to impact.com's tracking service.

These instructions are tailored for Cloudflare, but similar configurations can be done on other networks such as Akamai, CloudFront, and Fastly. The specific steps may vary, but the general process of setting a proxied CNAME and configuring SSL rules is universal.

**Add the DNS record**

1. Sign in to Cloudflare and select the relevant domain from your dashboard.
2. In the *DNS* section, select **Add Record** and complete the fields:
   * **Type**: Select **CNAME**
   * **Name**: Enter your desired domain, e.g., `goto.yourcompany.com`
   * **Target**: Set to `customtracking.impact.com`
   * **Proxy Status**: Select **Enable** (cloud icon should be orange)
   * **TTL**: Leave as **Automatic**

**Configure rules and SSL**

1. In Cloudflare, go to **Rules** → **Configuration Rules**.
2. Select **Create Rule**.
3. Complete the fields:
   * **Rule Name**: Define a unique name for the rule.
   * **URL**: Input your domain with asterisks before and after your domain, e.g., `*goto.yourcompany.com*`.
4. Below the *SSL* heading, use the drop-down list to select the **Full** encryption mode.
5. Select **Deploy** to activate the rule.
6. Drag the rule to the top of the *Configuration Rules* list to prioritize it.
   {% endtab %}

{% tab title="Express Domain Integration:" %}
Integrate by making a single CNAME change. impact.com handles the technical intricacies, allowing you to enhance brand consistency with minimal setup effort.

**Express Domain Integration instructions**

1. Sign in to your domain provider's website.

2. Look for the DNS or domain management area.

3. Modify the DNS records.
   * In the *Host* or *Alias* field, enter your selected domain.
   * In the *Type* or *Record Type* field, select **CNAME**.
   * Set the CNAME record for your domain to `customtracking.impact.com.cdn.cloudflare.net`.

4. Confirm and save your new DNS settings.
   {% endtab %}
   {% endtabs %}

5. Select **Save**.

#### Verify your domain

Once you've updated your domain's settings, return to your impact.com account to verify your domain and confirm it's correctly configured.

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**. 
2. On the left, under *Account Settings* → *Technical*, select **Tracking Domains**.
3. Hover your cursor over the domain and select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-8ec3e877b1397045c61d394485e72ac4d93120ee%2Fc6ddb46c637059f06e86c790a911217a9428f5c47b5efef046f90555e85b03cd.svg?alt=media) **\[More]** → **Verify**.
4. Select **Verify** at the bottom of the page, then select **Finish** to exit.
   * If your domain is verified successfully, it will be listed as `VERIFIED`. Please allow up to 48 hours for the verification process to take effect.
   * If there are any issues, impact.com will check the domain status regularly and notify you via email once it's fully configured and ready for use.
5. Finally, activate your verified domain.

#### Activate your verified domain

Your custom tracking domain will remain dormant until you complete these steps. Assigning your custom domain to programs ensures that all future tracking links utilize your custom domain. Links using the previous tracking domain will continue working and automatically redirect through your new custom tracking domain.

{% hint style="info" %}
**Note:** The impact.com platform will assign new tracking domains to all your programs by default. If you’d like to set up a tracking domain for a specific program, please [contact support](https://app.impact.com/support/portal.ihtml?createTicket=true).
{% endhint %}

{% hint style="info" %}
**Tip**: Coordinate changes to your tracking domain with your partners so that they can update their existing tracking links accordingly. This helps reduce any unnecessary latency when they get redirected to your site.
{% endhint %}

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**. 
2. On the left, under *Account Settings* → *Technical*, select **Tracking Domains**.
3. Hover your cursor over your domain and select **Set For All Programs** to assign your domain across your programs.
   * It is recommended that you ask your partners to update their tracking links. They can learn to do so by visiting [Create Tracking Links](https://app.gitbook.com/s/b2rE79d9UhOKZQLgzSqx/what-would-you-like-to-learn-about/platform-features/tracking/tracking-links/create-and-manage-links/create-tracking-links).

#### Update Your Universal Tracking Tag (UTT)

If you're utilizing impact.com's Universal Tracking Tag (UTT) for tracking, now is a good time to update the tag’s script host. Previously, you might have used utt.impactcdn.com or d.impactradius-event.com as your script host. However, to maintain brand consistency and leverage your new verified domain, switching to your branded domain for the UTT script host is recommended. Changing the host of the script tag is not required for tracking to continue working.

1. Locate the UTT script tag within your website's code, tag manager, or any platform where you've integrated the UTT.
2. Replace the script host found in the tag (utt.impactcdn.com or d.impactradius-event.com) with your new branded domain host.
3. Save and publish the changes.

After completing these updates, ensure you test the functionality of the UTT to confirm that tracking remains unaffected and operates as expected with the new script host.