Clinch

Send conversion events to Clinch for dynamic creative optimisation (DCO), personalised ad delivery, and cross-channel performance measurement.

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, and Safari’s ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Clinch optimises against are not filtered by the browser.
• Email is hashed before leaving your infrastructure. Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Clinch receives match keys rather than raw personal data.
• Client IP and user agent are preserved. Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so Clinch attributes the event to the right session.
• 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

Complete these steps in the Clinch platform before configuring the integration in Signal.

Configuration

Signal Setup

Quick Setup

1. Navigate to Integrations in the sidebar.
2. Open the Integration Library tab.
3. Find Clinch or filter by Advertising.
4. Click Install, select a variant if available, and fill in the required fields.
5. Click Install Integration to create the integration with a ready-to-use default configuration.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/clinch/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Clinch",
    "variant": "default",
    "config": {
      "advertiser_id": "clinch-adv-12345",
      "api_key": "ak_clinch_abc123..."
    },
    "delivery_mode": "server_side"
  }'

API endpoint

GET https://trkweb.clinch.co/trk

Allow egress to trkweb.clinch.co from the network your delivery workers run on.

Event Mapping

To customise or extend, edit the integration’s Field Mappings in the Management UI.

Delivery

Events are delivered server-side from your Datafly Signal infrastructure directly to the Clinch API. No client-side scripts are loaded for this integration.

Testing

1. Install the integration with your Advertiser ID and API key.
2. Trigger a test event (e.g. a product view or purchase) on your site with the Datafly.js collector active.
3. Check the Live Events view in Signal to confirm the event was captured.
4. Verify the event appears in the Clinch Flight Control platform under conversion reporting.
5. Check the Delivery Log in Signal for confirmation of successful delivery (HTTP 200 response).

Troubleshooting