Should we send server-side events to AppLovin, and how?
Our answer
Send purchases or qualified leads to AppLovin's Conversion API alongside the pixel, not instead of it. Keep the Shopify app, add server events through a tracking tool or your server, and use the order ID as dedupe_id on both.
- Confidence
- High
- Strongest proof
- 9 AppLovin rules
- 4 practitioners, 4 opinions or claims
- Sources
- 8 sources
- 17 statements
- A
E
AMSPDN
New here? Take the 1-minute tour
Why this is the answer
3 reasons and our judgmentAppLovin itself recommends the Conversion API alongside the pixel. Its FAQ tells lead generation businesses to connect it for a stronger signal on lead quality.
Duplicates are handled if both copies share an ID. AppLovin merges events with the same dedupe_id that arrive within 30 seconds and drops a duplicate more than 5 minutes later. Jetfuel Agency and Attribuly both key the browser and server copies to the order.
Browser-only tracking may miss purchases. Jetfuel Agency estimates it loses 20 to 40% of purchases to ad blockers and Safari. Sweat Pants Agency and Pilothouse still launch on the app alone.
Our judgment
Keep the Shopify app installed after you add server events. AppLovin recommends the pairing, its Prospecting campaigns rely on the order history the Shopify app supplies, and the setup from Elevar (Shopify server-side tracking vendor) keeps the app installed for that reason. A consumer brand testing on a small budget can launch on the Shopify app and add server events before it scales. That combines Attribuly's advice to move past pixel-only once browser tracking proves fragile, the app-only launches of Sweat Pants Agency and Pilothouse, and Jetfuel Agency's observation that brands past $10K a day have this wired while those stuck at $1K usually don't. Use the order ID as the dedupe_id on both the pixel and the server purchase, and fire the server event when the order is paid, going by AppLovin's deduplication rules and Jetfuel Agency's setup.
Our judgment, built from AppLovin, Elevar, Attribuly, Sweat Pants Agency, Pilothouse and Jetfuel: our reading of these sources, not a finding from any one of them.
What the sources say
17 statements from 8 sourcesAppLovin recommends running its Conversion API alongside the AppLovin Pixel, sending the same dedupe_id for matching pixel and server events, in batches of up to 100.
“The same pixel event and server-to-server event should have the same dedupe_id”
AppLovin's Conversion API docs say each server event needs a real public client IP, a user agent, and at least one identifier such as client_id, email or phone. Any invalid event fails the whole batch.
“Any invalid event fails the batch.”
AppLovin says to pass the same dedupe_id when one event is sent through more than one integration; events within 30 seconds are merged and a repeat after 5 minutes is dropped.
“pass the same dedupe_id to each of your integrations”
AppLovin's launch checklist says to connect the Conversion API after choosing an optimization type, install the pixel, and validate it with its Pixel Helper. The 'stronger signal' benefit is AppLovin's own claim.
“Connect the Conversion API for stronger optimization signal.”
AppLovin tells lead-gen and digital services businesses to connect its Conversion API alongside the pixel so its model can optimize for lead quality. Shopify stores should install its app, which sets up tracking.
“It gives the model stronger signal to optimize toward lead quality, and lets you avoid sending leads that aren't valuable to your business.”
AppLovin recommends using its Conversion API alongside the Pixel for lead gen, sending generate_lead only for qualified leads with a value, and matching dedupe IDs across both.
“Send generate_lead only for qualified leads; do not send event for unqualified leads such as duplicate submissions or low-quality leads”
AppLovin's restricted lead-generation API accepts only listed fields, and asks advertisers to pass higher values for strong leads and 0 for duplicate or poor leads, which may be left out of optimization.
“Leads with a value of 0 may be discounted or excluded from optimization.”
AppLovin highly recommends sharing order history to optimize prospecting, either through its Shopify app or a CSV upload, subject to your own privacy notices and consents.
“To optimize prospecting campaigns (which acquire new customers), AppLovin highly recommends that you provide AppLovin with order history data.”
Shopify says pairing server pixels with web pixels gets the most customer events through; ad blockers can block web pixels, which cuts third-party attribution but not Shopify's own reports.
“What's reduced or lost is third-party attribution”
Metorik, which sells profit reporting, says WooCommerce has no AppLovin plugin, so add the pixel through Google Tag Manager, a pixel-manager plugin or a server-side connector, then check it with Pixel Helper.
“WooCommerce has no AppLovin plugin.”
Elevar, which sells server-side tracking, says its September 2026 release moved AppLovin from beta to a stable destination. This is a note about its own product, not an AppLovin change.
“AppLovin has been promoted to a stable destination!”
Elevar, which sells server-side tracking, says to set up AppLovin through its destination and avoid duplicate events by removing previous tracking. Keep the Shopify AppLovin app installed but disable its data sending.
“Do NOT uninstall the AppLovin app. Instead, disable sending data via the AppLovin app.”
Pilothouse, which sells AppLovin management, says the AppLovin pixel is simple to install on Shopify, and once tracking and UTMs check out, a new campaign should be left alone for one to two weeks.
“Just leave it for a week, maybe even two weeks.”
Attribuly, which sells attribution tools, lists three ways to track AppLovin ROAS on Shopify: pixel-only, MMP postbacks, or server-side hybrid, which it calls most resilient. It suggests starting with a pixel.
“Choose one of three viable paths: pixel-only (fast), MMP postbacks (integrated), or server-side/hybrid (most resilient with dedup).”
Jetfuel, an agency, estimates that browser-only tracking loses 20 to 40% of purchase events, with no data shown, and says wiring AppLovin's Conversion API before launch shortens the warmup.
“Wiring CAPI before launch compresses the warmup phase materially.”
Jetfuel, which audits AppLovin accounts, says the default Shopify app install misses real setup work, and to dedupe server events by order ID or Axon counts purchases twice and overbids.
“Axon counts both events, the reported value doubles, and the bidder overpays accordingly”
Sweat Pants Agency, which runs AppLovin tests for clients, says the Shopify app installs the AppLovin tracking pixel automatically, and setup takes under 30 minutes once your account is approved.
“The full setup takes under 30 minutes if your Axon account is already approved.”
In the full answer
For readers who sign in- What to do this week3 steps
- The numbers behind it3 figures from cited sources
- Where each source standsA chart placing each source on the question
- The strongest disagreementThe best case against the answer, from a cited source
- How sure we areWhat its confidence rests on, and what would change the answer