> 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/partner/what-would-you-like-to-learn-about/platform-features/tracking/tracking-links/create-and-manage-links/publisher-tag-implementation-for-partners.md).
# Publisher Tag Implementation for Partners
The Publisher Tag is a JavaScript snippet that automatically converts direct brand links into tracking links, captures impression data, and, with Trackonomics Essentials, enables page-level reporting.
Depending on your specific setup and add-ons, the tag provides four primary features:
| Feature | Description | Requirement |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Transform Links | Detects direct links to the landing pages of brands you work with and converts them into impact.com tracking links, so you get credit for actions that result from that traffic. | |
| Impression Tracking | Measures link visibility by tracking how often links are viewed. | |
| Page-Level Tracking | Provides granular revenue data for specific pages via the [*Overview by Story*](/partner/what-would-you-like-to-learn-about/platform-features/trackonomics/trackonomics-reports/overview-by-story-report.md) report. | |
| `identifyUser` | Captures advanced traffic data for more precise conversion path reporting. | [`identifyUser` Implementation](#install-the-publisher-tag-with-identifyuser) |
## Publisher tag placement
Depending on how you want to use the Publisher Tag, it can be placed:
* In the `` tag of your web pages — **\[Recommended]** place the code at the bottom of the `` of each of the web pages on which you want it to run.
* In the `` tag of your web pages — place the code in the `` of each of the web pages on which you want it to run.
* In the **header template** of your website — **\[Recommended]** place the code at the bottom of your **header template** if you want it to run automatically on all of your webpages.
## Configure and copy the Publisher Tag
1. From the top navigation bar, select **Tools →** [**Ad Tools**](https://app.impact.com/secure/mediapartner/fr/ads/mp-ad-tools-flow.ihtml).
2. In the *Publisher Tag* section on the right, set your tracking configurations:
1. **Transform Links:** Detects direct links to the landing pages of brands you work with and converts them into impact.com tracking links. When users follow these links, you receive credit for any resulting actions.
* Select  **\[Toggle on]:** Transform Links works on every page where the Publisher Tag is installed.
* Select  **\[Toggle off]:** Transform Links is off, and a *Disabled* label appears next to it.
2. **Third Party Click Tracking**:  **\[Toggle on] Third Party Click Tracking** to enable tracking from external partner networks on pages where the tag runs. To view this data in the *Overview by Story* report, you must first [activate the free Trackonomics Essentials add-on](https://impact.com/trackonomics-essentials/).
3. Under the code snippet, select **Copy Tag** to copy the code to your clipboard.
{% hint style="warning" %}
**Important:** Publisher Tags copied before June 1, 2026, contain the code snippet below. On any page with this snippet, Transform Links still runs and overrides the toggle, even when the toggle is off.
```javascript
impactStat('transformLinks');
```
To disable Transform Links completely, disable the **Transform Links** toggle, then replace the old tag on those pages with the current tag.
{% endhint %}
## Install the Publisher Tag with a basic integration
The process for installing your Publisher Tag is different depending on whether your website is locally hosted, CMS-hosted, or whether you use a tag manager.
{% tabs %}
{% tab title="Locally hosted" %}
Use this method if you manage your website's code directly, rather than hosting it on a CMS or website platform.
1. Open the source code of the web page on which you want to install the Publisher Tag.
2. In your web page's code, find the `` opening tag at the top.
3. Paste the entire Publisher Tag code at the end of the section, making sure that everything is before the `` closing tag.
4. Repeat this for each webpage on which you want the Publisher Tag to run.
{% endtab %}
{% tab title="CMS-hosted" %}
If you use a Content Management System (CMS) or third-party website platform like WordPress, Squarespace, Wix, etc., refer to their help docs on how to add a JavaScript tag to your website. A quick web search should surface some results on how to install a JavaScript tag for your particular CMS. See examples below:
* WordPress[: Header and Footer Scripts plugin](https://wordpress.org/plugins/header-and-footer-scripts/)
* [Squarespace: Using Code Injection](https://support.squarespace.com/hc/en-us/articles/205815908)
* [Wix: About Tracking Tools and Analytics](https://support.wix.com/en/article/about-tracking-tools-analytics)
{% endtab %}
{% tab title="Tag managers" %}
If you use a Tag Management System (TMS) for your website, you'll need to add a custom HTML tag to your website. Refer to the tag manager's help docs on how to do this. For example:
* [Google Tag Manager — Custom tags](https://support.google.com/tagmanager/answer/6107167?hl=en\&ref_topic=3002579)
{% endtab %}
{% endtabs %}
### Test your basic integration
Once you've installed the Publisher Tag code snippet on your website, test the integration to make sure it's working correctly. Use your browser’s developer console to check that the link transformation and impression tracking features are working.
Check your website links
1. Open your browser's developer console by hovering over a link, then right-click and select **Inspect** (or **Inspect Element**).
* Check that the link in the `` quotation marks looks like an impact.com tracking link (e.g., `https://advertiser.sjv.io/` ).
2. Alternatively, hover over links on your web page. Most browsers will show the link's path in the browser’s status bar in the lower-left corner. The link should look like an impact.com tracking link (e.g., `https://advertiser.sjv.io/` or similar).
Check impression tracking
{% hint style="success" %}
**Note:** If you're using Safari, make sure to enable the *Status* bar from the top menu. Select **View → Show Status Bar** (or on your keyboard, hold  **\[Command] +** **/ \[Forward slash]**).
{% endhint %}
1. Open your browser's developer console by hovering over a link, then right-click and select **Inspect** (or **Inspect Element**).
2. In your browser’s developer console, select the **Network** tab. Refresh the page to capture fresh data.
* In the list under *Type*, check that an `xhr` or `beacon` has fired with a Status of `200`.
3. Alternatively, you can search your **Partner ID** in the *Network* tab. The format of the line item is `{trackingdomain}/i/partnerId/adId/campaignId` with an `xhr` or `beacon` Type and Status of `200`.
## Install the Publisher Tag with identifyUser
{% hint style="warning" %}
**Warning:** The advanced integration requires a skilled web developer who understands how this integration changes the script, along with the implications of the function. impact.com strongly advises consulting with a developer before attempting this integration.
{% endhint %}
Integrating using `identifyUser` is the recommended approach, because submitting authenticated user data through `identifyUser` can allow for improved attribution.
The `identifyUser` function also captures non-personally identifiable information (non-PII).
{% stepper %}
{% step %}
### **Modify the script**
1. Add the following line of code to the Publisher Tag body before the other function calls:
```programlisting
impactStat('identifyUser', {properties}, {options});
```
{% hint style="success" %}
**Note:** The current tag uses `impactStat`. Older tags use `impactPublisher` instead. Use the same function name that your tag uses.
{% endhint %}
2. Once you've added the new code, the full tag looks similar to this:
```programlisting
```
{% endstep %}
{% step %}
### **Install the script**
Once you’ve modified the script, you can follow the [basic integration instructions](#install-the-publisher-tag-with-a-basic-integration) to install the script.
{% endstep %}
{% step %}
### **Test your identifyUser integration**
Once you've installed the Publisher Tag code snippet on your website, test it to make sure it's working correctly. Testing the advanced integration requires knowledge of how to dynamically pass the `partnercustid` or `customeremail` variables.
Once this is configured, check the *Network* tab of your browser’s developer console for `partnercustid={passedid}` and `customeremail={passedemail}`.
{% endstep %}
{% endstepper %}
{% hint style="success" %}
**Note:** For more information on the Publisher Tag, read the [Publisher Tag FAQ](/brand/what-would-you-like-to-learn-about/platform-features/tracking/tracking-explained/publisher-tag-faq.md). If you’re unsure how to accomplish any of the mentioned steps in this article, [contact support](https://app.impact.com/support/portal.ihtml?createTicket=true).
{% endhint %}
---
# 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/partner/what-would-you-like-to-learn-about/platform-features/tracking/tracking-links/create-and-manage-links/publisher-tag-implementation-for-partners.md?ask=&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.