Conversion API

Use the Conversion API to send conversion events for your website. AppLovin recommends that advertisers use the Conversion API alongside the Axon Pixel. This helps you achieve optimal campaign performance.

Request format

To submit one or more events to the Conversion API, send an HTTP POST request to https://b.applovin.com/v1/event.

Authentication

Header nameValue
AuthorizationYour Conversion API key

To get your Conversion API Key, contact your Axon representative or Support.

Query parameters

NameTypeRequiredDescription
pixel_idstringtrueYour pixel ID

Response codes

CodeDescription
200All events processed successfully.
400There is an error with your request. This batch of events was dropped.
401Authentication failed.

POST payload

The POST payload of your HTTP request describes the event or events that you submit:

NameTypeRequiredDescription
eventsServer event[]trueList of events to submit. All events must be valid. Any invalid event fails the batch. Maximum batch size is 100.

Server event

NameTypeRequiredDescription
dataEvent datatrueThe data for this event. See the Events and objects page for the data to send with each Event.
event_source_urlstringtrueThe complete URL where the event occurred (e.g. https://example.com/product?product_name=widget)
event_timenumbertrueThe current Unix epoch time in milliseconds
namestringtrueThe name for this event. See the Events and objects reference for available events.
user_dataUser datatrueRefer to the User data table below with data fields such as aleid, client_id, axwrt, alart, etc.
measurement_partner_dataMeasurement datafalseMeasurement data to inform how much credit is given to AppLovin for the event
dedupe_idstringfalseA unique identifier for this event. Axon uses this for de-duplication. The same pixel event and server-to-server event should have the same dedupe_id.
Note: this is different than aleid below.

Event data

Refer to Events and objects to learn how to populate the data field for each event. In addition to the events documented in this link you can find additional supported events below.

Optional events

app_open event (mobile app integrations only)

Trigger this event when a user starts the app. There is no data object to pass for this event.

User data

NameTypeRequiredDescription
alartstringtrue*alart set as a query parameter.
*See Sending user identifiers below for more details.
aleidstringtrue*See Sending aleid below for additional details.
*Required if present in the URL (sent by AppLovin after ad click)
axwrtstringtrue*The axwrt set in the Axon Pixel.
*See Sending user identifiers below for more details.
client_idstringtrue*A stable first-party user identifier.
*See Sending user identifiers below for more details.
client_ip_addressstringtrueIP address (without any spaces) of the browser corresponding to the event. You can use either an IPv4 or an IPv6 address. IPv4 is better.
client_user_agentstringtrueUser Agent of the device/browser
emailstringtrue*The user’s email address. Axon automatically hashes this value using SHA-256. You can also provide your own SHA-256 hash if you preprocess the identifier according to Axon’s hashing guidelines.
*See Sending user identifiers below for more details.
esistringtrueEvent source indicator. Use "app" for mobile app events or "web" for website events.
phonestringtrue*The user’s phone number. Axon automatically hashes this value using SHA-256. You can also provide your own SHA-256 hash if you preprocess the identifier according to Axon’s hashing guidelines.
*See Sending user identifiers below for more details.
user_idstringtrue*The unique identifier for a customer.
*See Sending user identifiers below for more details.
country_codestringfalseThe user’s billing country code. Follow the ISO 3166 standard.
ifastringfalseThe user’s identifier for advertisers: idfa or gaid
idfvstringfalseThe user’s identifier for vendors
osstringfalseThe user’s operating system: ios, android, or desktop_os
sidstringfalseSession ID
zipstringfalseThe user’s billing zip code. Use only the first five digits for U.S. zip codes.

Measurement data

NameTypeRequiredDescription
accounting_modestringtrueEither CASH or ACCRUAL
attribution_lookback_window_hoursnumbertrueDuration in hours of how far back a touchpoint can occur to gain credit for the conversion. Leave empty for infinite lookback.
attribution_modelstringtrueOne of LAST_CLICK, FIRST_CLICK, LINEAR, TIME_DECAY, CUSTOM_MULTI_TOUCH, LAST_NON_DIRECT_TOUCH, CLICKS_AND_VIEWS_ENHANCED, or ANY_CLICK
attribution_sharenumbertrueNumber between 0 and 1 representing the credit AppLovin gets for the event based on the given attribution model and lookback
is_claimablebooleantrueFlag to indicate if AppLovin drove the event
campaign_idstringfalseAppLovin’s campaign ID
creative_set_idstringfalseAppLovin’s creative set ID. Also known as adset ID
first_purchase_tsnumberfalseEpoch timestamp in milliseconds of when the customer first made a purchase with the advertiser
first_visit_tsnumberfalseEpoch timestamp in milliseconds of when the customer first visited the advertiser
is_new_customerbooleanfalseWhether the customer has made a purchase with the advertiser before
is_new_visitorbooleanfalseWhether the customer has visited the advertiser before
last_purchase_tsnumberfalseEpoch timestamp in milliseconds of when the customer last made a purchase with the advertiser
last_visit_tsnumberfalseEpoch timestamp in milliseconds of when the customer last visited the advertiser

Sending aleid

aleid is a query parameter that AppLovin adds to website URLs after a user clicks an AppLovin ad.

Use the presence of this parameter to identify which clicks come from AppLovin.

To send the aleid, you can do one of the following:

  • If you have the Axon Pixel installed on your site, the Axon Pixel automatically sets the cookie _axeid when it sees the aleid query parameter. Whenever you see such a cookie, read its value and then send it in your request by making it the value of the aleid query parameter.
  • When you see that the aleid URL query parameter is present, retrieve its value. When your server sees the aleid query parameter, read the parameter server-side. AppLovin recommends that you set this as an HTTP cookie with name _axeid on your site. Set this cookie to have a one-year expiration time. As in the previous method, whenever you see such a cookie, read its value and then send it in your request by making it the value of the aleid query parameter.

Sending user identifiers

Axon requires that you pass at least one of the following fields: client_id, axwrt, alart, user_id, email, or phone.

client_id
If you don’t have the AXON Pixel installed on your site, pass another stable first-party cookie you store to identify visitors. It should be globally unique and stay the same across browsing sessions of the user.
axwrt
If you have the AXON Pixel installed on your site, the AXON Pixel automatically sets the cookie _axwrt.
alart
For App users, when you see the alart URL query parameter is present, retrieve its value.
user_id
The unique identifier for a customer in your system. This should be a stable identifier that remains consistent across user sessions.
email
The user’s email address. Axon automatically hashes this value using SHA-256 for privacy protection. You can also provide your own SHA-256 hash if you preprocess the identifier according to Axon’s guidelines.
phone
The user’s phone number. Axon automatically hashes this value using SHA-256 for privacy protection. You can also provide your own SHA-256 hash if you preprocess the identifier according to Axon’s guidelines.

Example payload

[
  {
    "event_time": 1741784485001,
    "event_source_url": "https://applovin.com",
    "name": "purchase",
    "user_data": {
      "client_ip_address": "172.59.8.172",
      "client_user_agent": "chrome/123.456 android mobile",
      "aleid": "_aleid-query-param",
      "axwrt": "_axwrt-cookie-value",
      "email": "user@example.com",
      "phone": "+11234567890",
      "user_id": "customer_12345",
      "client_id": "_first_party_identifier",
      "sid": "sid",
      "ifa": "idfa",
      "idfv": "idfv",
      "os": "macos",
      "esi": "web",
      "zip": "12345",
      "country_code": "US"
    },
    "measurement_partner_data": {
      "is_claimable": true,
      "attribution_model": "LAST_CLICK",
      "attribution_lookback_window_hours": 24,
      "attribution_share": 0.5,
      "accounting_mode": "ACCRUAL",
      "campaign_id": "456",
      "creative_set_id": "789",
      "is_new_customer": false,
      "last_purchase_ts": null,
      "is_new_visitor": true,
      "last_visit_ts": 1
    },
    "data": {
      "user_id": "customer_12345",
      "currency": "USD",
      "value": 30,
      "transaction_id": "txn_abc123_20250120",
      "shipping": 5.99,
      "tax": 6,
      "items": [
        {
          "item_variant_id": "SKU-123-M",
          "item_id": "PROD-456",
          "item_name": "T-Shirt",
          "affiliation": "affiliation",
          "item_brand": "item_brand",
          "item_category": "item_category",
          "item_category_id": 604,
          "item_category2": "item_category2",
          "image_url": "image_url",
          "price": 15,
          "discount": 10,
          "quantity": 2
        }
      ]
    }
  }
]
Was this article helpful?
search