Clinch

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 data, enhancing ad effectiveness and campaign success.


Product Type: Advertising
Integration Type: Starter Kit & ID Sync
Event Source Type: Web
Event Scope: Full-Funnel Events


Capabilities

  • Streams server-side event data into Clinch for ad decisioning and measurement.
  • Enables Clinch tag removal, with no effect on website load latency.
  • Unlocks all customer data events and attributes for custom event mapping and transformation.
  • Supports full-funnel events including page, product, cart, and order lifecycle actions.

Considerations

  • The client ID and data source ID must be the encoded IDs provided by Clinch.
  • The partner ID defaults to a static value for the MetaRouter-to-Clinch integration and should not be changed unless advised by your Clinch representative.
  • The mobile resettable advertising ID (did, such as ADID or IDFA) can be added as a Global or Event Specific mapping to improve user match rates when available.
  • In our testing, requests above ~20,000 characters in the URL began to fail. While this isn't a formally documented limit, it may be a practical constraint to consider when using this integration.
  • All values must be URL-encoded and arrays pipe-delimited.
  • One request per event; batching not supported.
  • Complex lists (e.g., products) must be pipe-delimited.

Identity Sync

Sync Details

  • Captures the Clinch click ID (clinchClickId) and cookie ID (clinch-sid) used for attribution and user matching.
  • Required by Clinch to associate events with users and prior ad activity.
  • Without this sync, events may not be accurately reflected in reporting.

Starter Kit Setup Guide

1. Deploy the Clinch Sync

  • To collect the sync values (e.g., clinchClickId, clinch-sid), you must implement a Clinch ID sync. Refer to the following documentation to complete the setup: Clinch - ID Sync Guide.

2. Gather Credentials

  • Obtain the following encoded IDs from the Clinch Flight Control platform, or from your Clinch Account Manager:
    • Client ID: Located within the account settings section.
    • Data Source ID: Retrieved during the creation of a new data source.

3. Add a Clinch Integration

  • From the integration library, add a Clinch integration. Then, fill out the Connection Parameters:
Connection ParameterDescription
CLIENT_IDYour Client ID.
DATA_SOURCE_IDYour Data Source ID.
PARTNER_IDThe default value is static for the MetaRouter to Clinch integration. Do not change this unless advised by your Clinch representative.

4. Configure Event Mapping

  • MetaRouter provides all of the event mappings that Clinch integrations typically require. You may add custom events, parameters, or mappings in accordance with Clinch's API documentation.

5. Deploy to Pipeline

  • In the Pipelines tab, add your Clinch integration.
  • Select the correct integration revision.
  • Click Add Integration to finalize deployment.

Event Mappings

Global

Global mappings will be applied to all events. If your parameter names do not match the Expected Inputs provided, you will need to overwrite the Inputs provided with your own.

Output KeyDescriptionExpected Input
cid RequiredString: Client ID (encoded).$$CLIENT_ID$$
dsid RequiredString: Data Source ID (encoded).$$DATA_SOURCE_ID$$
partner RequiredNumeric: Vendor partner ID on Clinch.$$PARTNER_ID$$
clinch-sid RequiredString: Clinch cookie ID.context.providers.clinch.sid
timestamp RequiredInteger: Event timestamp in epoch milliseconds (UTC).Expression – converts the event timestamp to epoch milliseconds
user_ip RequiredString: IPv4 address of the user.context.ip
user_agent RequiredString: User agent string.context.userAgent
referrer RequiredString: The page URL where the event originated.context.page.referrer
hem Highly RecommendedString: SHA-256 hashed email address.Expression – hashes trimmed, lowercased traits.email when present

Event Specific

Identify

Output KeyDescriptionExpected Input
type RequiredString: Event type.Enrichment – 'Other'

Page

Output KeyDescriptionExpected Input
type RequiredString: Event type.Enrichment – 'PageView'

Products Searched

Output KeyDescriptionExpected Input
type RequiredString: Event type.Enrichment – 'Search'
termString: Search term.properties.query

Product List Viewed

Output KeyDescriptionExpected Input
type RequiredString: Event type.Enrichment – 'Category'
product RequiredString: One of Ecommerce, Flight, Hotel, Package, Car.Enrichment – 'Ecommerce'
categoryString: Product category.properties.category
idsComma-separated String: Viewed product IDs.Expression – joins product_id values from properties.products
amountNumber: Total price amount.Expression – sums price × quantity across properties.products
currencyString: Currency code (e.g., USD).properties.currency (uppercased, default USD)

Product Viewed

Output KeyDescriptionExpected Input
type RequiredString: Event type.Enrichment – 'Details'
product RequiredString: One of Ecommerce, Flight, Hotel, Package, Car.Enrichment – 'Ecommerce'
categoryString: Product category.properties.category
idsComma-separated String: Viewed product IDs.properties.product_id
amountNumber: Total price amount.Expression – returns properties.value or price × quantity
currencyString: Currency code (e.g., USD).properties.currency (uppercased, default USD)

Product Added

Output KeyDescriptionExpected Input
type RequiredString: Event type.Enrichment – 'AddtoCart'
product RequiredString: One of Ecommerce, Flight, Hotel, Package, Car.Enrichment – 'Ecommerce'
categoryString: Product category.properties.category
idsComma-separated String: Viewed product IDs.properties.product_id
amountNumber: Total price amount.Expression – returns properties.value or price × quantity
currency RequiredString: Currency code (e.g., USD).properties.currency (uppercased, default USD)

Product Added To Wishlist

Output KeyDescriptionExpected Input
type RequiredString: Event type.Enrichment – 'AddToWishList'
product RequiredString: One of Ecommerce, Flight, Hotel, Package, Car.Enrichment – 'Ecommerce'
categoryString: Product category.properties.category
idsComma-separated String: Viewed product IDs.properties.product_id
amountNumber: Total price amount.Expression – returns properties.value or price × quantity
currencyString: Currency code (e.g., USD).properties.currency (uppercased, default USD)

Product Removed

Output KeyDescriptionExpected Input
type RequiredString: Event type.Enrichment – 'RemFromCart'
product RequiredString: One of Ecommerce, Flight, Hotel, Package, Car.Enrichment – 'Ecommerce'
categoryString: Product category.properties.category
idsComma-separated String: Viewed product IDs.properties.product_id
amountNumber: Total price amount.Expression – returns properties.value or price × quantity
currencyString: Currency code (e.g., USD).properties.currency (uppercased, default USD)

Cart Viewed

Output KeyDescriptionExpected Input
type RequiredString: Event type.Enrichment – 'CartPage'
product RequiredString: One of Ecommerce, Flight, Hotel, Package, Car.Enrichment – 'Ecommerce'
idsComma-separated String: Viewed product IDs.Expression – joins product_id values from properties.products
amountNumber: Total price amount.Expression – sums price × quantity across properties.products
currencyString: Currency code (e.g., USD).properties.currency (uppercased, default USD)

Checkout Started

Output KeyDescriptionExpected Input
type RequiredString: Event type.Enrichment – 'Checkout'
product RequiredString: One of Ecommerce, Flight, Hotel, Package, Car.Enrichment – 'Ecommerce'
idsComma-separated String: Viewed product IDs.Expression – joins product_id values from properties.products
amountNumber: Total price amount.Expression – sums price × quantity across properties.products
currencyString: Currency code (e.g., USD).properties.currency (uppercased, default USD)

Order Completed

Output KeyDescriptionExpected Input
type RequiredString: Event type.Enrichment – 'Conv'
product RequiredString: One of Ecommerce, Flight, Hotel, Package, Car.Enrichment – 'Ecommerce'
idsComma-separated String: Viewed product IDs.Expression – joins product_id values from properties.products
orderId RequiredString: Purchase order ID or confirmation ID.properties.order_id
amount RequiredNumber: Total price amount.Expression – sums price × quantity across properties.products
currency RequiredString: Currency code (e.g., USD).properties.currency (uppercased, default USD)

Required & Recommended Identifiers

These identifiers must be mapped to Clinch in order for successful user matching to occur. Without the required IDs, any events sent to Clinch will be rejected. For your convenience, required and recommended IDs are mapped as Global parameters to ensure they are added to every event.

AttributeExampleSync Injector Required?
clinchClickId_{client_enc_id} Required?clinchClickId_abc12D=9K2bXp4s…Yes
clinch-sid Highly Recommended5c299f0f-c409-4abc-bd10-4e17...Yes
hem Highly Recommended7c6a180b36896a0a8c02787eeafb0e4c52a24f8d44c98dbb5a3eac573e7b5eecNo

Integration Validation

  • Coordinate with your Clinch representative to confirm that events are being received and processed correctly on their backend.

Additional Clinch Documentation