# \[Beta] Create a Partner Integration
{% hint style="info" %}
**Note:** This functionality is in beta. Contact your CSM or our [support team](https://app.impact.com/support/portal.ihtml?createTicket=true&) if you'd like to test this feature.
{% endhint %}
The Partner Integrations Hub allows you to connect with technical partners who require a JavaScript integration with your website. These technical partner integrations make use of the [impact.com universal tracking tag (UTT)](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/tracking/javascript-tag-tracking/tracking-with-universal-tracking-tag-utt), a JavaScript tag that is placed on your website, to execute new code from the technical partner.
{% hint style="info" %}
**Note:** You must [have UTT enabled](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/tracking/javascript-tag-tracking/tracking-with-universal-tracking-tag-utt) as a pre-requisite for making use of the Partner Integrations Hub, and have approval from your website's IT or Site Reliability teams before deploying a JavaScript tag.
{% endhint %}
#### Step 1: Add the integration details
1. From the top navigation bar, select  **\[User profile] → Settings**.
2. In the *Account* column, scroll to the *Technical* heading and select **Partner Integrations Hub**.
3. From the top-right of the page, select **Add Integration**.
4. Select the integration's *Integration Tag* from the  **\[Drop-down menu]**.
* The identifiers required to set up an integration will differ from partner to partner. When you select a partner from the drop-down menu, you'll see which identifier the partner requires.
* If you have any questions, please reach out directly to the partner with which you are integrating.
5. Enter any unique identifier required by the selected partner. For instance, in the screenshot below, the integration requires the *domain* identifier.
6. Select  **\[Checked box]** **Email partner when integration is added** to send an email notification to the relevant technical partner.
7. Next, select **Add Integration** to save the integration details and proceed to the review stage.
#### Step 2: Review and publish the integration
After adding the integration, the *Review and Publish* page is displayed. This page includes a validation checklist to ensure you've addressed common technical and compliance requirements before the integration goes live. Completing this checklist helps verify several common implementation gaps and ensures your integration is published accurately and can be tracked successfully.
1. To enable the *Publish Tag* button, you must review and select the  **\[Unchecked box]** for each item listed below:
| Field | Description |
| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Code Placement confirmed | Verify that the impact.com Universal Tag is correctly placed on your website.
If applicable, confirm that the partner's tag domain is allowed in your website's Content Security Policy (CSP) so the script isn't blocked.
|
| Correct Integration ID | Validate the unique IDs (e.g., "id") entered are accurate and match those provided by your integration partner. |
| Privacy & Compliance Review | Confirm adherence to data privacy regulations (e.g. GDPR, CCPA) and other legal requirement, ensuring no personal data is inadvertently collected or shared. |
| Internal Stakeholder Sign-Off | Since new code will be placed on your website, secure approval from required internal stakeholders (e.g. Site reliability Engineer, Product manager, Legal) before publishing. |
2. Once the required confirmations are complete:
* Select **Publish Tag** to enable the integration immediately.
* Alternatively, if you are not ready to publish yet, select **Publish Later** to save the integration in a disabled state.
{% hint style="info" %}
**Note:** Depending on your organization’s content security policy, you may need to add `https://*.partner.com` into your Content Security Policy directive. Replace`partner` with the top-level domain of the partner with which you are integrating.
{% endhint %}
#### Publish an added integration
If you've saved an integration in a disabled state, you can publish it by following these steps:
1. From the [*Partner Integrations Hub*](https://app.impact.com/secure/advertiser/fr/partner-integrations-hub.ihtml) page, find the *Disabled* integration you want to publish.
2. Hover your cursor over the integration and select  **\[More]** → **Publish**.
3. After selecting *Publish*, the *Review and Publish* page is displayed. Complete the verification steps outlined in Step 2: Review and publish the integration.
4. The published integration is now enabled and will be displayed with an *Enabled* status on the list in the *Partner Integrations Hub*.
#### Update an integration
You can edit an integration as follows:
1. From the [*Partner Integrations Hub*](https://app.impact.com/secure/advertiser/fr/partner-integrations-hub.ihtml) page, find the integration you want to edit.
2. Hover your cursor over the integration and select  **\[More]** → **Edit**.
3. Enter a new identifier, usually supplied by the technical partner, into the textbox.
4. Select **Save** to save your changes.
