AppLovin (Axon)
Datafly Signal sends website events to AppLovin Axon through the Conversion API.
Why route AppLovin (Axon) 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. Signal sends the event from your own server, so the conversions AppLovin (Axon) optimises against are not filtered by the browser.
- One consent decision governs every destination. AppLovin (Axon) is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
- No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.
Prerequisites
Get your keys
In Axon Ads Manager open Keys and copy the Event Key (pixel ID) and the Conversion API Key.
Collect the Axon identifiers (optional)
If the Axon pixel is on your site, collect its _axwrt cookie and the aleid click parameter (or _axeid cookie) with ID providers named axwrt and aleid. Without them Signal sends its first-party ID as client_id.
Configure in Signal
Configuration fields
| Field | Required | Description |
|---|---|---|
event_key | Yes | Your Axon Event Key (pixel identifier), sent as the pixel_id query parameter. Found in the Keys section of the Axon Ads Manager dashboard. |
conversion_api_key | Yes | Your Conversion API Key, sent in the Authorization header. Generated in the Keys section of the Axon Ads Manager dashboard. Keep this secret. |
Management UI setup
- Go to Integrations > Add Integration > AppLovin (Axon).
- Choose a preset: Default (
default), E-commerce (ecommerce), Lead generation (lead_gen), Insurance (insurance). - Fill in the fields above and click Save.
Request format
POST https://b.applovin.com/v1/event?pixel_id=<Event Key>
Authorization: <Conversion API Key>
{"events":[{"name":"purchase","event_time":1758500000123,
"event_source_url":"https://shop.example.co.uk/checkout/done","dedupe_id":"evt-1",
"user_data":{"client_ip_address":"203.0.113.9","client_user_agent":"Mozilla/5.0 ...","esi":"web",
"client_id":"df_anon","email":"86e0b9e5...","phone":"11072303..."},
"data":{"transaction_id":"ORD-1001","value":259.99,"currency":"GBP","tax":43.33,"shipping":10,
"items":[{"item_id":"SKU_1","item_name":"Parka","price":120,"quantity":2}]}}]}Up to 100 events per request; one invalid event fails the batch.
Event mapping
| Signal event | Vendor event | Presets |
|---|---|---|
page | page_view | Default, E-commerce, Lead generation, Insurance |
view_item | view_item | Default, E-commerce |
add_to_cart | add_to_cart | Default, E-commerce |
begin_checkout | begin_checkout | Default, E-commerce |
purchase | purchase | Default, E-commerce, Insurance |
search | search | E-commerce |
remove_from_cart | remove_from_cart | E-commerce |
view_cart | view_cart | E-commerce |
add_payment_info | add_payment_info | E-commerce |
sign_up | sign_up | E-commerce, Lead generation |
login | login | E-commerce |
generate_lead | generate_lead | E-commerce, Lead generation, Insurance |
quote_completed | generate_lead | Insurance |
Events not listed are not sent (the presets drop unmapped events). Each preset turns on the strict output contract, so only the mapped fields are sent.
Identity
user_data carries the visitor IP and user agent, esi=web, Signal’s first-party ID as client_id, the Axon axwrt cookie and aleid click ID when collected, your user ID, and SHA-256 hashes of the normalised email and of the phone number as digits with country code.
Limitations
- Axon asks for value on purchase as the subtotal before tax and shipping; Signal sends the event’s value, which in the Datafly event spec includes them.
- Axon’s email hashing also removes dots and +tags from Gmail addresses; Signal’s normalisation does not yet (#784), so some Gmail hashes will not match.
- page_view is sent without a data object.
Vendor documentation
AppLovin (Axon) (read 2026-09-22).