Clinch
Datafly Signal sends website events to Clinch (Flight Control) through the server-to-server website pixel, for dynamic creative optimisation and attribution.
Why route Clinch through Datafly Signal
- Conversions survive ad blockers and tracking prevention. A browser tag served from an advertising domain is blocked outright for part of your traffic. Signal sends the event from your own server, so the conversions Clinch optimises against are not filtered by the browser.
- One consent decision governs every destination. Clinch is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
- No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.
Prerequisites
Create a website pixel data source
In Flight Control open Account > Data Sources > Create > Add Website Pixel. Download its pixel code to find the client ID (cid) and data source ID (dsid). The pixel code does not need to be on your site. Clinch recommends reviewing server-side identity matching with a Clinch solution architect first.
Collect the Clinch cookie ID (optional)
Collect the clinch-sid first-party cookie with an ID provider named clinch_sid.
Configure in Signal
Configuration fields
| Field | Required | Description |
|---|---|---|
cid | Yes | The encoded client ID of your Clinch website pixel data source (Flight Control > Account > Data Sources > Download pixel code). |
dsid | Yes | The pixel (data source) ID from the same website pixel data source. |
partner | No | Optional. Only when Clinch has set up custom partner logic and gave you a partner ID. |
Management UI setup
- Go to Integrations > Add Integration > Clinch.
- Choose a preset: Default (
default), E-commerce (ecommerce), Travel (travel). - Fill in the fields above and click Save.
Request format
GET https://trkweb.clinch.co/trk?cid=CID_ENC&dsid=DSID_1&type=conv×tamp=1758500000123
&user_ip=203.0.113.9&user_agent=Mozilla%2F5.0...&referrer=https%3A%2F%2Fshop.example.co.uk%2Fcheckout%2Fdone
&hem=86e0b9e5...&orderId=ORD-1001&amount=259.99¤cy=GBP&ids=SKU_1,SKU_2&product=EcommerceNo authentication beyond cid and dsid.
Event mapping
| Signal event | Vendor event | Presets |
|---|---|---|
page | PageView | Default, E-commerce, Travel |
view_item | Details | Default, E-commerce |
add_to_cart | AddToCart | Default, E-commerce |
begin_checkout | Checkout | Default, E-commerce |
purchase | conv | Default, E-commerce, Travel |
sign_up | Registration | Default, E-commerce |
search | Search | E-commerce |
view_item_list | Category | E-commerce |
remove_from_cart | RemFromCart | E-commerce |
view_cart | CartPage | E-commerce |
add_to_wishlist | AddToWishList | E-commerce |
flight_searched | Search | Travel |
hotel_searched | Search | Travel |
flight_viewed | Details | Travel |
hotel_viewed | Details | Travel |
booking_started | Checkout | Travel |
Events not listed are not sent (the presets drop unmapped events). Each preset turns on the strict output contract, so only the mapped fields are sent.
Identity
Identifiers: the Clinch cookie ID, a SHA-256 of the normalised email (hem), the mobile advertising ID and the UID2 token, with the TCF string when present.
Limitations
- The Clinch click ID parameter is named
clinchClickId_<cid>, a name that differs per account; a blueprint cannot name a target from configuration yet (#1405), so it is not sent.
Vendor documentation
Clinch (read 2026-09-22).