Integrations / Attribution
Voluum
Server-side conversion tracking via Voluum's S2S postback. Matches conversions to their originating click using the Voluum click ID (cid) captured client-side at landing time, and sends payout, transaction ID, currency, and event type to your Voluum tracking domain. Voluum has no pageview/analytics ingestion, so non-conversion events are dropped.
Datafly Signal delivers first-party events to Voluum server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Voluum expects.
Why route Voluum 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 Voluum optimises against are not filtered by the browser.
One consent decision governs every destination
Voluum 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
purchasesign_upVertical 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 Voluum documentation.
Frequently asked questions
Does Datafly Signal integrate with Voluum?
Yes. Datafly Signal delivers first-party events to Voluum server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Voluum expects. The integration is included in every deployment at no additional cost.
How is server-side Voluum tracking different from the Voluum tag?
The Voluum 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 Voluum from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Voluum?
The blueprint ships with mappings for purchase, sign_up. Any event in your schema can be mapped to Voluum through pipeline configuration without a code change.
Do I need to keep the Voluum 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 Voluum deduplicates, then remove the tag once server-side volume matches.
Other attribution integrations
Ready to move Voluum server-side?
See how Datafly Signal delivers first-party events to Voluum from infrastructure you control, with hashed identity and consent enforcement built in.