Integrations / Attribution
Admitad
Server-to-server affiliate conversion tracking for the Admitad (Mitgo) partner network. Reports sales, registrations, and leads to Admitad's tracking endpoint (ad.admitad.com/tt) as a trusted backend postback, attributed via the admitad_uid captured on the affiliate-link click. Immune to ad blockers and browser tracking prevention.
Datafly Signal delivers first-party events to Admitad server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Admitad expects.
Why route Admitad 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 Admitad optimises against are not filtered by the browser.
One consent decision governs every destination
Admitad 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
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 Admitad documentation.
Frequently asked questions
Does Datafly Signal integrate with Admitad?
Yes. Datafly Signal delivers first-party events to Admitad server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Admitad expects. The integration is included in every deployment at no additional cost.
How is server-side Admitad tracking different from the Admitad tag?
The Admitad 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 Admitad from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Admitad?
The blueprint ships with mappings for generate_lead, purchase, sign_up. Any event in your schema can be mapped to Admitad through pipeline configuration without a code change.
Do I need to keep the Admitad 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 Admitad deduplicates, then remove the tag once server-side volume matches.
Other attribution integrations
Ready to move Admitad server-side?
See how Datafly Signal delivers first-party events to Admitad from infrastructure you control, with hashed identity and consent enforcement built in.