Skip to main content

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.

New to Upstack? Follow the getting started guide for a streamlined onboarding walkthrough.
  • Configure the AppLovin destination in Upstack Data with your Pixel ID (Event Key) and Conversions API access token.
  • Verify events appear in the AppLovin Axon Dashboard Events section within 5-10 minutes.
  • Monitor match quality improvements as more identified customers convert.

​
Prerequisites

Before you start, you need:
1

Locate your AppLovin Pixel ID (Event Key)

In the AppLovin Dashboard, navigate to Account → General → Keys to find your Event Key (Pixel ID).Help guide:How to find your AppLovin Pixel ID →
2

Generate a Conversions API access token

In the AppLovin Dashboard, navigate to Account → General → Keys and generate a new Conversions API Key.Help guide:How to generate your AppLovin CAPI token →
3

Configure the AppLovin destination in Upstack Data

In the Upstack dashboard, navigate to Event Destinations and add an AppLovin destination using your Pixel ID and Conversions API access token.Help guide:How to configure the AppLovin destination in Upstack Data →
4

Verify the full setup is healthy

Confirm each piece of the setup is working:
  • In the Upstack dashboard, Event Destinations shows your AppLovin destination as Healthy (green).
  • In the AppLovin Axon Dashboard, the Events section shows recent events arriving via the Conversions API.
  • Events appear within 5-10 minutes of storefront activity.
If anything is unhealthy, check the corresponding help guide above for troubleshooting steps.

​
What to expect after setup

​
Event delivery timeline

  • Events start appearing in the AppLovin Dashboard within 5-10 minutes of storefront activity.
  • Match quality improves as more identified customers (with email/phone at checkout) convert.
  • The dedupe_id ensures browser Pixel events and server-side CAPI events are not double-counted.

​
Reporting differences

  • Your AppLovin campaign performance will likely improve after a few days as the algorithm receives more complete conversion data.
  • Conversion volume may temporarily fluctuate during the first 48 hours as AppLovin’s deduplication logic adjusts to receiving both pixel and CAPI events.
Important: AppLovin’s batch API drops the entire batch if any single event is invalid. Ensure all events include a dedupe_id and at least one user identifier (aleid, axwrt, client_id, email, phone, or user_id).
Need help?If you encounter any issues during setup or events aren’t appearing after 15 minutes, contact our support team with your AppLovin Pixel ID and we’ll help diagnose the problem.