( An endpoint is a web URL where information, like postbacks, can be sent by an advertisement network to an advertiser.).
AppLovin wasnt claiming credit for any of these installs. Acquiring presence into all of a marketers postbacks would reveal which networks were winning quotes for any impressions served in apps generating income from with MAX.
And if AppLovin might see that a certain app is a great source of installs, for instance, it could theoretically use that info to notify its own automatic quotes on behalf of that advertiser.
AppLovin claims it did not actually gather any of the data, although only AppLovin understands if thats genuinely the case.
According to AppLovin, the Unity plugin in question was benign instead of a data grab. (A Unity plugin is a software add-on utilized by SDKs that provides access to functions such as third-party libraries or OS calls.).
In a declaration shown AdExchanger, an AppLovin spokesperson said the plugin was “designed to develop an app that is all set to test/submit to the app store” which “this feature demand was documented for all designers using native combination and our Unity plugin.”.
AppLovin has actually because stopped this practice and instituted a code upgrade that gives developers the choice to by hand set their NSAdvertisingAttributionReportEndpoint. AppLovins endpoint is no longer the default.
Just what occurred on the backend.
Apples new SKAdNetwork structure sends out a postback from the users device straight to the advertisement network that should have credit when an install occurs on iOS 14+.
Some marketers were worried that advertisement networks, consisting of Facebooks, would not always share these postbacks with them. And so, beginning with iOS 15, Apple began permitting marketers to get a copy of these postbacks by themselves– a sort of “god mode” view of installs associated for their app across all ad networks. Designers do this by defining their own URL (referred to as the NSAdvertisingAttributionReportEndpoint).
The MAX SDK was accessing iOS 15 postback data automatically by bypassing the NSAdvertisingAttributionReportEndpoint a designer had set as the destination for where SKAdNetwork was expected to send out postback details and replacing it with an AppLovin endpoint.
With this setup, AppLovin was in a position to piggyback off its money making offering and obtain info it might utilize to benefit its advertisement network– but without the understanding of its designer partners.
AppLovin stated that it enabled this configuration to make life easier for its clients. “While a lot of our developers by hand allow NSAdvertisingAttributionReportEndpoint utilizing the guidelines in our documentation, our Unity plugin permits developers a method to automate many steps of a combination procedure, consisting of the function in concern,” the spokesperson stated.
In other AppLovin news, the business just dropped a cool $1.05 billion in cash to obtain MoPub from Twitter last week– resulting in one less independent mediation option available to app developers.

Designers have actually been reporting apparently weird habits from AppLovins MAX Unity SDK.
At least one developer discovered that MAX, AppLovins in-app money making solution, appears to have been recording iOS 15 postbacks for installs produced by other advertisement networks immediately and without approval.
The suggestion was shared anonymously with the mobile ad industry forum Mobile Dev Memo.
Postback data is like an invoice with basic details about a set up and the project that caused it. Due to the fact that it shows which apps are sources of good traffic and which ad networks are most effective at driving certain outcomes, its valuable.
To the MAX
Its crucial to keep in mind that there is no PII in a SKAdNetwork postback.
At problem was the truth that AppLovin could see the attribution postbacks for all of a marketers installs, not simply its own, even if the developer had actually explicitly defined a various endpoint for where to send out postbacks.