Integrations / Attribution
Partnerize
Server-to-server affiliate and partner-marketing conversion tracking via the Partnerize prf.hn conversion API. Records sales against the last-click clickref so partner commissions track without a browser pixel.
Datafly Signal delivers first-party events to Partnerize server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Partnerize expects.
Why route Partnerize 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 Partnerize optimises against are not filtered by the browser.
One consent decision governs every destination
Partnerize 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
pagepurchaseVertical presets
Retail. 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 Partnerize documentation.
Frequently asked questions
Does Datafly Signal integrate with Partnerize?
Yes. Datafly Signal delivers first-party events to Partnerize server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Partnerize expects. The integration is included in every deployment at no additional cost.
How is server-side Partnerize tracking different from the Partnerize tag?
The Partnerize 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 Partnerize from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Partnerize?
The blueprint ships with mappings for page, purchase. Any event in your schema can be mapped to Partnerize through pipeline configuration without a code change.
Do I need to keep the Partnerize 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 Partnerize deduplicates, then remove the tag once server-side volume matches.
Other attribution integrations
Ready to move Partnerize server-side?
See how Datafly Signal delivers first-party events to Partnerize from infrastructure you control, with hashed identity and consent enforcement built in.