Clinch
Enable Clinch with Branch to power your mobile attribution.
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
Capability | Details |
---|---|
Company Type | DCO |
Deep Linking | Not Supported |
Attribution | Contact support at Clinch for more information. |
Ad Campaign Types | Contact support at Clinch for more information. |
Ad Formats | Contact support at Clinch for more information. |
Click Types | Contact support at Clinch for more information. |
Supported Platforms | Contact support at Clinch for more information. |
Link Wrapping | Contact support at Clinch for more information. |
Cost Ingestion Support | Contact support at Clinch for more information. |
Cost Ingestion Types | Contact support at Clinch for more information. |
Pricing Models | Contact support at Clinch for more information. |
Prerequisites
In order to enable Clinch, you need to have completed the following:
- Created a Branch Dashboard.
- Have Branch's Performance product enabled for your Branch Account.
- Implemented the Branch SDK into your mobile app (iOS | Android)
- 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 Type | Window |
---|---|
click to session start | 90 days |
click to install | 30 days |
click to conversion event | 90 days |
impression to session start | 1 day |
impression to install | 1 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:
Filter | Operator | Value |
---|---|---|
ad partner (3p) | equals | a_clinch |
Once applied, data should flow through the Liveview, and you can see the data being sent to Clinch from Branch.
Updated 3 months ago