Documentation Index
Fetch the complete documentation index at: https://docs.upstackdata.com/llms.txt
Use this file to discover all available pages before exploring further.
What this setup enablesSetting up the AppLovin destination in Upstack Data enables dual tracking via browser pixel and server-side Conversions API (CAPI), recovering conversions lost to ad blockers, iOS restrictions, and cross-device journeys.
Prerequisites
Before you start, you need:- An active Upstack Data account (sign up)
- Admin access to an AppLovin Axon account
- A configured Axon Pixel in the AppLovin Dashboard — see How to find your AppLovin Pixel ID
- A Conversions API access token — see How to generate your AppLovin CAPI token
Configuration steps
Sign in to Upstack Data
Sign in to Upstack Data at app.upstackdata.com.
Open the destination configuration
In the Upstack dashboard, navigate to Event Destinations.Click + New Destination in the top-right of the page.In the Select a Destination popup, click AppLovin Axon, then click Next.
Enter your Pixel ID and CAPI token
Fill in the form:
- Pixel ID — the Event Key identifier for your Axon pixel. Find this in the AppLovin Dashboard under Account → General → Keys.
- Conversions API access token — a secure key generated from the AppLovin Dashboard under Account → General → Keys.
Need help finding these?
Configure optional settings
Enable Conversion API — Toggle this on to send events to AppLovin’s server-side Conversions API (recommended).Send User Data — Toggle this on to include hashed PII (email, phone) for improved match quality.
Create the configuration
Click the Create Configuration button.You should see a confirmation message and the AppLovin destination will appear in your Event Destinations list.
Verify the destination is healthy
In the Upstack dashboard, the AppLovin destination card should display Healthy with a green status indicator within 5 minutes.If the status shows Unhealthy:
- Confirm your Pixel ID is correct (no leading/trailing spaces).
- Confirm your Conversions API token was pasted in full (no truncation, no whitespace).
- Confirm the token was generated for the same AppLovin account as the Pixel ID.