Kwanko

Datafly Signal registers affiliate sales and leads with Kwanko (formerly NetAffiliation) server-to-server through the S2S postback (trk.php), attributed by the Kwanko click ID.

Why route Kwanko 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 what Kwanko receives is not filtered by the browser.
Click identifiers are captured and replayed. Signal keeps the click ID first-party when the visitor lands and attaches it to the later conversion.
One consent decision governs every destination. Kwanko 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

Get your tracking code

Kwanko provides your mclic value (the program’s tracking identifier).

Keep the Kwanko click ID

Kwanko appends the click ID to the landing URL (kwks2s, or cible by default; Kwanko can rename it). Signal reads either.

Configure in Signal

Configuration Fields

Field	Required	Description
`program_id`	Yes	Your Kwanko program / tracking identifier. Sent as the mclic parameter on every conversion. Provided by your Kwanko account manager (Advertiser dashboard > program settings).

Management UI Setup

Go to Integrations > Add Integration > Kwanko.
Choose a preset: Default (default), Retail (ecommerce), Lead Generation (lead_gen), Insurance (insurance), Travel (travel).
Fill in the fields above and click Save.

Request format

A GET with every value in the query string. Sales carry the order ID (argann), amount (argmon), currency (nacur), voucher code (argbr) and payment method (argmodp); leads carry a unique reference in argann.

GET https://action.metaffiliation.com/trk.php?argann=ORD-1001&argbr=SPRING10&argmodp=creditcard&argmon=259.99&cible=KWK-SUBID-1&gdpr_kwk=1&mclic={program_id}&nacur=GBP

Event Mapping

Signal event	Vendor event	Presets
`purchase`	`sale`	Default, Retail, Insurance, Travel
`generate_lead`	`lead`	Default, Lead Generation, Insurance
`sign_up`	`lead`	Lead Generation
`quote_completed`	`lead`	Insurance
`booking_completed`	`sale`	Travel

Identity

Attribution is by the Kwanko click ID (cible) only. No personal data is sent.

Kwanko sits in the attribution category. gdpr_kwk is 1 unless the visitor has refused marketing consent.

Known limitations

The collector does not capture Kwanko’s landing parameter yet (#1260); until it does, a conversion has a click ID only when an ID provider collects it.
Kwanko asks for the amount excluding tax and shipping; Signal sends the event value as your site reports it (#1383).

Troubleshooting

Problem	Solution
Events dropped in Signal	The visitor has no Kwanko click ID.

Blueprint

The Kwanko blueprint version is 0.5.0. It was last reviewed against the vendor’s documentation on 2026-09-22.