applovin-ads-integration

Add the AppLovinSDK pod plus Google AdMob and Meta Audience Network mediation adapters to your Podfile, then initialize ALSdk in application(_:didFinishLaunchingWithOptions:) with mediationProvider set to max. You must also add NSUserTrackingUsageDescription to Info.plist and show the ATT prompt before SDK initialization.

Send a GET request to https://d.applovin.com/postback/v1/purchase with event_token, event_name=purchase, user_id, transaction_id, revenue formatted as a decimal, and currency as query parameters. Server-side postbacks are preferred because client-side events can be spoofed and give less reliable ROAS signal.

Yes, an MMP such as Adjust, AppsFlyer, or Singular is strongly recommended before running campaigns. Direct postbacks miss cross-device attribution and SKAdNetwork decoding, which MMPs handle automatically through their AppLovin integration modules.

This happens when updateConversionValue is called at payment intent rather than after final purchase confirmation. Also verify the identical conversion value schema is configured in AppLovin's SKAN configuration panel so the platform can decode postbacks.

ROAS campaigns need at least 50 purchase events per day for the algorithm to optimize, plus a minimum $200 daily budget. If underspending persists, lower your target ROAS from the 200% starting point until volume builds.

No, this integration only applies to merchants with a native iOS or Android shopping app listed on the App Store or Google Play. Web-only stores should use web advertising platforms instead.