Integrations / Advertising
AppLovin
Server-side web conversion delivery to the AppLovin / Axon Conversion API (CAPI). Sends events to https://b.applovin.com/v1/event with SHA-256 hashed email/phone, the Axon Pixel cookie (axwrt) and click id (aleid) for identity matching, IP and user-agent forwarded from the original request, and GA4-style e-commerce event mapping.
Datafly Signal delivers first-party events to AppLovin server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload AppLovin expects.
Why route AppLovin 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 AppLovin optimises against are not filtered by the browser.
Email and phone number hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so AppLovin receives match keys rather than raw personal data.
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 AppLovin attributes the event to the right session.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the AppLovin rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
AppLovin 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_payment_infoadd_to_cartbegin_checkoutgenerate_leadloginpagepurchaseremove_from_cartsearchsign_upview_cartview_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 AppLovin documentation.
Frequently asked questions
Does Datafly Signal integrate with AppLovin?
Yes. Datafly Signal delivers first-party events to AppLovin server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload AppLovin expects. The integration is included in every deployment at no additional cost.
How is server-side AppLovin tracking different from the AppLovin tag?
The AppLovin 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 AppLovin from your server, so delivery does not depend on browser conditions.
What personal data is sent to AppLovin?
Email and phone number are normalised and SHA-256 hashed inside your own deployment before delivery, so AppLovin receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to AppLovin?
The blueprint ships with mappings for add_payment_info, add_to_cart, begin_checkout, generate_lead, login, page, purchase, remove_from_cart, and more. Any event in your schema can be mapped to AppLovin through pipeline configuration without a code change.
Do I need to keep the AppLovin 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 AppLovin deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move AppLovin server-side?
See how Datafly Signal delivers first-party events to AppLovin from infrastructure you control, with hashed identity and consent enforcement built in.