Partnerize

Datafly Signal delivers conversions to Partnerize (formerly Performance Horizon) server-to-server using the prf.hn conversion API. Sales are recorded against the stored last-click clickref, so partner commissions track accurately without a client-side tracking tag and without being affected by ad blockers or cookie deletion.

Prerequisites

Before configuring Partnerize in Signal you need:

1. An active Partnerize campaign with server-to-server (S2S / API) tracking enabled. Contact your Partnerize account manager to confirm S2S tracking is switched on for the campaign before you go live.
2. Your campaign reference (camref). Find it in the Partnerize console under Admin > Publisher. This is the only credential — Partnerize S2S tracking has no API key or secret.
3. Your site must capture the clickref URL parameter on landing pages and store it as a first-party cookie, then make it available to Signal at the point of sale (see Capturing the clickref below).

Configure in Signal

Configuration Fields

Management UI Setup

API Endpoint

Partnerize conversions are sent as a server-to-server call to the prf.hn tracking host. Parameters are expressed as colon-delimited path segments:

GET https://prf.hn/conversion/tracking_mode:api/campaign:{campaign}/clickref:{clickref}/conversionref:{order_id}/currency:{currency}/customertype:{new|existing}/voucher:{voucher}/conversion_time:{YYYY-MM-DD+HH:MM:SS}/[category:{category}/sku:{sku}/value:{value}/quantity:{quantity}]

• tracking_mode:api marks the call as server-to-server.
• campaign is your camref.
• clickref is the last-click reference that awards commission.
• conversionref is your order ID.
• Each line item is wrapped in its own [ ... ] container; multiple items are appended one after another, e.g. [sku:A/value:10.00/quantity:2][sku:B/value:40.00/quantity:1].

A 200 response means the conversion was accepted.

Identity Signals

Partnerize attribution is click-based, not identity-based — it does not use hashed email or phone. The single identifier that matters is the clickref.

Capturing the clickref

When a partner sends a visitor to your site, Partnerize appends a clickref URL parameter to the landing-page URL. You must:

1. Read the clickref query parameter on every landing page.
2. Store the most recent value in a first-party cookie (last click wins).
3. Replay that stored value to Signal on the Order Completed event so it can be sent as clickref in the conversion call.

Signal reads the click reference from vendor_ids.partnerize_clickref. Surface the stored cookie value into the Signal event under that key (for example via a server-side enrichment or by passing it on the track call).

Event Mapping

Retail preset

All other events (including page) are dropped — Partnerize records conversions only.

Conversion field mapping

Example: Order Completed

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "ORD-001",
  revenue: 129.99,
  currency: "GBP",
  coupon: "SAVE10",
  customer_type: "new",
  products: [
    { sku: "SKU-A", category: "shoes", price: 49.99, quantity: 2 },
    { sku: "SKU-B", category: "bags", price: 30.01, quantity: 1 }
  ]
});

Partnerize conversion call sent by Signal:

GET https://prf.hn/conversion/tracking_mode:api/campaign:1101l1234/clickref:def456abc/conversionref:ORD-001/currency:GBP/customertype:new/voucher:SAVE10/conversion_time:2026-06-06+18:33:03/[category:shoes/sku:SKU-A/value:49.99/quantity:2][category:bags/sku:SKU-B/value:30.01/quantity:1]

Testing Your Integration

Troubleshooting