Integrations / Attribution
AppsFlyer Android
Mobile attribution events for Android via the AppsFlyer S2S API.
Datafly Signal delivers first-party events to AppsFlyer Android server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload AppsFlyer Android expects.
Why route AppsFlyer Android 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 AppsFlyer Android optimises against are not filtered by the browser.
Client IP and user agent are preserved
Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so AppsFlyer Android attributes the event to the right session.
One consent decision governs every destination
AppsFlyer Android 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
add_to_cartloginpurchasesearchsign_upview_itemVertical presets
Retail. 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 AppsFlyer Android documentation.
Frequently asked questions
Does Datafly Signal integrate with AppsFlyer Android?
Yes. Datafly Signal delivers first-party events to AppsFlyer Android server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload AppsFlyer Android expects. The integration is included in every deployment at no additional cost.
How is server-side AppsFlyer Android tracking different from the AppsFlyer Android tag?
The AppsFlyer Android 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 AppsFlyer Android from your server, so delivery does not depend on browser conditions.
Which events can Signal send to AppsFlyer Android?
The blueprint ships with mappings for add_to_cart, login, purchase, search, sign_up, view_item. Any event in your schema can be mapped to AppsFlyer Android through pipeline configuration without a code change.
Do I need to keep the AppsFlyer Android 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 AppsFlyer Android deduplicates, then remove the tag once server-side volume matches.
Ready to move AppsFlyer Android server-side?
See how Datafly Signal delivers first-party events to AppsFlyer Android from infrastructure you control, with hashed identity and consent enforcement built in.