> For the complete documentation index, see [llms.txt](https://help.branch.io/llms.txt).

# Enable Clinch (New)

> Integrate Clinch with Branch for ad personalization and dynamic optimization, enhancing your campaign performance across channels.

## Overview

[Clinch](https://clinch.co) is an AI-powered creative personalization and dynamic creative optimization (DCO) platform that delivers consumer-tailored ad experiences across channels to drive online and in-store performance. Connect Clinch to Branch to attribute clicks and installs and forward conversion events via Postbacks.

For more information about integrating ad partners in general, visit our [Ad Partner Integration Guide](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md).

> **Note: this guide is for new Branch**
>
> Please note that this guide is about integrating Clinch in the [new Branch experience](https://help.branch.io/marketer-hub/new-branch-overview.md). For information on Clinch in legacy Branch, visit our [legacy guide](https://help.branch.io/marketer-hub/clinch.md).

### Partner capabilities

| Capability | Details |
| --- | --- |
| Company type | DCO, Ad server |
| Deep linking | Not supported |
| Attribution | View-Through Attribution, Click-Through Attribution |
| Ad campaign types | Dynamic personalization, Acquisition, Retargeting, Sequential storytelling |
| Ad formats | CTV, OTT, Programmable video, Banner, Interstitial, Native, Social |
| Click types | Server-side click redirection, Client-side event tracking |
| Supported platforms | iOS, Android |
| Link wrapping | Supported |
| Cost ingestion support | Not supported |
| Pricing models | Contact Clinch for details |

## Before you begin

To set up the Clinch integration, you need:

- Ad partner integrations enabled for your Branch account. Availability varies by Branch plan. See [Branch pricing](https://www.branch.io/pricing/) or contact your Branch representative.
- A Branch account with access to **Configuration > Ad Partners** and admin permissions to enable and configure integrations.
- The Branch SDK implemented in your app ([iOS](https://help.branch.io/developer-hub/ios-sdk-overview.md) | [Android](https://help.branch.io/developer-hub/android-sdk-overview.md)) with [event tracking](https://help.branch.io/developer-hub/track-branch-events.md) configured.
- A Clinch account with admin access and campaigns running through Clinch.
- [PAM](https://help.branch.io/marketer-hub/predictive-aggregate-measurement.md) enabled (recommended).

> **Note: PAM uses two separate toggles**
>
> The **PAM for Publishers** toggle for this partner, found under **Partner settings** > **Manage account**, is separate from the account-level **PAM switch**. **PAM for Publishers** must be enabled to reconcile conversion events with your partner. To attribute events with PAM, you also need PAM enabled on the [Attribution page](https://help.branch.io/account-hub/attribution-page-new.md) under **Configuration** > **Attribution**. Learn more in our [PAM Overview](https://help.branch.io/marketer-hub/predictive-aggregate-measurement.md#pam-for-publishers).

## Enable Clinch

To begin, navigate to **Configuration > Ad Partners > Clinch**.

Branch enables Clinch's basic setup automatically. On the **Status** tab, the **Ad Linking** and **Attribution** cards show **Enabled**. The **Postbacks** card shows **Needs Setup** until you add your Clinch credentials.

To complete setup, select **Partner settings** to open the **Manage account** dialog. Under **Postback Credentials**, enter your **Clinch Client ID** and **Clinch Data Source ID**, then select **Save**. These credentials are automatically added to your postbacks. Contact your Clinch account manager if you need help locating these values.

(Recommended) To configure the optional **PAM for Publishers** privacy setting, select **Partner settings** to open the **Manage account** dialog and enable the toggle. When enabled, [PAM for Publishers](https://help.branch.io/marketer-hub/predictive-aggregate-measurement.md#pam-for-publishers) removes advertiser-specific user identifiers from postbacks for users who haven't opted in via Apple's App Tracking Transparency (ATT) framework, prioritizing identifiers provided directly by Clinch.

## Configure attribution

By default, Clinch uses your global app attribution settings. To set attribution windows specific to Clinch, enable the **Override global app settings** toggle on the **Attribution windows** tab.

For more information, follow [Configure attribution](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md#configure-attribution) in the general [Ad Partner Integration Guide](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md).

## Configure postbacks

Enabling Clinch automatically activates postbacks for `INSTALL`, `PURCHASE`, `ADD_TO_CART`, `ADD_TO_WISHLIST`, `VIEW_CART`, `VIEW_ITEM`, `VIEW_ITEMS`, and `INITIATE_PURCHASE`. The default postback URL template is:

```
https://trk.clinch.co/trk?partner=1003&cid=${ (ad_network.credentials.cid)! }&dsid=${ (ad_network.credentials.dsid)! }&type=${ (name)! }&event_time=${ (timestamp/1000)?long }&is_attributed=<#if (last_attributed_touch_data.$3p)! == (ad_network.machine_name)!>1<#else>0</#if>&event_data=<@urlencode><@jsonmap data=event_data></@jsonmap></@urlencode>&apl_did=${ (user_data.idfa)! }&and_did=${ (user_data.aaid)! }&did=<#if (user_data.os)! == "IOS" && (user_data.idfa)! != "">${(user_data.idfa)!}<#elseif (user_data.os)! == "IOS">${(user_data.idfv)!}<#elseif (user_data.os)! == "ANDROID">${(user_data.aaid)!}</#if>&user_ip=${ (user_data.ip)! }&os=${ (user_data.os)! }&os_version=${ (user_data.os_version)! }&ct=${ (user_data.geo_country_code)! }&language=${ (user_data.language)! }&user_agent=${ (user_data.user_agent)! }&bundle_id=<@loop data=app.app_bundles val="bundle"><#if user_data.os == bundle.os><#if bundle.os=="ANDROID">${(bundle.android.package_name)!}<#elseif bundle.os == "IOS">${(bundle.ios.bundle_id)!}</#if><@break/></#if></@loop>&app_name=${ (app.name)! }&app_version=${ (user_data.app_version)! }&apl_idfv=${ (user_data.idfv)! }
```

By default, a postback fires only for events attributed to Clinch. To send a given event regardless of attribution, enable its **All events** toggle on the **Postback config** tab.

To add postbacks for additional events or to customize postback behavior, follow [Configure postbacks](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md#configure-postbacks) in the general [Ad Partner Integration Guide](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md).

## Create a Branch Ad Link

Create a Branch Ad Link to use in your Clinch campaigns. Branch uses the link to attribute conversions from your Clinch campaigns.

Follow [Create Ad Links](https://help.branch.io/marketer-hub/ad-links-new.md).

## Verify your data

After your integration is connected and events are flowing, you can verify data is reaching Branch and Clinch:

- **In Branch** [**Liveview**](https://app.branch.io/testing-and-monitoring/events): confirm that events from your app appear in real time. This is the fastest way to confirm SDK events are firing.
- **In Branch** [**Analysis dashboards**](https://help.branch.io/marketer-hub/analysis-dashboards-overview-new.md): review attributed installs and events where `Ad Partner Name = Clinch`.
- **In Clinch**: confirm that forwarded events are appearing in your Clinch reporting.

## Data mappings

### Campaign data

Branch populates the following fields from Clinch campaign data.

| Branch field | Partner data |
| --- | --- |
| `~advertising_partner_name` | `"Clinch"` (static) |
| `~feature` | `"paid advertising"` (static) |