Integrations / Attribution
Everflow
Server-to-server conversion tracking for Everflow (partner-marketing / affiliate attribution). Matches conversions to their originating click via Everflow's transaction_id and posts sale value, order ID, currency, coupon, email, and custom advertiser datapoints to your Everflow tracking domain over an HTTP GET postback. Everflow ingests conversions only (not page views), so non-conversion events are dropped.
Datafly Signal delivers first-party events to Everflow server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Everflow expects.
Why route Everflow 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 Everflow optimises against are not filtered by the browser.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what Everflow needs to attribute the event to the right session.
One consent decision governs every destination
Everflow 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
_comment_no_pageviewgenerate_leadpurchaseVertical 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 Everflow documentation.
Frequently asked questions
Does Datafly Signal integrate with Everflow?
Yes. Datafly Signal delivers first-party events to Everflow server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Everflow expects. The integration is included in every deployment at no additional cost.
How is server-side Everflow tracking different from the Everflow tag?
The Everflow 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 Everflow from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Everflow?
The blueprint ships with mappings for _comment_no_pageview, generate_lead, purchase. Any event in your schema can be mapped to Everflow through pipeline configuration without a code change.
Do I need to keep the Everflow 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 Everflow deduplicates, then remove the tag once server-side volume matches.
Other attribution integrations
Ready to move Everflow server-side?
See how Datafly Signal delivers first-party events to Everflow from infrastructure you control, with hashed identity and consent enforcement built in.