Integrations / Attribution
Webgains
Server-to-server conversion tracking for the Webgains affiliate network via the queue-conversion (S2S Conversion) API. Delivers sales and leads with item-level basket data, attributed by the first-party Webgains click identifier (s2s). Immune to ad blockers, ITP, and cookie deletion. programId and the commission eventId come from integration config.
Datafly Signal delivers first-party events to Webgains server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Webgains expects.
Why route Webgains 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 Webgains optimises against are not filtered by the browser.
One consent decision governs every destination
Webgains 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_leadpurchasesign_upVertical presets
Retail, Lead Generation. 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 Webgains documentation.
Frequently asked questions
Does Datafly Signal integrate with Webgains?
Yes. Datafly Signal delivers first-party events to Webgains server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Webgains expects. The integration is included in every deployment at no additional cost.
How is server-side Webgains tracking different from the Webgains tag?
The Webgains 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 Webgains from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Webgains?
The blueprint ships with mappings for generate_lead, purchase, sign_up. Any event in your schema can be mapped to Webgains through pipeline configuration without a code change.
Do I need to keep the Webgains 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 Webgains deduplicates, then remove the tag once server-side volume matches.
Other attribution integrations
Ready to move Webgains server-side?
See how Datafly Signal delivers first-party events to Webgains from infrastructure you control, with hashed identity and consent enforcement built in.