What Is Clinch?

Clinch is a dynamic creative optimization platform that empowers advertisers to create personalized, data-driven ad experiences at scale. By leveraging artificial intelligence and machine learning algorithms, Clinch enables advertisers to dynamically generate and deliver tailored ad content to individual users across various digital channels. Its intuitive platform allows advertisers to easily create, manage, and optimize campaigns, while providing robust analytics and insights to drive better performance and ROI. Clinch's technology helps advertisers engage audiences more effectively by delivering relevant messages based on real-time data, enhancing ad effectiveness and campaign success.

Getting Started

1. From Your Clinch Account

You will need the following ID from the Clinch platform. The ID must be the encoded ID:

• Client ID
  1. Navigate to the Flight Control platform.
  2. Locate the Client ID within the account settings section, or alternatively, consult your Clinch Account Manager for assistance.

2. From MetaRouter

To gather the clickClickID value and the clinch-sid value, you must add a Clinch sync.

1. From the Pipelines page, find the pipeline associated with the web property you’d like to add a sync to. Hover over the three dot dropdown and select “Build AJS File.”
2. In the Identity Syncs section, select the Clinch sync.
3. Fill out the following fields:
   1. Consent Type - We recommend that you consult with your legal team when determining your consent requirements.
   2. Client ID(s) - Please input your Client ID in the following format [”XXXXXX”].
   3. Cookie Lifetime - Recommended 90 days.
4. Scroll down and click the Save and Build File button.
5. Deploy your AJS file to propagate changes to your web property.

Technical Details

Sync Types

Sync Ids

ids: clinchClickId_CLIENT_ENC_ID,sid

syncType: urlParams, fetchSync

1. URL Sync

• clinchClickId_{client_enc_id}
  • The sync captures the value of all Clinch Click IDs URL parameter(s) and stores each value as a first-party cookie named _meta_clinch_clinchClickId_{client_enc_id} for a default duration of 90 days.
  • The client_enc_id value from the parameter name is dynamic and will be provided via our UI within the Client ID(s) field. There can be one or more Client IDs.
  • The value will be updated whenever a new clinchClickId_{client_enc_id} URL parameter is detected.
  • Consequently, all server-side events will be enhanced with the context.providers.clinch object as detailed below.

2. Fetch Sync

• Endpoint: https://trkweb.clinch.co/clinch-sid?cid={client_encoded_id}
• HTTP method : GET
• Response format: JSON
• Response example : {“clinch-sid“:”5c299f0f-c409-4abc-bd10-4e17b5d12eb3”}

Notes

• The request might perform an HTTP 302 redirect to verify cookie persistency.
• In case there is no data, the following response will be returned: {“clinch-sid“:null}.
• We tested the returned sid value for multiple client IDs and we received the same sid value. As a result, we decided to use the first client ID value from the provided Array of Client IDs.

Server-Side Event Payload: providers object enrichments

Upon completion of all vendor's sync, the server-side events will incorporate all resolved identifiers as described above. The following object will be appended to the context.providers property within the event's JSON payload.

{
   "clinch": {
     "clinchClickId_{client_enc_id}": "URL parameter value from clinchClickId_{client_enc_id}",
     "sid": "Value from fetch sync"
   }
}

UI build settings

• (Required) Cookie Lifetime (in days)
  • Defines how long the synced identifier will remain in the first-party ID graph. Once this lifetime is reached, or whenever the sync no longer detects the identifier (whichever comes first), another sync will be performed to pull a new value.
  • The default value recommended by the Vendor is set to 37.
• (Required) Client ID(s)
  • Array of String representing Client IDs received from the Vendor.
  • Example: ["your-client-id-1", "your-client-id-2"]