We constantly publish updates to our documentation, which may not yet be available in your language. For the most current information, use the English version.

for Marketers

Set up Clinch

Clinch is an ad network integrated with Adjust. Our integration lets Clinch receive attribution and in-app event data through automated callbacks.

In this article, learn how to set up measurement with Clinch for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with Clinch.

Before you begin

Requirements

Admin, Editor, or Custom Editor permissions in Adjust.
Adjust SDK v4.0.0 and later to map SDK parameters to Clinch parameters. Follow the guides linked below to use this feature.

Credentials

CID and API KEY

For help finding your credentials, contact your Clinch representative.

Select Clinch and your app in Campaign Lab

Under Campaign Lab, select Partners.
Select New partner > Clinch. Select Next to move to the next screen.
In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with Clinch.
Select Next.

Enable data sharing

Enable data sharing to activate the integration with Clinch. To enable data sharing:

Enter your CID and API KEY.

Once you enable data sharing with Clinch, Adjust automatically sends Clinch the following data, by default:

install
event

Set your data sharing options

If you’re working with a multi-platform app with data sharing enabled for multiple platforms, you can:

Separate data sharing options at the platform-level by selecting Use platform-specific settings.
Set the same data sharing settings for multiple platforms by selecting Use global settings.

Now, under What will be shared by default?, review the activities that Adjust shares with Clinch by default.

install
event

Send additional data

Choose the amount and type of data that you want to share with Clinch through callbacks. Clinch may use this information to optimize performance.

Under What sources of data do you want to share?, choose the attribution source of the data you are sharing with Clinch:

Data from all attribution sources
Only data attributed to Clinch

In-app revenue (from in-app purchases)

Sharing in-app revenue lets Clinch receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.

Map events

Map events that you want to share to the values that Clinch can receive. Data for unmapped events is not shared with Clinch.

Map individual events

If you have a multi-platform app, you can choose to share different events per platform with Clinch. This lets you:

Set individual events to manage campaign strategies for each platform.
Customize data sharing per platform.

Under Map events, follow these steps to choose the in-app events you want to directly send to Clinch.

Select Map event.
In the Adjust event list, choose the Adjust event that you want to share with Clinch.
Under Partner event, you need to select the Clinch event that corresponds to the Adjust event.
1. For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
  - Select Use platform-specific mapping to map separate events at the platform-level or to not map events for certain platforms.
  - Select Use global mapping to map the same events for all platforms.
2. In the Partner event list, choose or enter a custom event name, that you want to map the Adjust event to.
Select Apply.

Now Clinch will receive in-app event data for each of your linked events.

Map all events

If Clinch supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.

Now Clinch will receive in-app event data for all your linked events.

Map parameters

You usually need to map parameters to share custom data with Clinch.

Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to Clinch. This lets Clinch receive custom event details for each of your linked events.

Before adding new partner parameters to the Adjust SDK, make sure no pre-existing partner parameters already fit your requirements.

To share partner parameters to Clinch, follow these steps.

Set up partner parameters within the Adjust SDK.
- Check Before you begin for all SDK development platform links.
Under Set your data sharing options, select Parameters.
Under Map parameters, you can specify how you want to send partner parameters defined in the SDK to the network:
1. Select Map parameter.
2. In the SDK parameter field, enter the name of the SDK parameter you want to share with the network.
3. In the Partner parameter field, enter the network parameter that corresponds to the SDK parameter.

Note:

If you set up partner parameters within the Adjust SDK without setting up parameter sharing in the dashboard, Adjust forwards the parameters as named in the Adjust SDK.

Configure your link and settings

You have the option to set your:

Create your link and share it with Clinch

In the Setup review screen, you can review your choices. You can also go back and make changes to:

Your selected app
Data sharing options
Link structure parameters
User destinations
Attribution settings

Select Create link to create your click URL, impression URL, QR code and link token. Creating a link also enables data sharing and the integration with Clinch.

Once you’ve created your link, share it with Clinch for placement in campaigns.

List of all parameters forwarded to Clinch

Clinch requires Adjust to send the following parameters (data points) with your callbacks:

Placeholder	Information
`{city}`	Device city
`{country_subdivision}`	Device subdivision of country, e.g., state
`{country}`	Device two-character country code
`{currency}`	Original ISO 4217 currency code sent from Adjust SDK
`{gps_adid_md5}`	Lowercase hex MD5 hash of Google Play Store advertising ID
`{idfa_md5_hex}`	IDFA hex MD5 hash
`{ip_address}`	Device IP address
`{language}`	Device two-character language code
`{partner_parameters}`	Custom partner parameters collected by the Adjust SDK or S2S request and transmitted to third party providers via postbacks
`{postal_code}`	Device postal code of IP address
`{revenue_usd}`	Revenue, in US dollars
`{user_agent}`	Incoming raw user agent
`{app_id}`	Store App ID or Google Play Store
`{app_name}`	Name of the app
`{store}`	Target store of click