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.

Product Type: Advertising

Integration Type: Starter Kit & ID Sync

Capabilities

• Captures click identifiers from URL parameters for attribution.
• Retrieves the Clinch cookie ID via a fetch request to support identity resolution across sessions and domains.
• Stores each identifier in first-party storage using configured client IDs.
• Adds all resolved identifiers to server-side events for personalization, audience matching, and conversion tracking.

Considerations

• Click ID parameter names are dynamic and must match the Client ID(s) configured in the UI.
• The Clinch cookie ID (sid) is shared across all Client IDs and returned using the first configured client ID.
• The fetch request may result in an HTTP 302 redirect as part of Clinch's cookie validation process.

Limitations

• If the Clinch cookie ID (sid) is not available, the response will return null, and the sync should not retry frequently. MetaRouter stores the empty result to prevent excessive requests.

Sync Details

• IDs:
  • clinchClickId_{client_enc_id} – A click identifier passed in the URL upon ad click-through, used for attribution. {client_enc_id} is the advertiser-specific Client ID.
  • sid – The Clinch cookie ID, a persistent identifier used by Clinch to recognize users across domains and sessions.
• Description:
  • URL Sync: Captures each clinchClickId_{client_enc_id} value from the URL based on the configured Client ID(s). The value is stored and refreshed as new parameters appear.
  • Fetch Sync: Sends a GET request to Clinch's clinch-sid endpoint using the first Client ID in the list to retrieve the Clinch cookie ID (sid). The value is stored for enrichment if present.
  • Both identifiers are included in server-side event payloads for downstream use by Clinch’s remarketing and dynamic creative optimization (DCO) systems.
• Response Example: {“clinch-sid“:”5c299f0f-c409-4abc-bd10-4e17b5d12eb3”}
• Server-side Event Payload: 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"
     }
  }
  

• Cookie Name:
  • Cookie: _meta_clinch_clinchClickId_{client_enc_id}, _meta_clinch_sid
  • IndexedDB: [your storage prefix]_clinch_clinchClickId_{client_enc_id}, [your storage prefix]_clinch_sid
  • For a general guide on ID Sync validation, see here.

Sync Setup Guide

1. Gather Credentials

• Client ID(s)
  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. Add a Clinch Sync in MetaRouter

To gather the clinchClickId_{client_enc_id} and sid values, 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. Cookie Lifetime (in days) – Duration to store all captured identifiers. Example: 37
   2. Client ID(s) – An array of client-encoded IDs provided by Clinch. You must enter this as a valid JSON array of strings.
      1. Example: ["your-client-id-1", "your-client-id-2"]
4. Scroll down and click the Save and Build File button.
5. Deploy your AJS file to propagate changes to your web property.