Integrations / Attribution
Effinity
Server-side affiliate conversion tracking for Effinity (Effiliation). Posts sale (purchase) and lead conversions to the Effiliation tracking servlet with publisher attribution carried by the eff_cpt click id. Order value, currency, order reference, new-customer flag, voucher code and click sub-ids map to Effinity's native query parameters.
Datafly Signal delivers first-party events to Effinity server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Effinity expects.
Why route Effinity 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 Effinity optimises against are not filtered by the browser.
One consent decision governs every destination
Effinity 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_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 Effinity documentation.
Frequently asked questions
Does Datafly Signal integrate with Effinity?
Yes. Datafly Signal delivers first-party events to Effinity server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Effinity expects. The integration is included in every deployment at no additional cost.
How is server-side Effinity tracking different from the Effinity tag?
The Effinity 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 Effinity from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Effinity?
The blueprint ships with mappings for generate_lead, purchase. Any event in your schema can be mapped to Effinity through pipeline configuration without a code change.
Do I need to keep the Effinity 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 Effinity deduplicates, then remove the tag once server-side volume matches.
Other attribution integrations
Ready to move Effinity server-side?
See how Datafly Signal delivers first-party events to Effinity from infrastructure you control, with hashed identity and consent enforcement built in.