Clinch

This destination is currently under final review and will be available soon.

Clinch's platform is used for omnichanel content orchestration. Using this destination you can activate server-to-server tracking to send events to Clinch.

Key features

The Clinch destination provides the following key features:

• Events structure: our Events reference model covers Clinch's event types, meaning that your data is properly bridged to the expected fields in an optimized way.

• Prebuilt mappings: data mapping for event-based destinations happens automatically, which simplifies user inputs.

• Automatic hashing: information is automatically hashed matching partner specifications.

• Smart mapping: data mapping can be readjusted using your datalayer defined fields.

• Event mapping: change standard mapping between Clinch events and yours.

• Support for multi-item data: information included in the item array is dispatched to Clinch.

Destination setup

Configuration

Settings	Description
Client Id	Required Your encoded client identifier (cid). You can find this value in Clinch interface by following Accounts → Data Sources after creating a Website Pixel. Here you can find the Advertiser ID (cid).
Data Source Id	Required Your encoded data source identifier (dsid). You can find this value in Clinch interface by following Accounts → Data Sources after creating a Website Pixel. Here you can find the Pixel ID (dsid).
Event Mapping	Change the standard mapping between Clinch event types and your events or add new mappings. Accepted value for Clinch event type: PageView, HomePage, Landing, Search, Category, Details, DetailsExit, AddToCart, RemFromCart, CartPage, AddToWishList, Checkout, conv, Registration and OfflineConv.

Quick reference

Commanders Act Events	Clinch Event Types
page_view	HomePage [1] Landing [2] PageView
search	Search
view_item_list	Category
view_item	Details
add_to_cart	AddToCart
remove_from_cart	RemFromCart
view_cart	CartPage
add_to_wishlist	AddToWishList
begin_checkout	Checkout
purchase	OfflineConv [3] conv
generate_lead	Registration
[Any Other Event]	Other
[Any Event]	[Any Event] [4]

1. Set if property page_type is home . 2. Set if property page_type is landing . 3. Set if property type is offline . 4. See Event Mapping in Configuration.

Field mappings

Properties can be remapped using our Smart Mapping feature.

Smart Mapping Field

Commanders Act Default Properties

Clinch Properties

-	Client Id	cid [*]
-	Data Source Id	dsid [*]
Device IP	context.device.ip	user_ip [*]
Device User Agent	context.device.user_agent	user_agent [*]
Page URL	context.page.url	referrer [*]
Event Timestamp	context.event_timestamp	timestamp
Vendor Partner Id	partners.clinch.partner	partner
Clinch Cookie Id	partners.clinch.clinch_sid	clinch-sid [1]
Clinch Click Id	partners.clinch.click_id	clinchClickId_[Client Id] [2]
User Email	user.email	hem [3]
Device Mobile Identifier	context.device.advertising_id	did
Liveramp ATS Envelope	partners.clinch.ats_envelop	atsEnvelop
Uid2	partners.clinch.uid2	uid2
-	(event_name)	type [4]
Event Secondary Type	partners.clinch.stype	stype [5]
Product Type	partners.clinch.product	product [6]
Item List	items	-
Item Id	items.X.id	ids [7]
Product Category	partners.clinch.category	category
Recommended Item Id	items.X.rec_id	recommended [7]
Search Term	search_term	term
Origin City/Airport IATA Code	partners.clinch.from	from
Destination City/Airport IATA Code	partners.clinch.to	to
Departure	partners.clinch.departure	depart
Return	partners.clinch.return	return
City Code	partners.clinch.city	city
Transaction Id	id	orderId
Transaction Value	value	amount
Currency	currency	currency
TCF String	partners.clinch.tcf_string	tcf_string
US Privacy String	partners.clinch.usp_string	usp_string
Global Privacy Platform	partners.clinch.gpp_string	gpp_string
GPP Enforced Section Ids	partners.clinch.gpp_sid	gpp_sid
User Tags	partners.clinch.utags	utags

* Mandatory property. 1. Default value: from cookie clinch-sid . 2. Default value: from parameter clinchClickId_[Client Id] in Page URL or cookie with the same name. 3. Automatically hashed if passed in clear text. 4. See Quick reference. 5. Default value: from property event_name . 6. Accepted values: Ecommerce, Flight, Hotel and Car. 7. Comma-separated string with all product identifiers.