Integrations / Advertising
Kwanko
Server-to-server affiliate conversion tracking for Kwanko (formerly NetAffiliation). Captures the Kwanko click ID (kwks2s) on landing and registers validated sale and lead conversions to action.metaffiliation.com/trk.php with order ID, amount, currency, and consent flag.
Datafly Signal delivers first-party events to Kwanko server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Kwanko expects.
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 the conversions Kwanko optimises against are not filtered by the browser.
Click identifiers are captured and replayed
Signal stores click_id first-party at collection time and attaches them to the conversion later, so attribution survives even when the original landing cookie has expired.
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.
What ships in the blueprint
Mapped events
generate_leadpagepurchaseVertical presets
Default. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Kwanko documentation.
Frequently asked questions
Does Datafly Signal integrate with Kwanko?
Yes. Datafly Signal delivers first-party events to Kwanko server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Kwanko expects. The integration is included in every deployment at no additional cost.
How is server-side Kwanko tracking different from the Kwanko tag?
The Kwanko tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Kwanko from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Kwanko?
The blueprint ships with mappings for generate_lead, page, purchase. Any event in your schema can be mapped to Kwanko through pipeline configuration without a code change.
Do I need to keep the Kwanko tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so Kwanko deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Kwanko server-side?
See how Datafly Signal delivers first-party events to Kwanko from infrastructure you control, with hashed identity and consent enforcement built in.