For single advertising SDK and aggregated advertising SDK, the working mechanism is basically the same, both are APP startup, call SDK, trigger advertisement request, send to the advertising platform server, the advertising platform server returns the advertisement, sends the material, displays the advertisement, and only sends the advertisement.
On the ad request, the aggregated ad SDK will forward one more step, and forward the ad request to multiple ad network platforms, as shown in the following figure: Advertising SDK operating mechanism The difference is that when sending an ad request, the aggregated ad SDK will forward the request one step further, and forward the ad request to multiple job title email list ad network platforms. The workflow of the advertising SDK is very clear, but for APP developers, these may not be difficult, and the biggest concern is the security of the SDK. The main problem, first, is the SDK security vulnerability. The second is whether to reserve a "back door".
The third is whether the data is misused. In the end, the problem still falls on these three points. To avoid these problems, the best way is to check the source code of the advertising SDK. In fact, this is the way it is now. Generally, developers will review the SDK when they connect with the advertising SDK, but for developers who do not know much about the advertising industry or lack technical skills, they have both concerns and may not be able to start the SDK review. Here AdScope gives the SDK verification. Some methods to facilitate the operation of developers.