Search specific term/phrase surrounded by double quotes. e.g. “deep linking”
Exclude records that contain a specific term prefixed with a minus. e.g. Android -Firebase

Clinch

Enable Clinch with Branch to power your mobile attribution.

1328

Overview

Clinch is an AI-powered Creative Personalization platform that delivers consumer-tailored ad experiences across all channels, to drive online and in-store performance and sales.

Partner Capabilities

CapabilityDetails
Company TypeDCO
Deep LinkingNot Supported
AttributionContact support at Clinch for more information.
Ad Campaign TypesContact support at Clinch for more information.
Ad FormatsContact support at Clinch for more information.
Click TypesContact support at Clinch for more information.
Supported PlatformsContact support at Clinch for more information.
Link WrappingContact support at Clinch for more information.
Cost Ingestion SupportContact support at Clinch for more information.
Cost Ingestion TypesContact support at Clinch for more information.
Pricing ModelsContact support at Clinch for more information.

Prerequisites

In order to enable Clinch, you need to have completed the following:

  1. Created a Branch Dashboard.
  2. Enabled Universal Ads for your Branch account.
  3. Implemented the Branch SDK into your mobile app (iOS | Android)
  4. Running campaigns through Clinch.

Enable Clinch

1. Enable Clinch in Branch

In the Branch Dashboard under Ads > Partner Management, find/search for Clinch. If you're already logged into the Branch Dashboard, you can also click here to go there directly.

You'll need to input your Clinch Client ID (CID) and your Clinch Data Source ID (DSID). Please reach out to your Clinch Account Manager for details.

Click the Save & Enable button.

2. Configure Postbacks

Enabling Clinch will automatically enable the following postbacks:

  • INSTALL
  • PURCHASE
  • ADD_TO_CART
  • ADD_TO_WISHLIST
  • VIEW_CART
  • VIEW_ITEM
  • VIEW_ITEMS
  • INITIATE_PURCHASE

You can configure these postbacks or add more under the Postback Config tab.

Send All Events

Optionally, you can check the checkbox for a given postback for sending all events. When checked, all events will be sent regardless of attribution. Otherwise, the postback will only fire for events attributed to Clinch.

Adding Postbacks

Click the Add New Postback button at the bottom of the screen. A modal will appear that will allow you to select an event that you are tracking with the Branch SDKs (including Custom Events).

For more in-depth postback configurations, view our guides:

3. Configure Attribution Windows

After configuring your events, navigate to the Attribution Windows tab to set windows by attribution type.

Recommended Attribution Windows

Attribution TypeWindow
click to session start90 days
click to install30 days
click to conversion event90 days
impression to session start1 day
impression to install1 day
impression to conversion event.1 day

4. Create Branch Ad Link

Next, you'll need to create a Branch Ad Link for your Clinch campaigns in order for Branch to properly attribute conversions.

The Branch Ad Link you create will be placed in your Clinch campaign.

5. Verify Data in Branch

After launching your Clinch campaigns, and conversions begin to happen, you'll want to to verify data is being sent from Branch to Clinch. You can look at the Branch Dashboard's Liveview Webhook Records and apply the following filter:

FilterOperatorValue
ad partner (3p)equalsa_clinch

Once applied, data should flow through the Liveview, and you can see the data being sent to Clinch from Branch.