Home
Connectors
Stripe - AppLovin

Send events from your Stripe-billed app to AppLovin through the Axon Pixel

Q: Do I need to keep my own Axon tag on the storefront?

No. Upstack loads the Axon Pixel for you once the destination is configured. If you already load Axon through your theme, Google Tag Manager or another app, remove that copy: two tags with the same Pixel ID can double count events.

Q: Which events does AppLovin receive?

PageView as page_view, ViewContent as view_item, AddToCart as add_to_cart, InitiateCheckout as begin_checkout and Purchase as purchase, reported from the browser through the Axon Pixel. Remove from cart, view cart, add payment info, search, lead, sign-up and subscribe are mapped too.

Q: Which customer parameters are sent to AppLovin?

Events carry email, phone and client_id when available, plus the aleid click ID for deterministic matching. The Send User Data setting includes hashed user data for better match quality.

Q: How do I check that Stripe events are reaching AppLovin?

Upstack marks the destination Healthy, and the Events section of the AppLovin Axon Dashboard shows recent events. AppLovin may take a little longer than Upstack to show them, and conversion volume may fluctuate during the first 48 hours.

Q: How long does it take to connect Stripe to AppLovin?

Most brands are live in under 20 minutes. Once Stripe events reach Upstack, every destination receives the same resolved events, AppLovin included.

Each event is resolved to a person against a 750M+ device graph, then reported to AppLovin through the Axon Pixel with the aleid click ID attached. AppLovin receives events from the browser only.

Request a demo Start free trial

US device IDs in the graph: 750M+
Match rate on events: 90%+
Identity window, per customer: Lifetime
Most brands are live: <20 min

How it flows

How a Stripe event reaches AppLovin. Sent from your app, resolved to a person, then reported through the Axon Pixel.

01 Capture

Captured from Stripe

For apps that bill through Stripe, send payment and subscription events to Upstack with the Upstack Pixel and JavaScript SDK, resolved to a customer before they reach the tools you spend on.

See the Stripe integration

StripeWhat it sends

subscription_initial_purchaseyou fire it for the first subscription order
subscription_recurring_purchaseon invoice.paid for an existing subscription
payment_succeededmaps to invoice.paid or charge.succeeded
payment_refundedmaps to charge.refunded
amount / currencyamount in cents, with invoiceId and subscriptionId

02 Understand

Resolved to one person before it leaves

Every Stripe event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.

How resolution works

Resolved before it is sent

IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
customer_typeNew or returning, resolved before send.
Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.

Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.

03 Activate

Delivered to AppLovin

Upstack loads the AppLovin Axon Pixel on your storefront and reports each event with identity data and the aleid click ID attached, so conversions are attributed to your AppLovin campaigns.

See the AppLovin integration

AppLovinWhat it receives

aleid / axwrtAppLovin click ID and attribution token
email / phone / client_iduser data, when available
transaction_idthe order, on purchase events
value / tax / shippingorder economics
itemsthe products on the event

Which events reach AppLovin

Each Upstack event is mapped to the AppLovin event below before it is sent.

Upstack event	Sent to AppLovin as	Key data on the event
Page view	page_view	url, referrer
Product view	view_item	items, value, currency
Add to cart	add_to_cart	items, value, currency
Checkout	begin_checkout	items, value, currency
Purchase	purchase	transaction_id, value, tax, shipping, items

Events carry email, phone and client_id when available, plus the aleid click ID for deterministic matching. The Send User Data setting includes hashed user data for better match quality.

The catch

AppLovin receives events from the browser only.

Upstack loads the Axon Pixel for you, so remove any other Axon tag in your theme, Google Tag Manager or another app: two tags with the same Pixel ID can double count events.

Where to check in AppLovinDelivery you can audit

AppLovin Axon Dashboard your pixel Events

Recent events appear here. AppLovin may take a little longer than Upstack to show them.

What changes

What changes when Stripe feeds AppLovin. Two gains on the AppLovin side, two on the Stripe side.

AppLovin

The Axon Pixel, loaded for you

Upstack loads the Axon Pixel once the destination is saved, so there is no separate Axon tag or second set of event mappings to maintain.

AppLovin

Identity-resolved events

Events sent to AppLovin carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.

Stripe

Subscription purchases as events

Fire subscription_initial_purchase for the first order and subscription_recurring_purchase each time a renewal is paid, so first orders and renewals are reported separately.

Stripe

Payments and refunds

payment_succeeded, payment_failed and payment_refunded each map to a Stripe event (invoice.paid or charge.succeeded, invoice.payment_failed, charge.refunded), so money events reach Upstack when your app fires them.

Setup

Live in under 20 minutes.

You need admin access to an AppLovin Axon account with an Axon Pixel set up in the AppLovin Dashboard.

Upstack dashboardExample

AppLovin Axon Destination Healthy

Read the full AppLovin setup guide

01

Install the Upstack Pixel and SDK

Add the Upstack Pixel to your app, then fire the subscription and payment events with the JavaScript SDK when Stripe reports them, such as subscription_recurring_purchase when invoice.paid fires for an existing subscription.
02

Add the AppLovin destination

Under Destinations, add AppLovin Axon with your Pixel ID, the Event Key under Account, General, Keys in the AppLovin Dashboard. Upstack then loads the Axon Pixel for you.
03

Check events in the Axon Dashboard

Upstack marks the destination Healthy, and the Events section of the AppLovin Axon Dashboard shows recent events. AppLovin may take a little longer than Upstack to show them, and conversion volume may fluctuate during the first 48 hours.

FAQ

Questions about Stripe and AppLovin.

Do I need to keep my own Axon tag on the storefront?

No. Upstack loads the Axon Pixel for you once the destination is configured. If you already load Axon through your theme, Google Tag Manager or another app, remove that copy: two tags with the same Pixel ID can double count events.

Which events does AppLovin receive?

PageView as page_view, ViewContent as view_item, AddToCart as add_to_cart, InitiateCheckout as begin_checkout and Purchase as purchase, reported from the browser through the Axon Pixel. Remove from cart, view cart, add payment info, search, lead, sign-up and subscribe are mapped too.

Which customer parameters are sent to AppLovin?

Events carry email, phone and client_id when available, plus the aleid click ID for deterministic matching. The Send User Data setting includes hashed user data for better match quality.

How do I check that Stripe events are reaching AppLovin?

Upstack marks the destination Healthy, and the Events section of the AppLovin Axon Dashboard shows recent events. AppLovin may take a little longer than Upstack to show them, and conversion volume may fluctuate during the first 48 hours.