Integrations / Attribution
Rockerbox
Server-side conversion delivery to the Rockerbox real-time conversion webhook for multi-touch attribution. Sends one conversion per request with plaintext email/phone (Rockerbox hashes server-side), customer_id, snake_case action, and epoch-seconds timestamp.
Datafly Signal delivers first-party events to Rockerbox server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Rockerbox expects.
Why route Rockerbox 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 Rockerbox optimises against are not filtered by the browser.
One consent decision governs every destination
Rockerbox 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_leadpagepurchasesign_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 Rockerbox documentation.
Frequently asked questions
Does Datafly Signal integrate with Rockerbox?
Yes. Datafly Signal delivers first-party events to Rockerbox server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Rockerbox expects. The integration is included in every deployment at no additional cost.
How is server-side Rockerbox tracking different from the Rockerbox tag?
The Rockerbox 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 Rockerbox from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Rockerbox?
The blueprint ships with mappings for generate_lead, page, purchase, sign_up. Any event in your schema can be mapped to Rockerbox through pipeline configuration without a code change.
Do I need to keep the Rockerbox 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 Rockerbox deduplicates, then remove the tag once server-side volume matches.
Other attribution integrations
Ready to move Rockerbox server-side?
See how Datafly Signal delivers first-party events to Rockerbox from infrastructure you control, with hashed identity and consent enforcement built in.