General rules for banner ads integration

The "Google Admanager 360" serving algorithm uses a prioritisation model and acts in the present. An earlier decision as to whether an ad booking should be served may already be outdated just a few milliseconds later. It is therefore not possible to determine in advance (e.g. during the app start), whether an ad position is occupied at a later point in time.
Ad requests are always called at the beginning of a page request, unless it has been defined for a specific position that the ad requests should be called "in-view" – in other words depending on the scroll position. In-view positions are marked separately in the tagging plan.
Loaded ads remain in the page; renewed overscrolling must not call the ad once again
Some ads communicate a change in size via the event handler using a setsize event", while other (e.g. programmatic) ads do not use a setsize event. This means the app cannot rely on the occurrence of a setsize event. Positions for which no advertising is planned contain "bookouts" (ads that use a noad event). In this event, the advertising can remained undisplayed together with the ad labelling.
The app must not generally mask out the advertising and only display it retroactively. In order to avoid page skipping, the app can wait for a "short" time to determine whether a noad event is received. If no event is received during this time, it must then display the advertising. If a noad event is then nevertheless received with a delay due to poor data transmission, it is not possible to avoid page skip. Bookouts are of the sizes 320x1, 320x3, 320x4 and 320x8 (depending on position).
The app must fully show the ad container and must not cut it off or push it out of the display with higher-level padding or margin. On narrow displays (e.g. iPhone SE with a viewport width of 320px), the full width of the ad must be visible. The app must not scale ads.
In the ad integration phase before going live, we insert test bookings in all positions. If all necessary parameters (creative sizes, keywords and ad unit) have been correctly entered, the positive feedback will take the form of a test ad returned by the ad server.
Correct creative-sizes, keywords and ad unit are necessary for the display of a (test) booking. If the ad server supplies a negative answer ("no ad to show"), there is no booking for the combination of creative size, keyword and ad unit. This may be due to false configuration in the app or in the booking (if the app configuration is correct).