Documentation - User contributions [en]

Integration of the Google Mobile Ads SDK

2026-02-18T10:27:21Z

Tlohmann: /* Political advertising in native apps */

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app or the homepage, e.g. ''politik'', ''openingpage''
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Content-Url parameter in the adrequest===
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Political advertising in native apps===
Political campaigns require consent from the user. In order for the ad server to take this into account correctly, it needs information from the app. The exact workflow works as follows:

====Workflow====
#The user decides in the CMP whether to give consent for political advertising
#The app evaluates the consent and checks whether consent has been given for political advertising
#If consent has been given, the app adds the keyword '''''political_ad''''' to the '''''kw''''' keywords for each ad request (see [[#Keywords (attachment of key-value pairs)]]).
#The ad server sees the keyword '''''political_ad''''' in the ad request and now has the option of delivering a political campaign targeted to that keyword (however, this is not mandatory; it can also deliver other campaigns).
#When an ad server plays a political campaign, a creative is delivered to the app that contains an additional setting in the template. This causes the creative to inform the app that the advertising slot in question actually contains a political campaign and that the app should respond by changing the ad label. The message is sent to the app via a political_ad event (see [[#Documentation of the iq digital app events]]).
#The app receives the '''''political_ad''''' event and can respond to it. iqdigital recommends that the ad label above the affected ad slot be changed to '''''Politische Anzeige''''' and that there be a link to the Political Ad Transparency URL for the campaign (which is passed in the event). '''Important''': The responsibility for whether and how the app responds to the '''''political_ad''''' event lies with the publisher and the app.

====App tasks (publisher tasks)====
*The app evaluates the consent string and checks whether the user has given consent for political advertising.
*If consent for political advertising has been given, the app adds the keyword '''''political_ad''''' to CustomTargeting (to key '''''kw''''').
*When the app receives a '''''political_ad''''' event through a creative, it should respond to it, for example by changing the ad label to '''''Politische Anzeige''''', as described above. If a URL is also passed as a data-String in the event, a link with the URL and the text '''''(mehr dazu)''''' should appear next to the ad label '''''Politische Anzeige'''''. Clicking on the link then opens the URL, where the user can find further information about the type of campaign.

====Tasks of the advertising template====
*A political campaign must be configured accordingly in the ad server. This is done via settings in the advertising template. This involves marking that the creative belongs to a political campaign and setting the PoliticalAdTransparencyUrl (for the "(mehr dazu)" link).
*The advertising template internally evaluates whether it is a political ad.
*In the case of a political advertisement, it sends an event to the app with the key political_ad and the set PoliticalAdTransparencyUrl as the "data" string.

====Example====
Attached is an example of a test campaign that has been marked as a political ad.
[[File:Political_Ad_Testkampagne.png|800px|thumbnail|Display of a political campaign from the web (right side of the image)]]

====Test placement====
The following keywords (separated by commas) can be set in the debug Easter egg:
<pre>iqdtests,political_ad_test</pre>
This will run an orange test ad on iqadtile1, iqadtile3 and/or iqadtile4 with the text "POLITICAL AD Test 320x320." However, this will only appear if the app transmits the keyword political_ad after evaluating consent in accordance with the instructions for political advertising.

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.

===policial_ad event===
The policial_ad event is called by iq digital's advertising templates to signal to the app that a political campaign exists on this placement and that it should respond to it (see [[#Political advertising in native apps]]).

The "data" string contains the PolticialAdTransparencyUrl, provided it has been defined in the campaign in the ad server.

====Example call:====
;<nowiki>"policial_ad","https://www.diesisteinekampagne.de/transparency.html"</nowiki>:The app should use "Politische Anzeige [https://www.diesisteinekampagne.de/transparency.html (mehr dazu)]" as the ad label for the placement, as recommended

[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Integration of the Google Mobile Ads SDK

2026-02-18T10:26:35Z

Tlohmann: /* policial_ad event */

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app or the homepage, e.g. ''politik'', ''openingpage''
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Content-Url parameter in the adrequest===
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Political advertising in native apps===
Political campaigns require consent from the user. In order for the ad server to take this into account correctly, it needs information from the app. The exact workflow works as follows:

====Workflow====
#The user decides in the CMP whether to give consent for political advertising
#The app evaluates the consent and checks whether consent has been given for political advertising
#If consent has been given, the app adds the keyword '''''political_ad''''' to the '''''kw''''' keywords for each ad request (see [[#Keywords (attachment of key-value pairs)]]).
#The ad server sees the keyword '''''political_ad''''' in the ad request and now has the option of delivering a political campaign targeted to that keyword (however, this is not mandatory; it can also deliver other campaigns).
#When an ad server plays a political campaign, a creative is delivered to the app that contains an additional setting in the template. This causes the creative to inform the app that the advertising slot in question actually contains a political campaign and that the app should respond by changing the ad label. The message is sent to the app via a political_ad event (see [[#Documentation of the iq digital app events]]).
#The app receives the '''''political_ad''''' event and can respond to it. iqdigital recommends that the ad label above the affected ad slot be changed to '''''Politische Anzeige''''' and that there be a link to the Political Ad Transparency URL for the campaign (which is passed in the event). '''Important''': The responsibility for whether and how the app responds to the '''''political_ad''''' event lies with the publisher and the app.

====App tasks (publisher tasks)====
*The app evaluates the consent string and checks whether the user has given consent for political advertising.
*If consent for political advertising has been given, the app adds the keyword '''''political_ad''''' to CustomTargeting (to key '''''kw''''').
*When the app receives a '''''political_ad''''' event through a creative, it should respond to it, for example by changing the ad label to '''''Politische Anzeige''''', as described above. If a URL is also passed as a data-String in the event, a link with the URL and the text '''''(more info)''''' should appear next to the ad label '''''Politische Anzeige'''''. Clicking on the link then opens the URL, where the user can find further information about the type of campaign.

====Tasks of the advertising template====
*A political campaign must be configured accordingly in the ad server. This is done via settings in the advertising template. This involves marking that the creative belongs to a political campaign and setting the PoliticalAdTransparencyUrl (for the "(more info)" link).
*The advertising template internally evaluates whether it is a political ad.
*In the case of a political advertisement, it sends an event to the app with the key political_ad and the set PoliticalAdTransparencyUrl as the "data" string.

====Example====
Attached is an example of a test campaign that has been marked as a political ad.
[[File:Political_Ad_Testkampagne.png|800px|thumbnail|Display of a political campaign from the web (right side of the image)]]

====Test placement====
The following keywords (separated by commas) can be set in the debug Easter egg:
<pre>iqdtests,political_ad_test</pre>
This will run an orange test ad on iqadtile1, iqadtile3 and/or iqadtile4 with the text "POLITICAL AD Test 320x320." However, this will only appear if the app transmits the keyword political_ad after evaluating consent in accordance with the instructions for political advertising.

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.

===policial_ad event===
The policial_ad event is called by iq digital's advertising templates to signal to the app that a political campaign exists on this placement and that it should respond to it (see [[#Political advertising in native apps]]).

The "data" string contains the PolticialAdTransparencyUrl, provided it has been defined in the campaign in the ad server.

====Example call:====
;<nowiki>"policial_ad","https://www.diesisteinekampagne.de/transparency.html"</nowiki>:The app should use "Politische Anzeige [https://www.diesisteinekampagne.de/transparency.html (mehr dazu)]" as the ad label for the placement, as recommended

[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Integration of the Google Mobile Ads SDK

2026-02-18T10:25:53Z

Tlohmann: /* Documentation of the iq digital app events */

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app or the homepage, e.g. ''politik'', ''openingpage''
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Content-Url parameter in the adrequest===
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Political advertising in native apps===
Political campaigns require consent from the user. In order for the ad server to take this into account correctly, it needs information from the app. The exact workflow works as follows:

====Workflow====
#The user decides in the CMP whether to give consent for political advertising
#The app evaluates the consent and checks whether consent has been given for political advertising
#If consent has been given, the app adds the keyword '''''political_ad''''' to the '''''kw''''' keywords for each ad request (see [[#Keywords (attachment of key-value pairs)]]).
#The ad server sees the keyword '''''political_ad''''' in the ad request and now has the option of delivering a political campaign targeted to that keyword (however, this is not mandatory; it can also deliver other campaigns).
#When an ad server plays a political campaign, a creative is delivered to the app that contains an additional setting in the template. This causes the creative to inform the app that the advertising slot in question actually contains a political campaign and that the app should respond by changing the ad label. The message is sent to the app via a political_ad event (see [[#Documentation of the iq digital app events]]).
#The app receives the '''''political_ad''''' event and can respond to it. iqdigital recommends that the ad label above the affected ad slot be changed to '''''Politische Anzeige''''' and that there be a link to the Political Ad Transparency URL for the campaign (which is passed in the event). '''Important''': The responsibility for whether and how the app responds to the '''''political_ad''''' event lies with the publisher and the app.

====App tasks (publisher tasks)====
*The app evaluates the consent string and checks whether the user has given consent for political advertising.
*If consent for political advertising has been given, the app adds the keyword '''''political_ad''''' to CustomTargeting (to key '''''kw''''').
*When the app receives a '''''political_ad''''' event through a creative, it should respond to it, for example by changing the ad label to '''''Politische Anzeige''''', as described above. If a URL is also passed as a data-String in the event, a link with the URL and the text '''''(more info)''''' should appear next to the ad label '''''Politische Anzeige'''''. Clicking on the link then opens the URL, where the user can find further information about the type of campaign.

====Tasks of the advertising template====
*A political campaign must be configured accordingly in the ad server. This is done via settings in the advertising template. This involves marking that the creative belongs to a political campaign and setting the PoliticalAdTransparencyUrl (for the "(more info)" link).
*The advertising template internally evaluates whether it is a political ad.
*In the case of a political advertisement, it sends an event to the app with the key political_ad and the set PoliticalAdTransparencyUrl as the "data" string.

====Example====
Attached is an example of a test campaign that has been marked as a political ad.
[[File:Political_Ad_Testkampagne.png|800px|thumbnail|Display of a political campaign from the web (right side of the image)]]

====Test placement====
The following keywords (separated by commas) can be set in the debug Easter egg:
<pre>iqdtests,political_ad_test</pre>
This will run an orange test ad on iqadtile1, iqadtile3 and/or iqadtile4 with the text "POLITICAL AD Test 320x320." However, this will only appear if the app transmits the keyword political_ad after evaluating consent in accordance with the instructions for political advertising.

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.

===policial_ad event===
The policial_ad event is called by iq digital's advertising templates to signal to the app that a political campaign exists on this placement and that it should respond to it (see #Political advertising in native apps).

The "data" string contains the PolticialAdTransparencyUrl, provided it has been defined in the campaign in the ad server.

====Example call:====
;<nowiki>"policial_ad","https://www.diesisteinekampagne.de/transparency.html"</nowiki>:The app should use "Politische Anzeige [https://www.diesisteinekampagne.de/transparency.html (mehr dazu)]" as the ad label for the placement, as recommended

[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Integration of the Google Mobile Ads SDK

2026-02-18T10:22:14Z

Tlohmann: /* App tasks (publisher tasks) */

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app or the homepage, e.g. ''politik'', ''openingpage''
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Content-Url parameter in the adrequest===
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Political advertising in native apps===
Political campaigns require consent from the user. In order for the ad server to take this into account correctly, it needs information from the app. The exact workflow works as follows:

====Workflow====
#The user decides in the CMP whether to give consent for political advertising
#The app evaluates the consent and checks whether consent has been given for political advertising
#If consent has been given, the app adds the keyword '''''political_ad''''' to the '''''kw''''' keywords for each ad request (see [[#Keywords (attachment of key-value pairs)]]).
#The ad server sees the keyword '''''political_ad''''' in the ad request and now has the option of delivering a political campaign targeted to that keyword (however, this is not mandatory; it can also deliver other campaigns).
#When an ad server plays a political campaign, a creative is delivered to the app that contains an additional setting in the template. This causes the creative to inform the app that the advertising slot in question actually contains a political campaign and that the app should respond by changing the ad label. The message is sent to the app via a political_ad event (see [[#Documentation of the iq digital app events]]).
#The app receives the '''''political_ad''''' event and can respond to it. iqdigital recommends that the ad label above the affected ad slot be changed to '''''Politische Anzeige''''' and that there be a link to the Political Ad Transparency URL for the campaign (which is passed in the event). '''Important''': The responsibility for whether and how the app responds to the '''''political_ad''''' event lies with the publisher and the app.

====App tasks (publisher tasks)====
*The app evaluates the consent string and checks whether the user has given consent for political advertising.
*If consent for political advertising has been given, the app adds the keyword '''''political_ad''''' to CustomTargeting (to key '''''kw''''').
*When the app receives a '''''political_ad''''' event through a creative, it should respond to it, for example by changing the ad label to '''''Politische Anzeige''''', as described above. If a URL is also passed as a data-String in the event, a link with the URL and the text '''''(more info)''''' should appear next to the ad label '''''Politische Anzeige'''''. Clicking on the link then opens the URL, where the user can find further information about the type of campaign.

====Tasks of the advertising template====
*A political campaign must be configured accordingly in the ad server. This is done via settings in the advertising template. This involves marking that the creative belongs to a political campaign and setting the PoliticalAdTransparencyUrl (for the "(more info)" link).
*The advertising template internally evaluates whether it is a political ad.
*In the case of a political advertisement, it sends an event to the app with the key political_ad and the set PoliticalAdTransparencyUrl as the "data" string.

====Example====
Attached is an example of a test campaign that has been marked as a political ad.
[[File:Political_Ad_Testkampagne.png|800px|thumbnail|Display of a political campaign from the web (right side of the image)]]

====Test placement====
The following keywords (separated by commas) can be set in the debug Easter egg:
<pre>iqdtests,political_ad_test</pre>
This will run an orange test ad on iqadtile1, iqadtile3 and/or iqadtile4 with the text "POLITICAL AD Test 320x320." However, this will only appear if the app transmits the keyword political_ad after evaluating consent in accordance with the instructions for political advertising.

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.
[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Integration of the Google Mobile Ads SDK

2026-02-18T10:19:40Z

Tlohmann: /* Test placement */

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app or the homepage, e.g. ''politik'', ''openingpage''
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Content-Url parameter in the adrequest===
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Political advertising in native apps===
Political campaigns require consent from the user. In order for the ad server to take this into account correctly, it needs information from the app. The exact workflow works as follows:

====Workflow====
#The user decides in the CMP whether to give consent for political advertising
#The app evaluates the consent and checks whether consent has been given for political advertising
#If consent has been given, the app adds the keyword '''''political_ad''''' to the '''''kw''''' keywords for each ad request (see [[#Keywords (attachment of key-value pairs)]]).
#The ad server sees the keyword '''''political_ad''''' in the ad request and now has the option of delivering a political campaign targeted to that keyword (however, this is not mandatory; it can also deliver other campaigns).
#When an ad server plays a political campaign, a creative is delivered to the app that contains an additional setting in the template. This causes the creative to inform the app that the advertising slot in question actually contains a political campaign and that the app should respond by changing the ad label. The message is sent to the app via a political_ad event (see [[#Documentation of the iq digital app events]]).
#The app receives the '''''political_ad''''' event and can respond to it. iqdigital recommends that the ad label above the affected ad slot be changed to '''''Politische Anzeige''''' and that there be a link to the Political Ad Transparency URL for the campaign (which is passed in the event). '''Important''': The responsibility for whether and how the app responds to the '''''political_ad''''' event lies with the publisher and the app.

====App tasks (publisher tasks)====
*The app evaluates the consent string and checks whether the user has given consent for political advertising.
*If consent for political advertising has been given, the app adds the keyword '''''political_ad''''' to CustomTargeting (to key '''''kw''''').
*When the app receives a '''''political_ad''''' event through a creative, it should respond to it, for example by changing the ad label to '''''Politische Anzeige''''', as described above. If a URL is also passed as a value in the event, a link with the URL and the text '''''(more info)''''' should appear next to the ad label '''''Politische Anzeige'''''. Clicking on the link then opens the URL, where the user can find further information about the type of campaign.

====Tasks of the advertising template====
*A political campaign must be configured accordingly in the ad server. This is done via settings in the advertising template. This involves marking that the creative belongs to a political campaign and setting the PoliticalAdTransparencyUrl (for the "(more info)" link).
*The advertising template internally evaluates whether it is a political ad.
*In the case of a political advertisement, it sends an event to the app with the key political_ad and the set PoliticalAdTransparencyUrl as the "data" string.

====Example====
Attached is an example of a test campaign that has been marked as a political ad.
[[File:Political_Ad_Testkampagne.png|800px|thumbnail|Display of a political campaign from the web (right side of the image)]]

====Test placement====
The following keywords (separated by commas) can be set in the debug Easter egg:
<pre>iqdtests,political_ad_test</pre>
This will run an orange test ad on iqadtile1, iqadtile3 and/or iqadtile4 with the text "POLITICAL AD Test 320x320." However, this will only appear if the app transmits the keyword political_ad after evaluating consent in accordance with the instructions for political advertising.

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.
[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Integration of the Google Mobile Ads SDK

2026-02-18T10:18:39Z

Tlohmann: /* App tasks (publisher tasks) */

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app or the homepage, e.g. ''politik'', ''openingpage''
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Content-Url parameter in the adrequest===
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Political advertising in native apps===
Political campaigns require consent from the user. In order for the ad server to take this into account correctly, it needs information from the app. The exact workflow works as follows:

====Workflow====
#The user decides in the CMP whether to give consent for political advertising
#The app evaluates the consent and checks whether consent has been given for political advertising
#If consent has been given, the app adds the keyword '''''political_ad''''' to the '''''kw''''' keywords for each ad request (see [[#Keywords (attachment of key-value pairs)]]).
#The ad server sees the keyword '''''political_ad''''' in the ad request and now has the option of delivering a political campaign targeted to that keyword (however, this is not mandatory; it can also deliver other campaigns).
#When an ad server plays a political campaign, a creative is delivered to the app that contains an additional setting in the template. This causes the creative to inform the app that the advertising slot in question actually contains a political campaign and that the app should respond by changing the ad label. The message is sent to the app via a political_ad event (see [[#Documentation of the iq digital app events]]).
#The app receives the '''''political_ad''''' event and can respond to it. iqdigital recommends that the ad label above the affected ad slot be changed to '''''Politische Anzeige''''' and that there be a link to the Political Ad Transparency URL for the campaign (which is passed in the event). '''Important''': The responsibility for whether and how the app responds to the '''''political_ad''''' event lies with the publisher and the app.

====App tasks (publisher tasks)====
*The app evaluates the consent string and checks whether the user has given consent for political advertising.
*If consent for political advertising has been given, the app adds the keyword '''''political_ad''''' to CustomTargeting (to key '''''kw''''').
*When the app receives a '''''political_ad''''' event through a creative, it should respond to it, for example by changing the ad label to '''''Politische Anzeige''''', as described above. If a URL is also passed as a value in the event, a link with the URL and the text '''''(more info)''''' should appear next to the ad label '''''Politische Anzeige'''''. Clicking on the link then opens the URL, where the user can find further information about the type of campaign.

====Tasks of the advertising template====
*A political campaign must be configured accordingly in the ad server. This is done via settings in the advertising template. This involves marking that the creative belongs to a political campaign and setting the PoliticalAdTransparencyUrl (for the "(more info)" link).
*The advertising template internally evaluates whether it is a political ad.
*In the case of a political advertisement, it sends an event to the app with the key political_ad and the set PoliticalAdTransparencyUrl as the "data" string.

====Example====
Attached is an example of a test campaign that has been marked as a political ad.
[[File:Political_Ad_Testkampagne.png|800px|thumbnail|Display of a political campaign from the web (right side of the image)]]

====Test placement====
The following keywords (separated by commas) can be set in the debug Easter egg:

This will run an orange test ad on iqadtile1, iqadtile3 and/or iqadtile4 with the text "POLITICAL AD Test 320x320." However, this will only appear if the app transmits the keyword political_ad after evaluating consent in accordance with the instructions for political advertising.

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.
[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Integration of the Google Mobile Ads SDK

2026-02-18T10:18:16Z

Tlohmann: /* Political advertising in native apps */

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app or the homepage, e.g. ''politik'', ''openingpage''
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Content-Url parameter in the adrequest===
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Political advertising in native apps===
Political campaigns require consent from the user. In order for the ad server to take this into account correctly, it needs information from the app. The exact workflow works as follows:

====Workflow====
#The user decides in the CMP whether to give consent for political advertising
#The app evaluates the consent and checks whether consent has been given for political advertising
#If consent has been given, the app adds the keyword '''''political_ad''''' to the '''''kw''''' keywords for each ad request (see [[#Keywords (attachment of key-value pairs)]]).
#The ad server sees the keyword '''''political_ad''''' in the ad request and now has the option of delivering a political campaign targeted to that keyword (however, this is not mandatory; it can also deliver other campaigns).
#When an ad server plays a political campaign, a creative is delivered to the app that contains an additional setting in the template. This causes the creative to inform the app that the advertising slot in question actually contains a political campaign and that the app should respond by changing the ad label. The message is sent to the app via a political_ad event (see [[#Documentation of the iq digital app events]]).
#The app receives the '''''political_ad''''' event and can respond to it. iqdigital recommends that the ad label above the affected ad slot be changed to '''''Politische Anzeige''''' and that there be a link to the Political Ad Transparency URL for the campaign (which is passed in the event). '''Important''': The responsibility for whether and how the app responds to the '''''political_ad''''' event lies with the publisher and the app.

====App tasks (publisher tasks)====
*The app evaluates the consent string and checks whether the user has given consent for political advertising.
*If consent for political advertising has been given, the app adds the keyword '''''political_ad''''' to CustomTargeting (to key '''''kw''''').
*When the app receives a '''''political_ad''''' event through a creative, it should respond to it, for example by changing the ad label to '''''Politische Anzeige''''', as described above. If a URL is also passed as a value in the event, a link with the URL and the text '''''(more info)" should appear next to the ad label '''''Politische Anzeige'''''. Clicking on the link then opens the URL, where the user can find further information about the type of campaign.

====Tasks of the advertising template====
*A political campaign must be configured accordingly in the ad server. This is done via settings in the advertising template. This involves marking that the creative belongs to a political campaign and setting the PoliticalAdTransparencyUrl (for the "(more info)" link).
*The advertising template internally evaluates whether it is a political ad.
*In the case of a political advertisement, it sends an event to the app with the key political_ad and the set PoliticalAdTransparencyUrl as the "data" string.

====Example====
Attached is an example of a test campaign that has been marked as a political ad.
[[File:Political_Ad_Testkampagne.png|800px|thumbnail|Display of a political campaign from the web (right side of the image)]]

====Test placement====
The following keywords (separated by commas) can be set in the debug Easter egg:

This will run an orange test ad on iqadtile1, iqadtile3 and/or iqadtile4 with the text "POLITICAL AD Test 320x320." However, this will only appear if the app transmits the keyword political_ad after evaluating consent in accordance with the instructions for political advertising.

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.
[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Integration of the Google Mobile Ads SDK

2026-02-18T10:17:42Z

Tlohmann: /* Political advertising in native apps */

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app or the homepage, e.g. ''politik'', ''openingpage''
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Content-Url parameter in the adrequest===
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Political advertising in native apps===
Political campaigns require consent from the user. In order for the ad server to take this into account correctly, it needs information from the app. The exact workflow works as follows:

====Workflow====
#The user decides in the CMP whether to give consent for political advertising
#The app evaluates the consent and checks whether consent has been given for political advertising
#If consent has been given, the app adds the keyword '''''political_ad''''' to the '''''kw''''' keywords for each ad request (see #[[Keywords (attachment of key-value pairs)]]).
#The ad server sees the keyword '''''political_ad''''' in the ad request and now has the option of delivering a political campaign targeted to that keyword (however, this is not mandatory; it can also deliver other campaigns).
#When an ad server plays a political campaign, a creative is delivered to the app that contains an additional setting in the template. This causes the creative to inform the app that the advertising slot in question actually contains a political campaign and that the app should respond by changing the ad label. The message is sent to the app via a political_ad event (see [[#Documentation of the iq digital app events]]).
#The app receives the '''''political_ad''''' event and can respond to it. iqdigital recommends that the ad label above the affected ad slot be changed to '''''Politische Anzeige''''' and that there be a link to the Political Ad Transparency URL for the campaign (which is passed in the event). '''Important''': The responsibility for whether and how the app responds to the '''''political_ad''''' event lies with the publisher and the app.

====App tasks (publisher tasks)====
*The app evaluates the consent string and checks whether the user has given consent for political advertising.
*If consent for political advertising has been given, the app adds the keyword '''''political_ad''''' to CustomTargeting (to key '''''kw''''').
*When the app receives a '''''political_ad''''' event through a creative, it should respond to it, for example by changing the ad label to '''''Politische Anzeige''''', as described above. If a URL is also passed as a value in the event, a link with the URL and the text '''''(more info)" should appear next to the ad label '''''Politische Anzeige'''''. Clicking on the link then opens the URL, where the user can find further information about the type of campaign.

====Tasks of the advertising template====
*A political campaign must be configured accordingly in the ad server. This is done via settings in the advertising template. This involves marking that the creative belongs to a political campaign and setting the PoliticalAdTransparencyUrl (for the "(more info)" link).
*The advertising template internally evaluates whether it is a political ad.
*In the case of a political advertisement, it sends an event to the app with the key political_ad and the set PoliticalAdTransparencyUrl as the "data" string.

====Example====
Attached is an example of a test campaign that has been marked as a political ad.
[[File:Political_Ad_Testkampagne.png|800px|thumbnail|Display of a political campaign from the web (right side of the image)]]

====Test placement====
The following keywords (separated by commas) can be set in the debug Easter egg:

This will run an orange test ad on iqadtile1, iqadtile3 and/or iqadtile4 with the text "POLITICAL AD Test 320x320." However, this will only appear if the app transmits the keyword political_ad after evaluating consent in accordance with the instructions for political advertising.

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.
[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Integration of the Google Mobile Ads SDK

2026-02-18T10:16:50Z

Tlohmann:

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app or the homepage, e.g. ''politik'', ''openingpage''
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Content-Url parameter in the adrequest===
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Political advertising in native apps===
Political campaigns require consent from the user. In order for the ad server to take this into account correctly, it needs information from the app. The exact workflow works as follows:

====Workflow====
#The user decides in the CMP whether to give consent for political advertising
#The app evaluates the consent and checks whether consent has been given for political advertising
#If consent has been given, the app adds the keyword '''''political_ad''''' to the '''''kw''''' keywords for each ad request (see #Keywords (Appending Key-Value Pairs)).
#The ad server sees the keyword '''''political_ad''''' in the ad request and now has the option of delivering a political campaign targeted to that keyword (however, this is not mandatory; it can also deliver other campaigns).
#When an ad server plays a political campaign, a creative is delivered to the app that contains an additional setting in the template. This causes the creative to inform the app that the advertising slot in question actually contains a political campaign and that the app should respond by changing the ad label. The message is sent to the app via a political_ad event (see [[#Documentation of the iq digital app events]]).
#The app receives the '''''political_ad''''' event and can respond to it. iqdigital recommends that the ad label above the affected ad slot be changed to '''''Politische Anzeige''''' and that there be a link to the Political Ad Transparency URL for the campaign (which is passed in the event). '''Important''': The responsibility for whether and how the app responds to the '''''political_ad''''' event lies with the publisher and the app.

====App tasks (publisher tasks)====
*The app evaluates the consent string and checks whether the user has given consent for political advertising.
*If consent for political advertising has been given, the app adds the keyword '''''political_ad''''' to CustomTargeting (to key '''''kw''''').
*When the app receives a '''''political_ad''''' event through a creative, it should respond to it, for example by changing the ad label to '''''Politische Anzeige''''', as described above. If a URL is also passed as a value in the event, a link with the URL and the text '''''(more info)" should appear next to the ad label '''''Politische Anzeige'''''. Clicking on the link then opens the URL, where the user can find further information about the type of campaign.

====Tasks of the advertising template====
*A political campaign must be configured accordingly in the ad server. This is done via settings in the advertising template. This involves marking that the creative belongs to a political campaign and setting the PoliticalAdTransparencyUrl (for the "(more info)" link).
*The advertising template internally evaluates whether it is a political ad.
*In the case of a political advertisement, it sends an event to the app with the key political_ad and the set PoliticalAdTransparencyUrl as the "data" string.

====Example====
Attached is an example of a test campaign that has been marked as a political ad.
[[File:Political_Ad_Testkampagne.png|800px|thumbnail|Display of a political campaign from the web (right side of the image)]]

====Test placement====
The following keywords (separated by commas) can be set in the debug Easter egg:

This will run an orange test ad on iqadtile1, iqadtile3 and/or iqadtile4 with the text "POLITICAL AD Test 320x320." However, this will only appear if the app transmits the keyword political_ad after evaluating consent in accordance with the instructions for political advertising.

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.
[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Integration of the Google Mobile Ads SDK

2026-02-18T10:16:19Z

Tlohmann: /* Political advertising in native apps */

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app or the homepage, e.g. ''politik'', ''openingpage''
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Content-Url parameter in the adrequest===
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Political advertising in native apps===
Political campaigns require consent from the user. In order for the ad server to take this into account correctly, it needs information from the app. The exact workflow works as follows:

====Workflow====
#The user decides in the CMP whether to give consent for political advertising
#The app evaluates the consent and checks whether consent has been given for political advertising
#If consent has been given, the app adds the keyword '''''political_ad''''' to the '''''kw''''' keywords for each ad request (see #Keywords (Appending Key-Value Pairs)).
#The ad server sees the keyword '''''political_ad''''' in the ad request and now has the option of delivering a political campaign targeted to that keyword (however, this is not mandatory; it can also deliver other campaigns).
#When an ad server plays a political campaign, a creative is delivered to the app that contains an additional setting in the template. This causes the creative to inform the app that the advertising slot in question actually contains a political campaign and that the app should respond by changing the ad label. The message is sent to the app via a political_ad event (see [[#Documentation of the iq digital app events]]).
#The app receives the '''''political_ad''''' event and can respond to it. iqdigital recommends that the ad label above the affected ad slot be changed to '''''Politische Anzeige''''' and that there be a link to the Political Ad Transparency URL for the campaign (which is passed in the event). '''Important''': The responsibility for whether and how the app responds to the '''''political_ad''''' event lies with the publisher and the app.

===App tasks (publisher tasks)===
*The app evaluates the consent string and checks whether the user has given consent for political advertising.
*If consent for political advertising has been given, the app adds the keyword '''''political_ad''''' to CustomTargeting (to key '''''kw''''').
*When the app receives a '''''political_ad''''' event through a creative, it should respond to it, for example by changing the ad label to '''''Politische Anzeige''''', as described above. If a URL is also passed as a value in the event, a link with the URL and the text '''''(more info)" should appear next to the ad label '''''Politische Anzeige'''''. Clicking on the link then opens the URL, where the user can find further information about the type of campaign.

===Tasks of the advertising template===
*A political campaign must be configured accordingly in the ad server. This is done via settings in the advertising template. This involves marking that the creative belongs to a political campaign and setting the PoliticalAdTransparencyUrl (for the "(more info)" link).
*The advertising template internally evaluates whether it is a political ad.
*In the case of a political advertisement, it sends an event to the app with the key political_ad and the set PoliticalAdTransparencyUrl as the "data" string.

====Example====
Attached is an example of a test campaign that has been marked as a political ad.
[[File:Political_Ad_Testkampagne.png|800px|thumbnail|Display of a political campaign from the web (right side of the image)]]

====Test placement====
The following keywords (separated by commas) can be set in the debug Easter egg:

This will run an orange test ad on iqadtile1, iqadtile3 and/or iqadtile4 with the text "POLITICAL AD Test 320x320." However, this will only appear if the app transmits the keyword political_ad after evaluating consent in accordance with the instructions for political advertising.

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.
[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Integration of the Google Mobile Ads SDK

2026-02-18T10:15:31Z

Tlohmann:

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app or the homepage, e.g. ''politik'', ''openingpage''
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Content-Url parameter in the adrequest===
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Political advertising in native apps===
Political campaigns require consent from the user. In order for the ad server to take this into account correctly, it needs information from the app. The exact workflow works as follows:

====Workflow====
#The user decides in the CMP whether to give consent for political advertising
#The app evaluates the consent and checks whether consent has been given for political advertising
#If consent has been given, the app adds the keyword '''''political_ad''''' to the '''''kw''''' keywords for each ad request (see #Keywords (Appending Key-Value Pairs)).
#The ad server sees the keyword '''''political_ad''''' in the ad request and now has the option of delivering a political campaign targeted to that keyword (however, this is not mandatory; it can also deliver other campaigns).
#When an ad server plays a political campaign, a creative is delivered to the app that contains an additional setting in the template. This causes the creative to inform the app that the advertising slot in question actually contains a political campaign and that the app should respond by changing the ad label. The message is sent to the app via a political_ad event (see [[#Documentation of iq digital app events]]).
#The app receives the '''''political_ad''''' event and can respond to it. iqdigital recommends that the ad label above the affected ad slot be changed to '''''Politische Anzeige''''' and that there be a link to the Political Ad Transparency URL for the campaign (which is passed in the event). '''Important''': The responsibility for whether and how the app responds to the '''''political_ad''''' event lies with the publisher and the app.

===App tasks (publisher tasks)===
*The app evaluates the consent string and checks whether the user has given consent for political advertising.
*If consent for political advertising has been given, the app adds the keyword '''''political_ad''''' to CustomTargeting (to key '''''kw''''').
*When the app receives a '''''political_ad''''' event through a creative, it should respond to it, for example by changing the ad label to '''''Politische Anzeige''''', as described above. If a URL is also passed as a value in the event, a link with the URL and the text '''''(more info)" should appear next to the ad label '''''Politische Anzeige'''''. Clicking on the link then opens the URL, where the user can find further information about the type of campaign.

===Tasks of the advertising template===
*A political campaign must be configured accordingly in the ad server. This is done via settings in the advertising template. This involves marking that the creative belongs to a political campaign and setting the PoliticalAdTransparencyUrl (for the "(more info)" link).
*The advertising template internally evaluates whether it is a political ad.
*In the case of a political advertisement, it sends an event to the app with the key political_ad and the set PoliticalAdTransparencyUrl as the "data" string.

====Example====
Attached is an example of a test campaign that has been marked as a political ad.
[[File:Political_Ad_Testkampagne.png|800px|thumbnail|Display of a political campaign from the web (right side of the image)]]

====Test placement====
The following keywords (separated by commas) can be set in the debug Easter egg:

This will run an orange test ad on iqadtile1, iqadtile3 and/or iqadtile4 with the text "POLITICAL AD Test 320x320." However, this will only appear if the app transmits the keyword political_ad after evaluating consent in accordance with the instructions for political advertising.

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.
[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Prebid Mobile SDK in Apps

2026-02-11T13:21:01Z

Tlohmann: /* Step 3 - Create BannerAdUnits per placement */

==Introduction==
The Prebid Mobile SDK is used to integrate various HeaderBidding providers into an app, which then bid on the available ad placements during initial page load. The winning bid is then passed to the Google Mobile Ads SDK (GMA SDK) to the ad server, which compares the bid with other bookings available there and delivers the most appropriate booking.

Note: The implementation guide uses code snippets for Android as examples and assumes that the Google Mobile Ads SDK is already integrated into the app.
Basic documentation of Prebid Mobile can be found here:
*General overview: https://docs.prebid.org/prebid-mobile/prebid-mobile.html
*iOS: https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html
*Android: https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html

===Required documents===
*This documentation
*Excel sheet with account ID and config IDs for each iqadtile

==Step 1 - Integrate Prebid Mobile SDK==
*iOS: https://github.com/prebid/prebid-mobile-ios
*Android: https://github.com/prebid/prebid-mobile-android

==Step 2 - Initial global configuration==
At the beginning, the endpoint and account ID must be set in the SDK and placed in an initialization method

*Prebid Server Account ID: '''<<<PREBID_SERVER_ACCOUNT_ID>>>''', the ID is different for each app, but is the same for all placements within the app. The ID can be found in the Excel sheet.
*Prebid Server Url: '''https://client-pbs.relevant-digital.com/openrtb2/auction'''

===Example===
<pre>
PrebidMobile.setPrebidServerAccountId("<<<PREBID_SERVER_ACCOUNT_ID>>>")

PrebidMobile.setCustomStatusEndpoint("https://client-pbs.relevant-digital.com/s
tatus")

PrebidMobile.initializeSdk(
applicationContext,
"https://client-pbs.relevant-digital.com/openrtb2/auction") { status ->
if (status == InitializationStatus.SUCCEEDED) {
Log.d(TAG, "SDK initialized successfully!")
} else {
Log.e(TAG, "SDK initialization error: $status\\
${status.description}")
}
}
)
</pre>

==Step 3 - Create BannerAdUnits per placement==
For each ad placement (iqadtile), a BannerAdUnit must be created and configured:

#'''Config Id''', this is different for each iqadtile within an app and is provided in the Excel sheet by iqdigital.
#The sizes that have been defined for the iqadtile must also be communicated to the BannerAdUnit. (Important: normally more than one size must be passed, they often differ from iqadtile to iqadtile)

==Step 4 - Global configurations for BannerAdUnits==
These apply equally to all BannerAdUnits

===OMID===
OMID tells the Headerbidding partners which OpenMeasurement SDK is being used. The GMA SDK has the OpenMeasurementSDK built in, which is why the IDs for Google must be specified here:

====iOS:====
*OmidPartnerVersion: '''afma-sdk-i-v12.11.0'''
*OmidPartnerName: '''Google'''

====Android:====
*OmidPartnerVersion: '''253830000.253830000'''
*OmidPartnerName: '''Google'''

====Example:====
<pre>
TargetingParams.setOmidPartnerVersion("253830000.253830000");
TargetingParams.setOmidPartnerName("Google");
</pre>

===Banner API===
The Headerbidding partners must be informed which APIs are available. In the case of the GMA SDK, the following values are valid:

MRAID 1 to 3, OMID 1

====Example:====
<pre>
val parameters = BannerParameters()
parameters.api = listOf(Signals.Api.MRAID_3, Signals.Api.OMID_1,
Signals.Api.MRAID_2, Signals.Api.MRAID_1)
adUnit?.bannerParameters = parameters
</pre>

===Display Manager===
The Headerbidding partners should be informed which DisplayManager and which version is being used.

====Example:====
<pre>
TargetingParams.setGlobalOrtbConfig(
"""
{
"displaymanager": "Google",
"displaymanagerver": "${MobileAds.getVersion()}",
"ext": {
"myext": {
"test": 1
}
}
}
""".trimIndent()
)
</pre>

==Step 5 - iqadtile/page-specific configurations for BannerAdUnits==
These differ depending on the iqadtile or page.

===GPID===
The GPID is there to tell certain Headerbidding partners which placement they are bidding on and is therefore very important. The absence of this information leads to worse bids!

*'''gpid''' corresponds to the AdUnit used for the iqadtile, e.g. /183/FAZ_app_android_phone/homepage
*'''pbadslot''' is a combination of AdUnit, the character '#' and the iqadtile, example /183/FAZ_app_android_phone/homepage#iqadtile3
*'''relevant_slotInstance''' is the number of the iqadtile, example 3 for iqadtile3

====Example====
<pre>
adUnit?.impOrtbConfig = """
{
"ext": {
"gpid":"/183/FAZ_app_android_phone/homepage"
"data": {
"pbadslot":"/183/FAZ_app_android_phone/homepage#iqadtile3"
"relevant_slotInstance": "3" // optional extra to RY analytics
}
}
}
""".trimIndent()
</pre>

==Appendix: How Prebid Mobile SDK and GMA SDK work==
[[Datei:Prebid SDK.png|800px]]
#The Prebid Mobile SDK sends a request to Prebid Server
#Prebid Server returns a bid if available
#The ad request to Google Ad Manager is supplemented with the Prebid parameters
#Google Ad Manager checks the request and delivers advertising
#The app displays the advertising

Important note: An ad request with the GMA SDK always occurs, even if the Prebid Mobile SDK has no bids. Prebid bids supplement the ad request, but they are not a necessary condition.

==Important Links==
*[https://docs.prebid.org/prebid-mobile/prebid-mobile.html Getting Started]
*[https://docs.prebid.org/prebid-server/use-cases/pbs-sdk.html#prebid-sdk-calls-prebid-server Prebid SDK Workflow]

===iOS===
*[https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html Code Integration]

===Android===
*[https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html Code Integration]
[[de:Prebid Mobile SDK in Apps]]

Prebid Mobile SDK in Apps

2026-02-11T13:20:18Z

Tlohmann: /* Step 2 - Initial global configuration */

==Introduction==
The Prebid Mobile SDK is used to integrate various HeaderBidding providers into an app, which then bid on the available ad placements during initial page load. The winning bid is then passed to the Google Mobile Ads SDK (GMA SDK) to the ad server, which compares the bid with other bookings available there and delivers the most appropriate booking.

Note: The implementation guide uses code snippets for Android as examples and assumes that the Google Mobile Ads SDK is already integrated into the app.
Basic documentation of Prebid Mobile can be found here:
*General overview: https://docs.prebid.org/prebid-mobile/prebid-mobile.html
*iOS: https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html
*Android: https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html

===Required documents===
*This documentation
*Excel sheet with account ID and config IDs for each iqadtile

==Step 1 - Integrate Prebid Mobile SDK==
*iOS: https://github.com/prebid/prebid-mobile-ios
*Android: https://github.com/prebid/prebid-mobile-android

==Step 2 - Initial global configuration==
At the beginning, the endpoint and account ID must be set in the SDK and placed in an initialization method

*Prebid Server Account ID: '''<<<PREBID_SERVER_ACCOUNT_ID>>>''', the ID is different for each app, but is the same for all placements within the app. The ID can be found in the Excel sheet.
*Prebid Server Url: '''https://client-pbs.relevant-digital.com/openrtb2/auction'''

===Example===
<pre>
PrebidMobile.setPrebidServerAccountId("<<<PREBID_SERVER_ACCOUNT_ID>>>")

PrebidMobile.setCustomStatusEndpoint("https://client-pbs.relevant-digital.com/s
tatus")

PrebidMobile.initializeSdk(
applicationContext,
"https://client-pbs.relevant-digital.com/openrtb2/auction") { status ->
if (status == InitializationStatus.SUCCEEDED) {
Log.d(TAG, "SDK initialized successfully!")
} else {
Log.e(TAG, "SDK initialization error: $status\\
${status.description}")
}
}
)
</pre>

==Step 3 - Create BannerAdUnits per placement==
For each ad placement (iqadtile), a BannerAdUnit must be created and configured:

#'''Config Id''', this is different for each iqadtile and will be provided in a table by iqdigital
#The sizes that have been defined for the iqadtile must also be communicated to the BannerAdUnit. (Important: normally more than one size must be passed, they often differ from iqadtile to iqadtile)

==Step 4 - Global configurations for BannerAdUnits==
These apply equally to all BannerAdUnits

===OMID===
OMID tells the Headerbidding partners which OpenMeasurement SDK is being used. The GMA SDK has the OpenMeasurementSDK built in, which is why the IDs for Google must be specified here:

====iOS:====
*OmidPartnerVersion: '''afma-sdk-i-v12.11.0'''
*OmidPartnerName: '''Google'''

====Android:====
*OmidPartnerVersion: '''253830000.253830000'''
*OmidPartnerName: '''Google'''

====Example:====
<pre>
TargetingParams.setOmidPartnerVersion("253830000.253830000");
TargetingParams.setOmidPartnerName("Google");
</pre>

===Banner API===
The Headerbidding partners must be informed which APIs are available. In the case of the GMA SDK, the following values are valid:

MRAID 1 to 3, OMID 1

====Example:====
<pre>
val parameters = BannerParameters()
parameters.api = listOf(Signals.Api.MRAID_3, Signals.Api.OMID_1,
Signals.Api.MRAID_2, Signals.Api.MRAID_1)
adUnit?.bannerParameters = parameters
</pre>

===Display Manager===
The Headerbidding partners should be informed which DisplayManager and which version is being used.

====Example:====
<pre>
TargetingParams.setGlobalOrtbConfig(
"""
{
"displaymanager": "Google",
"displaymanagerver": "${MobileAds.getVersion()}",
"ext": {
"myext": {
"test": 1
}
}
}
""".trimIndent()
)
</pre>

==Step 5 - iqadtile/page-specific configurations for BannerAdUnits==
These differ depending on the iqadtile or page.

===GPID===
The GPID is there to tell certain Headerbidding partners which placement they are bidding on and is therefore very important. The absence of this information leads to worse bids!

*'''gpid''' corresponds to the AdUnit used for the iqadtile, e.g. /183/FAZ_app_android_phone/homepage
*'''pbadslot''' is a combination of AdUnit, the character '#' and the iqadtile, example /183/FAZ_app_android_phone/homepage#iqadtile3
*'''relevant_slotInstance''' is the number of the iqadtile, example 3 for iqadtile3

====Example====
<pre>
adUnit?.impOrtbConfig = """
{
"ext": {
"gpid":"/183/FAZ_app_android_phone/homepage"
"data": {
"pbadslot":"/183/FAZ_app_android_phone/homepage#iqadtile3"
"relevant_slotInstance": "3" // optional extra to RY analytics
}
}
}
""".trimIndent()
</pre>

==Appendix: How Prebid Mobile SDK and GMA SDK work==
[[Datei:Prebid SDK.png|800px]]
#The Prebid Mobile SDK sends a request to Prebid Server
#Prebid Server returns a bid if available
#The ad request to Google Ad Manager is supplemented with the Prebid parameters
#Google Ad Manager checks the request and delivers advertising
#The app displays the advertising

Important note: An ad request with the GMA SDK always occurs, even if the Prebid Mobile SDK has no bids. Prebid bids supplement the ad request, but they are not a necessary condition.

==Important Links==
*[https://docs.prebid.org/prebid-mobile/prebid-mobile.html Getting Started]
*[https://docs.prebid.org/prebid-server/use-cases/pbs-sdk.html#prebid-sdk-calls-prebid-server Prebid SDK Workflow]

===iOS===
*[https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html Code Integration]

===Android===
*[https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html Code Integration]
[[de:Prebid Mobile SDK in Apps]]

Prebid Mobile SDK in Apps

2026-02-11T13:20:06Z

Tlohmann: /* Step 2 - Initial global configuration */

==Introduction==
The Prebid Mobile SDK is used to integrate various HeaderBidding providers into an app, which then bid on the available ad placements during initial page load. The winning bid is then passed to the Google Mobile Ads SDK (GMA SDK) to the ad server, which compares the bid with other bookings available there and delivers the most appropriate booking.

Note: The implementation guide uses code snippets for Android as examples and assumes that the Google Mobile Ads SDK is already integrated into the app.
Basic documentation of Prebid Mobile can be found here:
*General overview: https://docs.prebid.org/prebid-mobile/prebid-mobile.html
*iOS: https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html
*Android: https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html

===Required documents===
*This documentation
*Excel sheet with account ID and config IDs for each iqadtile

==Step 1 - Integrate Prebid Mobile SDK==
*iOS: https://github.com/prebid/prebid-mobile-ios
*Android: https://github.com/prebid/prebid-mobile-android

==Step 2 - Initial global configuration==
At the beginning, the endpoint and account ID must be set in the SDK and placed in an initialization method

*Prebid Server Account ID: '''<<<PREBID_SERVER_ACCOUNT_ID>>>''', tThe ID is different for each app, but is the same for all placements within the app. The ID can be found in the Excel sheet.
*Prebid Server Url: '''https://client-pbs.relevant-digital.com/openrtb2/auction'''

===Example===
<pre>
PrebidMobile.setPrebidServerAccountId("<<<PREBID_SERVER_ACCOUNT_ID>>>")

PrebidMobile.setCustomStatusEndpoint("https://client-pbs.relevant-digital.com/s
tatus")

PrebidMobile.initializeSdk(
applicationContext,
"https://client-pbs.relevant-digital.com/openrtb2/auction") { status ->
if (status == InitializationStatus.SUCCEEDED) {
Log.d(TAG, "SDK initialized successfully!")
} else {
Log.e(TAG, "SDK initialization error: $status\\
${status.description}")
}
}
)
</pre>

==Step 3 - Create BannerAdUnits per placement==
For each ad placement (iqadtile), a BannerAdUnit must be created and configured:

#'''Config Id''', this is different for each iqadtile and will be provided in a table by iqdigital
#The sizes that have been defined for the iqadtile must also be communicated to the BannerAdUnit. (Important: normally more than one size must be passed, they often differ from iqadtile to iqadtile)

==Step 4 - Global configurations for BannerAdUnits==
These apply equally to all BannerAdUnits

===OMID===
OMID tells the Headerbidding partners which OpenMeasurement SDK is being used. The GMA SDK has the OpenMeasurementSDK built in, which is why the IDs for Google must be specified here:

====iOS:====
*OmidPartnerVersion: '''afma-sdk-i-v12.11.0'''
*OmidPartnerName: '''Google'''

====Android:====
*OmidPartnerVersion: '''253830000.253830000'''
*OmidPartnerName: '''Google'''

====Example:====
<pre>
TargetingParams.setOmidPartnerVersion("253830000.253830000");
TargetingParams.setOmidPartnerName("Google");
</pre>

===Banner API===
The Headerbidding partners must be informed which APIs are available. In the case of the GMA SDK, the following values are valid:

MRAID 1 to 3, OMID 1

====Example:====
<pre>
val parameters = BannerParameters()
parameters.api = listOf(Signals.Api.MRAID_3, Signals.Api.OMID_1,
Signals.Api.MRAID_2, Signals.Api.MRAID_1)
adUnit?.bannerParameters = parameters
</pre>

===Display Manager===
The Headerbidding partners should be informed which DisplayManager and which version is being used.

====Example:====
<pre>
TargetingParams.setGlobalOrtbConfig(
"""
{
"displaymanager": "Google",
"displaymanagerver": "${MobileAds.getVersion()}",
"ext": {
"myext": {
"test": 1
}
}
}
""".trimIndent()
)
</pre>

==Step 5 - iqadtile/page-specific configurations for BannerAdUnits==
These differ depending on the iqadtile or page.

===GPID===
The GPID is there to tell certain Headerbidding partners which placement they are bidding on and is therefore very important. The absence of this information leads to worse bids!

*'''gpid''' corresponds to the AdUnit used for the iqadtile, e.g. /183/FAZ_app_android_phone/homepage
*'''pbadslot''' is a combination of AdUnit, the character '#' and the iqadtile, example /183/FAZ_app_android_phone/homepage#iqadtile3
*'''relevant_slotInstance''' is the number of the iqadtile, example 3 for iqadtile3

====Example====
<pre>
adUnit?.impOrtbConfig = """
{
"ext": {
"gpid":"/183/FAZ_app_android_phone/homepage"
"data": {
"pbadslot":"/183/FAZ_app_android_phone/homepage#iqadtile3"
"relevant_slotInstance": "3" // optional extra to RY analytics
}
}
}
""".trimIndent()
</pre>

==Appendix: How Prebid Mobile SDK and GMA SDK work==
[[Datei:Prebid SDK.png|800px]]
#The Prebid Mobile SDK sends a request to Prebid Server
#Prebid Server returns a bid if available
#The ad request to Google Ad Manager is supplemented with the Prebid parameters
#Google Ad Manager checks the request and delivers advertising
#The app displays the advertising

Important note: An ad request with the GMA SDK always occurs, even if the Prebid Mobile SDK has no bids. Prebid bids supplement the ad request, but they are not a necessary condition.

==Important Links==
*[https://docs.prebid.org/prebid-mobile/prebid-mobile.html Getting Started]
*[https://docs.prebid.org/prebid-server/use-cases/pbs-sdk.html#prebid-sdk-calls-prebid-server Prebid SDK Workflow]

===iOS===
*[https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html Code Integration]

===Android===
*[https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html Code Integration]
[[de:Prebid Mobile SDK in Apps]]

Prebid Mobile SDK in Apps

2026-02-11T13:19:44Z

Tlohmann: /* Step 2 - Initial global configuration */

==Introduction==
The Prebid Mobile SDK is used to integrate various HeaderBidding providers into an app, which then bid on the available ad placements during initial page load. The winning bid is then passed to the Google Mobile Ads SDK (GMA SDK) to the ad server, which compares the bid with other bookings available there and delivers the most appropriate booking.

Note: The implementation guide uses code snippets for Android as examples and assumes that the Google Mobile Ads SDK is already integrated into the app.
Basic documentation of Prebid Mobile can be found here:
*General overview: https://docs.prebid.org/prebid-mobile/prebid-mobile.html
*iOS: https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html
*Android: https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html

===Required documents===
*This documentation
*Excel sheet with account ID and config IDs for each iqadtile

==Step 1 - Integrate Prebid Mobile SDK==
*iOS: https://github.com/prebid/prebid-mobile-ios
*Android: https://github.com/prebid/prebid-mobile-android

==Step 2 - Initial global configuration==
At the beginning, the endpoint and account ID must be set in the SDK and placed in an initialization method

*Prebid Server Account ID: '''<<<PREBID_SERVER_ACCOUNT_ID>>>'''. The ID is different for each app, but is the same for all placements within the app. The ID can be found in the Excel sheet.*Prebid Server Url: '''https://client-pbs.relevant-digital.com/openrtb2/auction'''

===Example===
<pre>
PrebidMobile.setPrebidServerAccountId("<<<PREBID_SERVER_ACCOUNT_ID>>>")

PrebidMobile.setCustomStatusEndpoint("https://client-pbs.relevant-digital.com/s
tatus")

PrebidMobile.initializeSdk(
applicationContext,
"https://client-pbs.relevant-digital.com/openrtb2/auction") { status ->
if (status == InitializationStatus.SUCCEEDED) {
Log.d(TAG, "SDK initialized successfully!")
} else {
Log.e(TAG, "SDK initialization error: $status\\
${status.description}")
}
}
)
</pre>

==Step 3 - Create BannerAdUnits per placement==
For each ad placement (iqadtile), a BannerAdUnit must be created and configured:

#'''Config Id''', this is different for each iqadtile and will be provided in a table by iqdigital
#The sizes that have been defined for the iqadtile must also be communicated to the BannerAdUnit. (Important: normally more than one size must be passed, they often differ from iqadtile to iqadtile)

==Step 4 - Global configurations for BannerAdUnits==
These apply equally to all BannerAdUnits

===OMID===
OMID tells the Headerbidding partners which OpenMeasurement SDK is being used. The GMA SDK has the OpenMeasurementSDK built in, which is why the IDs for Google must be specified here:

====iOS:====
*OmidPartnerVersion: '''afma-sdk-i-v12.11.0'''
*OmidPartnerName: '''Google'''

====Android:====
*OmidPartnerVersion: '''253830000.253830000'''
*OmidPartnerName: '''Google'''

====Example:====
<pre>
TargetingParams.setOmidPartnerVersion("253830000.253830000");
TargetingParams.setOmidPartnerName("Google");
</pre>

===Banner API===
The Headerbidding partners must be informed which APIs are available. In the case of the GMA SDK, the following values are valid:

MRAID 1 to 3, OMID 1

====Example:====
<pre>
val parameters = BannerParameters()
parameters.api = listOf(Signals.Api.MRAID_3, Signals.Api.OMID_1,
Signals.Api.MRAID_2, Signals.Api.MRAID_1)
adUnit?.bannerParameters = parameters
</pre>

===Display Manager===
The Headerbidding partners should be informed which DisplayManager and which version is being used.

====Example:====
<pre>
TargetingParams.setGlobalOrtbConfig(
"""
{
"displaymanager": "Google",
"displaymanagerver": "${MobileAds.getVersion()}",
"ext": {
"myext": {
"test": 1
}
}
}
""".trimIndent()
)
</pre>

==Step 5 - iqadtile/page-specific configurations for BannerAdUnits==
These differ depending on the iqadtile or page.

===GPID===
The GPID is there to tell certain Headerbidding partners which placement they are bidding on and is therefore very important. The absence of this information leads to worse bids!

*'''gpid''' corresponds to the AdUnit used for the iqadtile, e.g. /183/FAZ_app_android_phone/homepage
*'''pbadslot''' is a combination of AdUnit, the character '#' and the iqadtile, example /183/FAZ_app_android_phone/homepage#iqadtile3
*'''relevant_slotInstance''' is the number of the iqadtile, example 3 for iqadtile3

====Example====
<pre>
adUnit?.impOrtbConfig = """
{
"ext": {
"gpid":"/183/FAZ_app_android_phone/homepage"
"data": {
"pbadslot":"/183/FAZ_app_android_phone/homepage#iqadtile3"
"relevant_slotInstance": "3" // optional extra to RY analytics
}
}
}
""".trimIndent()
</pre>

==Appendix: How Prebid Mobile SDK and GMA SDK work==
[[Datei:Prebid SDK.png|800px]]
#The Prebid Mobile SDK sends a request to Prebid Server
#Prebid Server returns a bid if available
#The ad request to Google Ad Manager is supplemented with the Prebid parameters
#Google Ad Manager checks the request and delivers advertising
#The app displays the advertising

Important note: An ad request with the GMA SDK always occurs, even if the Prebid Mobile SDK has no bids. Prebid bids supplement the ad request, but they are not a necessary condition.

==Important Links==
*[https://docs.prebid.org/prebid-mobile/prebid-mobile.html Getting Started]
*[https://docs.prebid.org/prebid-server/use-cases/pbs-sdk.html#prebid-sdk-calls-prebid-server Prebid SDK Workflow]

===iOS===
*[https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html Code Integration]

===Android===
*[https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html Code Integration]
[[de:Prebid Mobile SDK in Apps]]

Prebid Mobile SDK in Apps

2026-02-11T13:18:52Z

Tlohmann: /* Introduction */

==Introduction==
The Prebid Mobile SDK is used to integrate various HeaderBidding providers into an app, which then bid on the available ad placements during initial page load. The winning bid is then passed to the Google Mobile Ads SDK (GMA SDK) to the ad server, which compares the bid with other bookings available there and delivers the most appropriate booking.

Note: The implementation guide uses code snippets for Android as examples and assumes that the Google Mobile Ads SDK is already integrated into the app.
Basic documentation of Prebid Mobile can be found here:
*General overview: https://docs.prebid.org/prebid-mobile/prebid-mobile.html
*iOS: https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html
*Android: https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html

===Required documents===
*This documentation
*Excel sheet with account ID and config IDs for each iqadtile

==Step 1 - Integrate Prebid Mobile SDK==
*iOS: https://github.com/prebid/prebid-mobile-ios
*Android: https://github.com/prebid/prebid-mobile-android

==Step 2 - Initial global configuration==
At the beginning, the endpoint and account ID must be set in the SDK and placed in an initialization method

*Prebid Server Account Id: '''<<<PREBID_SERVER_ACCOUNT_ID>>>'''
*Prebid Server Url: '''https://client-pbs.relevant-digital.com/openrtb2/auction'''

===Example===
<pre>
PrebidMobile.setPrebidServerAccountId("<<<PREBID_SERVER_ACCOUNT_ID>>>")

PrebidMobile.setCustomStatusEndpoint("https://client-pbs.relevant-digital.com/s
tatus")

PrebidMobile.initializeSdk(
applicationContext,
"https://client-pbs.relevant-digital.com/openrtb2/auction") { status ->
if (status == InitializationStatus.SUCCEEDED) {
Log.d(TAG, "SDK initialized successfully!")
} else {
Log.e(TAG, "SDK initialization error: $status\\
${status.description}")
}
}
)
</pre>

==Step 3 - Create BannerAdUnits per placement==
For each ad placement (iqadtile), a BannerAdUnit must be created and configured:

#'''Config Id''', this is different for each iqadtile and will be provided in a table by iqdigital
#The sizes that have been defined for the iqadtile must also be communicated to the BannerAdUnit. (Important: normally more than one size must be passed, they often differ from iqadtile to iqadtile)

==Step 4 - Global configurations for BannerAdUnits==
These apply equally to all BannerAdUnits

===OMID===
OMID tells the Headerbidding partners which OpenMeasurement SDK is being used. The GMA SDK has the OpenMeasurementSDK built in, which is why the IDs for Google must be specified here:

====iOS:====
*OmidPartnerVersion: '''afma-sdk-i-v12.11.0'''
*OmidPartnerName: '''Google'''

====Android:====
*OmidPartnerVersion: '''253830000.253830000'''
*OmidPartnerName: '''Google'''

====Example:====
<pre>
TargetingParams.setOmidPartnerVersion("253830000.253830000");
TargetingParams.setOmidPartnerName("Google");
</pre>

===Banner API===
The Headerbidding partners must be informed which APIs are available. In the case of the GMA SDK, the following values are valid:

MRAID 1 to 3, OMID 1

====Example:====
<pre>
val parameters = BannerParameters()
parameters.api = listOf(Signals.Api.MRAID_3, Signals.Api.OMID_1,
Signals.Api.MRAID_2, Signals.Api.MRAID_1)
adUnit?.bannerParameters = parameters
</pre>

===Display Manager===
The Headerbidding partners should be informed which DisplayManager and which version is being used.

====Example:====
<pre>
TargetingParams.setGlobalOrtbConfig(
"""
{
"displaymanager": "Google",
"displaymanagerver": "${MobileAds.getVersion()}",
"ext": {
"myext": {
"test": 1
}
}
}
""".trimIndent()
)
</pre>

==Step 5 - iqadtile/page-specific configurations for BannerAdUnits==
These differ depending on the iqadtile or page.

===GPID===
The GPID is there to tell certain Headerbidding partners which placement they are bidding on and is therefore very important. The absence of this information leads to worse bids!

*'''gpid''' corresponds to the AdUnit used for the iqadtile, e.g. /183/FAZ_app_android_phone/homepage
*'''pbadslot''' is a combination of AdUnit, the character '#' and the iqadtile, example /183/FAZ_app_android_phone/homepage#iqadtile3
*'''relevant_slotInstance''' is the number of the iqadtile, example 3 for iqadtile3

====Example====
<pre>
adUnit?.impOrtbConfig = """
{
"ext": {
"gpid":"/183/FAZ_app_android_phone/homepage"
"data": {
"pbadslot":"/183/FAZ_app_android_phone/homepage#iqadtile3"
"relevant_slotInstance": "3" // optional extra to RY analytics
}
}
}
""".trimIndent()
</pre>

==Appendix: How Prebid Mobile SDK and GMA SDK work==
[[Datei:Prebid SDK.png|800px]]
#The Prebid Mobile SDK sends a request to Prebid Server
#Prebid Server returns a bid if available
#The ad request to Google Ad Manager is supplemented with the Prebid parameters
#Google Ad Manager checks the request and delivers advertising
#The app displays the advertising

Important note: An ad request with the GMA SDK always occurs, even if the Prebid Mobile SDK has no bids. Prebid bids supplement the ad request, but they are not a necessary condition.

==Important Links==
*[https://docs.prebid.org/prebid-mobile/prebid-mobile.html Getting Started]
*[https://docs.prebid.org/prebid-server/use-cases/pbs-sdk.html#prebid-sdk-calls-prebid-server Prebid SDK Workflow]

===iOS===
*[https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html Code Integration]

===Android===
*[https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html Code Integration]
[[de:Prebid Mobile SDK in Apps]]

Prebid Mobile SDK in Apps

2026-02-06T08:14:55Z

Tlohmann: /* GPID */

==Introduction==
The Prebid Mobile SDK is used to integrate various HeaderBidding providers into an app, which then bid on the available ad placements during initial page load. The winning bid is then passed to the Google Mobile Ads SDK (GMA SDK) to the ad server, which compares the bid with other bookings available there and delivers the most appropriate booking.

Note: The implementation guide uses code snippets for Android as examples and assumes that the Google Mobile Ads SDK is already integrated into the app.
Basic documentation of Prebid Mobile can be found here:
*General overview: https://docs.prebid.org/prebid-mobile/prebid-mobile.html
*iOS: https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html
*Android: https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html

==Step 1 - Integrate Prebid Mobile SDK==
*iOS: https://github.com/prebid/prebid-mobile-ios
*Android: https://github.com/prebid/prebid-mobile-android

==Step 2 - Initial global configuration==
At the beginning, the endpoint and account ID must be set in the SDK and placed in an initialization method

*Prebid Server Account Id: '''<<<PREBID_SERVER_ACCOUNT_ID>>>'''
*Prebid Server Url: '''https://client-pbs.relevant-digital.com/openrtb2/auction'''

===Example===
<pre>
PrebidMobile.setPrebidServerAccountId("<<<PREBID_SERVER_ACCOUNT_ID>>>")

PrebidMobile.setCustomStatusEndpoint("https://client-pbs.relevant-digital.com/s
tatus")

PrebidMobile.initializeSdk(
applicationContext,
"https://client-pbs.relevant-digital.com/openrtb2/auction") { status ->
if (status == InitializationStatus.SUCCEEDED) {
Log.d(TAG, "SDK initialized successfully!")
} else {
Log.e(TAG, "SDK initialization error: $status\\
${status.description}")
}
}
)
</pre>

==Step 3 - Create BannerAdUnits per placement==
For each ad placement (iqadtile), a BannerAdUnit must be created and configured:

#'''Config Id''', this is different for each iqadtile and will be provided in a table by iqdigital
#The sizes that have been defined for the iqadtile must also be communicated to the BannerAdUnit. (Important: normally more than one size must be passed, they often differ from iqadtile to iqadtile)

==Step 4 - Global configurations for BannerAdUnits==
These apply equally to all BannerAdUnits

===OMID===
OMID tells the Headerbidding partners which OpenMeasurement SDK is being used. The GMA SDK has the OpenMeasurementSDK built in, which is why the IDs for Google must be specified here:

====iOS:====
*OmidPartnerVersion: '''afma-sdk-i-v12.11.0'''
*OmidPartnerName: '''Google'''

====Android:====
*OmidPartnerVersion: '''253830000.253830000'''
*OmidPartnerName: '''Google'''

====Example:====
<pre>
TargetingParams.setOmidPartnerVersion("253830000.253830000");
TargetingParams.setOmidPartnerName("Google");
</pre>

===Banner API===
The Headerbidding partners must be informed which APIs are available. In the case of the GMA SDK, the following values are valid:

MRAID 1 to 3, OMID 1

====Example:====
<pre>
val parameters = BannerParameters()
parameters.api = listOf(Signals.Api.MRAID_3, Signals.Api.OMID_1,
Signals.Api.MRAID_2, Signals.Api.MRAID_1)
adUnit?.bannerParameters = parameters
</pre>

===Display Manager===
The Headerbidding partners should be informed which DisplayManager and which version is being used.

====Example:====
<pre>
TargetingParams.setGlobalOrtbConfig(
"""
{
"displaymanager": "Google",
"displaymanagerver": "${MobileAds.getVersion()}",
"ext": {
"myext": {
"test": 1
}
}
}
""".trimIndent()
)
</pre>

==Step 5 - iqadtile/page-specific configurations for BannerAdUnits==
These differ depending on the iqadtile or page.

===GPID===
The GPID is there to tell certain Headerbidding partners which placement they are bidding on and is therefore very important. The absence of this information leads to worse bids!

*'''gpid''' corresponds to the AdUnit used for the iqadtile, e.g. /183/FAZ_app_android_phone/homepage
*'''pbadslot''' is a combination of AdUnit, the character '#' and the iqadtile, example /183/FAZ_app_android_phone/homepage#iqadtile3
*'''relevant_slotInstance''' is the number of the iqadtile, example 3 for iqadtile3

====Example====
<pre>
adUnit?.impOrtbConfig = """
{
"ext": {
"gpid":"/183/FAZ_app_android_phone/homepage"
"data": {
"pbadslot":"/183/FAZ_app_android_phone/homepage#iqadtile3"
"relevant_slotInstance": "3" // optional extra to RY analytics
}
}
}
""".trimIndent()
</pre>

==Appendix: How Prebid Mobile SDK and GMA SDK work==
[[Datei:Prebid SDK.png|800px]]
#The Prebid Mobile SDK sends a request to Prebid Server
#Prebid Server returns a bid if available
#The ad request to Google Ad Manager is supplemented with the Prebid parameters
#Google Ad Manager checks the request and delivers advertising
#The app displays the advertising

Important note: An ad request with the GMA SDK always occurs, even if the Prebid Mobile SDK has no bids. Prebid bids supplement the ad request, but they are not a necessary condition.

==Important Links==
*[https://docs.prebid.org/prebid-mobile/prebid-mobile.html Getting Started]
*[https://docs.prebid.org/prebid-server/use-cases/pbs-sdk.html#prebid-sdk-calls-prebid-server Prebid SDK Workflow]

===iOS===
*[https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html Code Integration]

===Android===
*[https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html Code Integration]
[[de:Prebid Mobile SDK in Apps]]

Prebid Mobile SDK in Apps

2026-01-30T10:33:53Z

Tlohmann:

==Introduction==
The Prebid Mobile SDK is used to integrate various HeaderBidding providers into an app, which then bid on the available ad placements during initial page load. The winning bid is then passed to the Google Mobile Ads SDK (GMA SDK) to the ad server, which compares the bid with other bookings available there and delivers the most appropriate booking.

Note: The implementation guide uses code snippets for Android as examples and assumes that the Google Mobile Ads SDK is already integrated into the app.
Basic documentation of Prebid Mobile can be found here:
*General overview: https://docs.prebid.org/prebid-mobile/prebid-mobile.html
*iOS: https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html
*Android: https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html

==Step 1 - Integrate Prebid Mobile SDK==
*iOS: https://github.com/prebid/prebid-mobile-ios
*Android: https://github.com/prebid/prebid-mobile-android

==Step 2 - Initial global configuration==
At the beginning, the endpoint and account ID must be set in the SDK and placed in an initialization method

*Prebid Server Account Id: '''<<<PREBID_SERVER_ACCOUNT_ID>>>'''
*Prebid Server Url: '''https://client-pbs.relevant-digital.com/openrtb2/auction'''

===Example===
<pre>
PrebidMobile.setPrebidServerAccountId("<<<PREBID_SERVER_ACCOUNT_ID>>>")

PrebidMobile.setCustomStatusEndpoint("https://client-pbs.relevant-digital.com/s
tatus")

PrebidMobile.initializeSdk(
applicationContext,
"https://client-pbs.relevant-digital.com/openrtb2/auction") { status ->
if (status == InitializationStatus.SUCCEEDED) {
Log.d(TAG, "SDK initialized successfully!")
} else {
Log.e(TAG, "SDK initialization error: $status\\
${status.description}")
}
}
)
</pre>

==Step 3 - Create BannerAdUnits per placement==
For each ad placement (iqadtile), a BannerAdUnit must be created and configured:

#'''Config Id''', this is different for each iqadtile and will be provided in a table by iqdigital
#The sizes that have been defined for the iqadtile must also be communicated to the BannerAdUnit. (Important: normally more than one size must be passed, they often differ from iqadtile to iqadtile)

==Step 4 - Global configurations for BannerAdUnits==
These apply equally to all BannerAdUnits

===OMID===
OMID tells the Headerbidding partners which OpenMeasurement SDK is being used. The GMA SDK has the OpenMeasurementSDK built in, which is why the IDs for Google must be specified here:

====iOS:====
*OmidPartnerVersion: '''afma-sdk-i-v12.11.0'''
*OmidPartnerName: '''Google'''

====Android:====
*OmidPartnerVersion: '''253830000.253830000'''
*OmidPartnerName: '''Google'''

====Example:====
<pre>
TargetingParams.setOmidPartnerVersion("253830000.253830000");
TargetingParams.setOmidPartnerName("Google");
</pre>

===Banner API===
The Headerbidding partners must be informed which APIs are available. In the case of the GMA SDK, the following values are valid:

MRAID 1 to 3, OMID 1

====Example:====
<pre>
val parameters = BannerParameters()
parameters.api = listOf(Signals.Api.MRAID_3, Signals.Api.OMID_1,
Signals.Api.MRAID_2, Signals.Api.MRAID_1)
adUnit?.bannerParameters = parameters
</pre>

===Display Manager===
The Headerbidding partners should be informed which DisplayManager and which version is being used.

====Example:====
<pre>
TargetingParams.setGlobalOrtbConfig(
"""
{
"displaymanager": "Google",
"displaymanagerver": "${MobileAds.getVersion()}",
"ext": {
"myext": {
"test": 1
}
}
}
""".trimIndent()
)
</pre>

==Step 5 - iqadtile/page-specific configurations for BannerAdUnits==
These differ depending on the iqadtile or page.

===GPID===
The GPID is there to tell certain Headerbidding partners which placement they are bidding on and is therefore very important. The absence of this information leads to worse bids!

*'''gpid''' corresponds to the AdUnit used for the iqadtile, e.g. /183/FAZ_app_android_phone/homepage
*'''pbadslot''' is a combination of AdUnit and iqadtile, example /183/FAZ_app_android_phone/homepage#iqadtile3
*'''relevant_slotInstance''' is the number of the iqadtile, example 3 for iqadtile3

====Example====
<pre>
adUnit?.impOrtbConfig = """
{
"ext": {
"gpid":"/183/FAZ_app_android_phone/homepage"
"data": {
"pbadslot":"/183/FAZ_app_android_phone/homepage#iqadtile3"
"relevant_slotInstance": "3" // optional extra to RY analytics
}
}
}
""".trimIndent()
</pre>

==Appendix: How Prebid Mobile SDK and GMA SDK work==
[[Datei:Prebid SDK.png|800px]]
#The Prebid Mobile SDK sends a request to Prebid Server
#Prebid Server returns a bid if available
#The ad request to Google Ad Manager is supplemented with the Prebid parameters
#Google Ad Manager checks the request and delivers advertising
#The app displays the advertising

Important note: An ad request with the GMA SDK always occurs, even if the Prebid Mobile SDK has no bids. Prebid bids supplement the ad request, but they are not a necessary condition.

==Important Links==
*[https://docs.prebid.org/prebid-mobile/prebid-mobile.html Getting Started]
*[https://docs.prebid.org/prebid-server/use-cases/pbs-sdk.html#prebid-sdk-calls-prebid-server Prebid SDK Workflow]

===iOS===
*[https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html Code Integration]

===Android===
*[https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html Code Integration]
[[de:Prebid Mobile SDK in Apps]]

Main Page

2025-05-26T14:52:14Z

Tlohmann:

__NOTOC__
<div class="mainpage">
<div class="mainheader">
<div class="title">'''iq digital media marketing gmbh'''<br />Documentation</div>
</div>
<div class="chapter">
{{:Ad Technology}}
</div>
</div>
[[de:Hauptseite]]

Integration of the Google Mobile Ads SDK

2025-05-26T14:51:57Z

Tlohmann:

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app or the homepage, e.g. ''politik'', ''openingpage''
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Content-Url parameter in the adrequest===
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.
[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Integration of the Google Mobile Ads SDK

2025-05-26T14:51:44Z

Tlohmann:

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app or the homepage, e.g. ''politik'', ''openingpage''
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Content-Url parameter in the adrequest===
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.
[[Kategorie:Ad Technology]][[Kategorie:APP]][[Kategorie:TEST]]
[[de:Einbau des Google Mobile Ads SDK]]

Main Page

2025-05-22T12:11:33Z

Tlohmann:

__NOTOC__
<div style="border:2px solid #ff6600;background-color:#fff7e6;width:300px;padding:10px;margin-bottom:20px;"><h2>Maintenance work on 05/26/2025</h2><p>In the period from 4-8pm it may be that the website is not available.</p></div>
<div class="mainpage">
<div class="mainheader">
<div class="title">'''iq digital media marketing gmbh'''<br />Documentation</div>
</div>
<div class="chapter">
{{:Ad Technology}}
</div>
</div>
[[de:Hauptseite]]

Integration of the Google Mobile Ads SDK

2025-04-25T06:33:59Z

Tlohmann:

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app or the homepage, e.g. ''politik'', ''openingpage''
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Content-Url parameter in the adrequest===
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.
[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Integration of the Google Mobile Ads SDK

2023-09-20T13:41:36Z

Tlohmann: /* Content-Url parameter in the adrequest */

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app, e.g. politik (politics)
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are openingpage, swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Content-Url parameter in the adrequest===
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.
[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Integration of the Google Mobile Ads SDK

2023-09-20T13:41:19Z

Tlohmann:

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app, e.g. politik (politics)
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are openingpage, swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

==Content-Url parameter in the adrequest==
In order for programmatic partners (e.g. Adexchange, Headerbidding or Backfill) to bid as high as possible for an ad placement, this app ad placement must be told which stationary website it actually belongs to. This is done via the content-url parameter in the adrequest. The URL of the web page that matches the content in the app as closely as possible must be passed here as the value. Example: An app article should link to its stationary web article in the content-url parameter, an app home page to the home page, etc. The GMA SDK has a setContentUrl function for this purpose. This is described in more detail here:
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting?hl=de#content_url
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting?hl=de#content_url

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.
[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Prebid Mobile SDK in Apps

2023-07-28T07:49:50Z

Tlohmann:

==Introduction==
The Prebid Mobile SDK serves to integrate different header bidding providers in one app, and these providers can then make initial bids for the available ad positions on a page when the page is called. The winning bid is then forwarded via the Google Mobile Ads SDK to the ad server, which compares the bid with other bookings that are present there and serves the most suitable booking.

==Integration and mode of operation==
[[Datei:Prebid SDK.png|800px]]
#Integrate the Prebid Mobile SDK
::iOS: https://github.com/prebid/prebid-mobile-ios
::Android: https://github.com/prebid/prebid-mobile-android
#Create the banner ad unit with all sizes and additional sizes that are to be included in the prebid request (the PREBID_SERVER_CONFIGURATION_ID is taken from a separate table and assigned to the corresponding position (Note for Ad Technology iq digital: The PREBID_SERVER_CONFIGURATION_ID of a placement is the "Targeting ID" in Prebid Server Premioum by Xandr)).
#The Prebid Mobile SDK sends a request to the prebid server.
#The prebid server sends back an offer (if present).
#The ad request to Google Ad Manager is supplemented by the prebid parameters.
#Google Ad Manager reviews the request and serves the ad.
#The app displays the ad.

===Android example===
The example on the page shows that man wohl einen DFP PublisherAdView (??) and then generates the prebid banner ad unit. This is then given the prebid server request ID assigned to the banner ad unit and defines a size. Additional sizes are transmitted to the object using the add additional size method. Here, all the sizes should be transmitted that are also normally part of the ad request for the position.

The bids are then connected using fetchDemand. The result codes are defined here: http://prebid.org/prebid-mobile/pbm- api/android/pbm-api-result-codes-android.html
In general, however, an ad request should always occur, regardless of whether bids are contained or not.

==Important configurations==
In our case, the Prebid Mobile SDK works together with Prebid Server Premium and therefore needs a few adjustments:

===Set Host===
Prebid Server Premium must be configured as a custom host. This is done in Android like this:
<pre>
Host custom = Host.CUSTOM;
custom.setHostUrl("https://ib.adnxs.com/openrtb2/prebid");
PrebidMobile.setPrebidServerHost(custom);
</pre>
[https://docs.prebid.org/prebid-mobile/pbm-api/android/prebidmobile-object-android.html#sethost Anleitung Android Custom Host]<br />
[https://docs.prebid.org/prebid-mobile/pbm-api/ios/prebidmobile-object-ios.html Anleitung iOS Custom Host]

===Set Account ID===
Our account ID must also be set.
<pre>PrebidMobile.setPrebidServerAccountId("6975");</pre>

==Important Links==
*[https://docs.prebid.org/prebid-mobile/prebid-mobile.html Getting Started]
*[https://docs.prebid.org/prebid-mobile/prebid-mobile-pbs.html#developers---using-the-sdk Developers using the SDK]
*[https://docs.prebid.org/prebid-mobile/privacy-regulation.html Privacy Regulation]
*[https://docs.prebid.org/prebid-server/use-cases/pbs-sdk.html#prebid-sdk-calls-prebid-server Prebid SDK Workflow]

===iOS===
*[https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html Code Integration]
*[https://docs.prebid.org/prebid-mobile/pbm-api/ios/pbm-banneradunit-ios.html Banner Adunit]

===Android===
*[https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html Code Integration]
*[https://docs.prebid.org/prebid-mobile/pbm-api/android/pbm-banneradunit-android.html Banner Adunit]
[[de:Prebid Mobile SDK in Apps]]

MediaWiki:Mobile.css

2022-12-08T08:44:38Z

Tlohmann:

/* Das folgende CSS wird für alle Nutzer der mobilen Ansicht geladen. */

.mainheader {
background-color: #a2a9b1;
color:#FFFFFF;
text-align:left;
font-size:25px;
width:100%;
padding-left:5px;
height:120px;
padding-top:30px;
}

.mainheader .title {
height:30px;
line-height:30px;
}

.bold {
font-weight:bold;
}

@font-face {
font-family: 'Rajdhani';
font-style: normal;
font-weight: 300;
src: url('/de/resources/assets/fonts/rajdhani-v7-latin-300.eot');
src: local('Rajdhani Light'), local('Rajdhani-Light'), url('/de/resources/assets/fonts/rajdhani-v7-latin-300.eot?#iefix') format('embedded-opentype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-300.woff2') format('woff2'), url('/de/resources/assets/fonts/rajdhani-v7-latin-300.woff') format('woff'), url('/de/resources/assets/fonts/rajdhani-v7-latin-300.ttf') format('truetype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-300.svg#Rajdhani') format('svg')
}

@font-face {
font-family: 'Rajdhani';
font-style: normal;
font-weight: 400;
src: url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.eot');
src: local('Rajdhani Regular'), local('Rajdhani-Regular'), url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.eot?#iefix') format('embedded-opentype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.woff2') format('woff2'), url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.woff') format('woff'), url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.ttf') format('truetype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.svg#Rajdhani') format('svg')
}

@font-face {
font-family: 'Rajdhani';
font-style: normal;
font-weight: 500;
src: url('/de/resources/assets/fonts/rajdhani-v7-latin-500.eot');
src: local('Rajdhani Medium'), local('Rajdhani-Medium'), url('/de/resources/assets/fonts/rajdhani-v7-latin-500.eot?#iefix') format('embedded-opentype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-500.woff2') format('woff2'), url('/de/resources/assets/fonts/rajdhani-v7-latin-500.woff') format('woff'), url('/de/resources/assets/fonts/rajdhani-v7-latin-500.ttf') format('truetype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-500.svg#Rajdhani') format('svg')
}

@font-face {
font-family: 'Rajdhani';
font-style: normal;
font-weight: 600;
src: url('/de/resources/assets/fonts/rajdhani-v7-latin-600.eot');
src: local('Rajdhani SemiBold'), local('Rajdhani-SemiBold'), url('/de/resources/assets/fonts/rajdhani-v7-latin-600.eot?#iefix') format('embedded-opentype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-600.woff2') format('woff2'), url('/de/resources/assets/fonts/rajdhani-v7-latin-600.woff') format('woff'), url('/de/resources/assets/fonts/rajdhani-v7-latin-600.ttf') format('truetype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-600.svg#Rajdhani') format('svg')
}

@font-face {
font-family: 'Rajdhani';
font-style: normal;
font-weight: 700;
src: url('/de/resources/assets/fonts/rajdhani-v7-latin-700.eot');
src: local('Rajdhani Bold'), local('Rajdhani-Bold'), url('/de/resources/assets/fonts/rajdhani-v7-latin-700.eot?#iefix') format('embedded-opentype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-700.woff2') format('woff2'), url('/de/resources/assets/fonts/rajdhani-v7-latin-700.woff') format('woff'), url('/de/resources/assets/fonts/rajdhani-v7-latin-700.ttf') format('truetype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-700.svg#Rajdhani') format('svg')
}

* {
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
font-size: 100%;
}

.pre-content h1, .content h1, .content h2, .content h3, .mw-body h1, .mw-body-content h1, .mw-body-content h2, .mw-body-content h3 {
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
font-weight:bold;
}
.content h3, .mw-body-content h3 {
text-decoration:underline;
}

p, p *, li, li * {
font-family: Arial,Tahoma,Verdana;
}
.branding-box a span {
background-image: url(/de/resources/assets/iq-digital.png?53da3);
background-repeat: no-repeat;
background-size: 100px auto;
background-position: left center;
padding-left:100px;
height:32px;
float:none;
}

.header .branding-box {
width:90%;
}

.minerva-header .branding-box a > * {
float: none;
}

.header {
white-space:normal;
}

a {
color:#ee7f00;
}

a:visited {
color:#ee7f00;
}

.specsBox {
position:relative;
width:320px;
margin: 16px auto 16px auto;
box-sizing:border-box;
}

.specsBox *{
box-sizing:border-box;
}

.specsBox .container{
width:320px;
padding:1em;
background-color:#ffeecc;
-webkit-border-radius: 5px;
-moz-border-radius: 5px;
border-radius: 5px;
}

.specsBox .infos {
border-top: 1px solid black;
padding-top:16px;
}

.specsBox span {
display:inline-block;
vertical-align:top;
}
.specsBox .key {
width:33%;
text-align:left;
font-weight:bold;
}

.specsBox .value {
width:66%;
text-align:left;
}

.specsBox .name {
font-weight:bold;
}

.specsBox h3 {
margin: 0 auto;
}

.content .specsBox ul {
padding-left:0;
}

.anlieferungselement {
width:320px;
background-color: #fff1e6;
border-radius: 5px;
margin-right:5px;
margin-bottom: 10px;
padding-bottom:5px;
font-size:14px;
}

.anlieferungselement *{
box-sizing: border-box;
}

.anlieferungselement:last-of-type {
margin-bottom:0;
}

.anlieferungselement .titel{
font-weight:bold;
font-size:120%;
text-align:center;
border-bottom: 2px solid #ffad66;
background-color: #ffe4cc;
padding: 5px 5px 0 5px;
border-top-left-radius:5px;
border-top-right-radius:5px;
}

.anlieferungselement .abmessung, .anlieferungselement .gewicht, .anlieferungselement .format, .anlieferungselement .alternative, .anlieferungselement .anmerkung, .anlieferungselement .abmessungExpandiert, .anlieferungselement .mandanten, .anlieferungselement .dauer, .anlieferungselement .seitenverhaeltnis{
padding-left: 5px;
padding-right: 5px;
}

.anlieferungselement .bezeichnung{
width:33%;
font-weight:bold;
padding-right:5px;
display:inline-block;
vertical-align:top;
}
.anlieferungselement .wert{
width:67%;
display:inline-block;
}
.anlieferung_kombination {
display:flex;
}

.anlieferung_kombination.horizontal {
align-content:center;
flex-direction:row;
border: 2px solid #ffad66;
flex-wrap:wrap;
justify-content:center;
}

.anlieferung_kombination.vertikal{
justify-content: center;
flex-direction:column;
align-content:center;
}

.anlieferung_kombination > .container > .anlieferung_kombination.vertikal{

}

.anlieferung_kombination > .container > .anlieferung_kombination.horizontal{
flex:initial;
}

.anlieferung_kombination.horizontal > .anlieferungselement {
flex:none;
margin: 5px;
}

.anlieferung_kombination.horizontal > .zeichen{
flex:none;
}

.anlieferung_kombination > .zeichen{
font-weight: bold;
font-size: 200%;
width: 100px;
text-align: center;
vertical-align:middle;
}

.anlieferung_kombination.vertikal > .zeichen{
font-size:300%;
line-height:80px;
height:80px;
width:320px;
align-self:center;
}

.anlieferung_kombination.vertikal .header {
background-color: #ffe4cc;
width: 100%;
text-align: center;
border: 2px solid #ffad66;
border-bottom: none;
box-sizing: border-box;
}

.anlieferung_kombination .header .bezeichnung{
font-size:200%;
font-weight:bold;
}
.anlieferung_kombination .header .text {
font-size:150%;
}

.galerie {
margin-top:1em;
margin-bottom:1em;
text-align: center;
}

.specsBox .galerie .gallery {
margin:0;
padding:0;
}

.mainpage {
display:flex;
flex-wrap:wrap;
justify-content:center;
min-width:320px;
box-sizing: border-box;
}

.mainpage * {
box-sizing: border-box;
}

.chapter {
width:320px;
min-width:320px;
margin-right:16px;
}

@media screen and (max-width: 352px) {
.mainpage, .specsBox {
margin-left:-16px;
margin-right:-16px;
}
.chapter {
width:320px;
min-width:320px;
margin-right:0;
}

.mainheader {
padding-top:15px;
}
}

@media screen and (max-width: 370px) {
.mainheader {
padding-top:15px;
}
}

@media screen and (min-width: 720px) {
.mainpage {
margin-left:-3.35em;
margin-right:-3.35em;
}

.mainheader .title{
text-align:left;
}
}

@media screen and (max-width: 672px) {
.chapter {
margin-right:0;
}

.mainheader .title{
text-align:left;
}
}

.kontakt{
margin: 15px 20px 5px 0;
width:250px;
}

.kontakt_name{
font-weight: 700;
font-size:16px;
}

.kontakt_funktion{
border-bottom: 1px solid black;
font-size:16px;
}

.included .specsBox .infos .anlieferung{
display:none;
}
.included .specsBox .infos.text{
padding-top:0;
}

div.warnung::after {
clear:both;
}

div.warnung::before {
content: "Warnung";
background:url(/de/images/c/cb/Warning.png) no-repeat;
background-position:center;
background-size:24px auto;
width:24px;
height:24px;
line-height:24px;
display:inline-block;
color:rgba(0,0,0,0);
float:left;
margin-right:10px;
}

div.warnung {
font-weight:bold;
font-size:120%;
color:#ff0000;
float:left;
}

.chapterlist {
width:320px;
border: 0.5px solid #a2a9b1;
background-color: #f8f9fa;
color: #222;
margin: 1em auto;
border-collapse: collapse;
font-size:16px;
}

.chapterlist .clheader {
font-size:22px;
background-color:#525050;
color:#FFF;
padding: 0.2em 0.4em;
font-weight:bold;
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
}

.chapterlist ul {
margin:0;
padding:0;
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
}

.chapterlist li {
list-style-type: none;
list-style-image: none;
padding: 0.2em 0.4em;
margin:0;
font-weight:bold;
border-bottom: 0.5px solid #a2a9b1;
line-height:1.6;
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
font-size:100%;
}
.chapterlist li *{
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
}

MediaWiki:Common.css

2022-12-08T07:49:57Z

Tlohmann:

/* Das folgende CSS wird für alle Benutzeroberflächen geladen. */

.bold {
font-weight:bold;
}

div#p-logo::after {
content: "Dokumentation";
font-weight: bold;
color:#ef7f00;
margin-top:-30px;
margin-left:1.1em;
}

@font-face {
font-family: 'Rajdhani';
font-style: normal;
font-weight: 300;
src: url('/de/resources/assets/fonts/rajdhani-v7-latin-300.eot');
src: local('Rajdhani Light'), local('Rajdhani-Light'), url('/de/resources/assets/fonts/rajdhani-v7-latin-300.eot?#iefix') format('embedded-opentype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-300.woff2') format('woff2'), url('/de/resources/assets/fonts/rajdhani-v7-latin-300.woff') format('woff'), url('/de/resources/assets/fonts/rajdhani-v7-latin-300.ttf') format('truetype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-300.svg#Rajdhani') format('svg')
}

@font-face {
font-family: 'Rajdhani';
font-style: normal;
font-weight: 400;
src: url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.eot');
src: local('Rajdhani Regular'), local('Rajdhani-Regular'), url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.eot?#iefix') format('embedded-opentype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.woff2') format('woff2'), url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.woff') format('woff'), url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.ttf') format('truetype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.svg#Rajdhani') format('svg')
}

@font-face {
font-family: 'Rajdhani';
font-style: normal;
font-weight: 500;
src: url('/de/resources/assets/fonts/rajdhani-v7-latin-500.eot');
src: local('Rajdhani Medium'), local('Rajdhani-Medium'), url('/de/resources/assets/fonts/rajdhani-v7-latin-500.eot?#iefix') format('embedded-opentype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-500.woff2') format('woff2'), url('/de/resources/assets/fonts/rajdhani-v7-latin-500.woff') format('woff'), url('/de/resources/assets/fonts/rajdhani-v7-latin-500.ttf') format('truetype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-500.svg#Rajdhani') format('svg')
}

@font-face {
font-family: 'Rajdhani';
font-style: normal;
font-weight: 600;
src: url('/de/resources/assets/fonts/rajdhani-v7-latin-600.eot');
src: local('Rajdhani SemiBold'), local('Rajdhani-SemiBold'), url('/de/resources/assets/fonts/rajdhani-v7-latin-600.eot?#iefix') format('embedded-opentype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-600.woff2') format('woff2'), url('/de/resources/assets/fonts/rajdhani-v7-latin-600.woff') format('woff'), url('/de/resources/assets/fonts/rajdhani-v7-latin-600.ttf') format('truetype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-600.svg#Rajdhani') format('svg')
}

@font-face {
font-family: 'Rajdhani';
font-style: normal;
font-weight: 700;
src: url('/de/resources/assets/fonts/rajdhani-v7-latin-700.eot');
src: local('Rajdhani Bold'), local('Rajdhani-Bold'), url('/de/resources/assets/fonts/rajdhani-v7-latin-700.eot?#iefix') format('embedded-opentype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-700.woff2') format('woff2'), url('/de/resources/assets/fonts/rajdhani-v7-latin-700.woff') format('woff'), url('/de/resources/assets/fonts/rajdhani-v7-latin-700.ttf') format('truetype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-700.svg#Rajdhani') format('svg')
}

* {
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
font-size: 100%;
}

.pre-content h1, .content h1, .content h2, .content h3, .mw-body h1, .mw-body-content h1, .mw-body-content h2, .mw-body-content h3 {
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
font-weight:bold;
}

.content h3, .mw-body-content h3 {
text-decoration:underline;
}

p, p *, li, li * {
font-family: Arial,Tahoma,Verdana;
}

.cb {
clear:both;
}

.underline {
text-decoration:underline;
}

.blue {
color:#0099ff;
}
.orange{
color:#ef7f00;
}
.red{
color:#ff0000;
}

table.standardtable {
border: 1px solid black;
border-collapse:collapse;
}

table.standardtable td, table.standardtable th{
padding:5px;
border: 1px solid black;
}

ul.widegallery {
text-align:left;
}

a, #mw-panel .portal .body li a {
color:#ee7f00;
}

a:visited, #mw-panel .portal .body li a:visited {
color:#ee7f00;
}

.specsBox {
position:relative;
float:right;
width:320px;
margin: 16px 0 16px 16px;
box-sizing:border-box;
}

.specsBox *{
box-sizing:border-box;
}

.specsBox .container{
width:320px;
padding:1em;
background-color:#ffeecc;
-webkit-border-radius: 5px;
-moz-border-radius: 5px;
border-radius: 5px;
}

.specsBox .infos {
border-top: 1px solid black;
padding-top:1em;
}

.specsBox span {
display:inline-block;
vertical-align:top;
}
.specsBox .key {
width:33%;
text-align:left;
font-weight:bold;
}

.specsBox .value {
width:66%;
text-align:left;
}

.specsBox .name {
font-weight:bold;
}

.specsBox h3 {
margin: 0 auto;
}

.content .specsBox ul {
padding-left:0;
}

.anlieferungselement {
width:320px;
background-color: #fff1e6;
border-radius: 5px;
margin-right:5px;
margin-bottom: 10px;
padding-bottom:5px;
}

.anlieferungselement *{
box-sizing: border-box;
}

.anlieferungselement:last-of-type {
margin-bottom:0;
}

.anlieferungselement .titel{
font-weight:bold;
font-size:120%;
text-align:center;
border-bottom: 2px solid #ffad66;
background-color: #ffe4cc;
padding: 5px 5px 0 5px;
border-top-left-radius:5px;
border-top-right-radius:5px;
}

.anlieferungselement .subtitel{
font-weight:bold;
font-size:120%;
text-align:center;
border-bottom: 2px solid #ffad66;
background-color: #ffe4cc;
padding: 5px 5px 0 5px;
}

.anlieferungselement .abmessung, .anlieferungselement .gewicht, .anlieferungselement .format, .anlieferungselement .alternative, .anlieferungselement .anmerkung, .anlieferungselement .abmessungExpandiert, .anlieferungselement .mandanten, .anlieferungselement .dauer, .anlieferungselement .seitenverhaeltnis{
padding-left: 5px;
padding-right: 5px;
}

.anlieferungselement .bezeichnung{
width:33%;
font-weight:bold;
padding-right:5px;
display:inline-block;
vertical-align:top;
}
.anlieferungselement .wert{
width:67%;
display:inline-block;
}
.anlieferung_kombination {
display:flex;
}

.anlieferung_kombination.horizontal {
align-content:center;
flex-direction:row;
border: 2px solid #ffad66;
flex-wrap:wrap;
justify-content:center;
}

.anlieferung_kombination.vertikal{
justify-content: center;
flex-direction:column;
align-content:center;
}

.anlieferung_kombination > .container > .anlieferung_kombination.vertikal{

}

.anlieferung_kombination > .container > .anlieferung_kombination.horizontal{
flex:initial;
}

.anlieferung_kombination.horizontal > .anlieferungselement {
flex:none;
margin: 5px;
}

.anlieferung_kombination.horizontal > .zeichen{
flex:none;
}

.anlieferung_kombination > .zeichen{
font-weight: bold;
font-size: 200%;
width: 100px;
text-align: center;
vertical-align:middle;
}

.anlieferung_kombination.vertikal > .zeichen{
font-size:300%;
line-height:80px;
height:80px;
width:320px;
align-self:center;
}

.anlieferung_kombination.vertikal .header {
background-color: #ffe4cc;
width: 100%;
text-align: center;
border: 2px solid #ffad66;
border-bottom: none;
box-sizing: border-box;
}

.anlieferung_kombination .header .bezeichnung{
font-size:200%;
font-weight:bold;
}
.anlieferung_kombination .header .text {
font-size:150%;
}

.galerie {
margin-top:1em;
margin-bottom:1em;
text-align:center;
}

.mainpage {
display:flex;
flex-wrap:wrap;
justify-content:flex-start;
min-width:320px;
box-sizing: border-box;
}

.mainpage * {
box-sizing: border-box;
}

.chapter {
width:320px;
min-width:320px;
margin-right:1em;
}

.kontakt{
margin: 15px 20px 5px 0;
width:200px;
}

.kontakt_name{
font-weight: 700;
font-size:16px;
}

.kontakt_funktion{
border-bottom: 1px solid black;
font-size:16px;
}

.included .specsBox .infos .anlieferung{
display:none;
}
.included .specsBox .infos.text{
padding-top:0;
}

div.warnung::after {
clear:both;
}

div.warnung .icon {
content: "Warnung";
background:url(/de/images/c/cb/Warning.png) no-repeat;
background-position:center;
background-size:24px auto;
width:24px;
height:24px;
line-height:24px;
display:inline-block;
color:rgba(0,0,0,0);
float:left;
margin-right:10px;
}

div.warnung {
background-color:#ffad99;
border:1px solid black;
float:left;
padding:5px;
}

#mw-panel #p-Start.portal .body li {
font-size:20px;
font-weight:bold;
}

.chapterlist {
width:320px;
border: 0.5px solid #a2a9b1;
background-color: #f8f9fa;
color: #222;
margin: 1em 0;
border-collapse: collapse;
font-size:16px;
}

.chapterlist .clheader {
font-size:22px;
background-color:#525050;
color:#FFF;
padding: 0.2em 0.4em;
font-weight:bold;
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
}

.chapterlist ul {
margin:0;
padding:0;
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
}

.chapterlist li {
list-style-type: none;
list-style-image: none;
padding: 0.2em 0.4em;
margin:0;
font-weight:bold;
border-bottom: 0.5px solid #a2a9b1;
line-height:1.6;
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
font-size:100%;
}
.chapterlist li *{
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
}

.mainheader {
background-color: #a2a9b1;
color:#FFFFFF;
text-align:left;
font-size:60px;
width:100%;
padding-left:20px;
height:300px;
padding-top:70px;
}

.mainheader .title {
height:80px;
line-height:80px;
}

.mw-highlight pre {
font-family: "Courier New", monospace;
}

.sdkappinfo .wichtig {
background-color:#e6ffb3;
border:1px solid black;
padding:10px;
float:right;
margin-left:10px;
width:320px;
}

.sdkappinfo .wichtig .warnung {
width:300px;
}

.sdkappinfo .wichtig .warnung .text{
float:right;
width:85%;
}

.keys {
background-color:rgb(235, 235, 235);
border: 1px solid lightgrey;
display:table;
margin:1em;
padding:1em;
border-radius:5px;
flex-wrap:wrap;
}

.keys .box {
display:inline-block;
width:40px;
height:40px;
line-height:40px;
vertical-align:middle;
text-align:center;
background-color:rgb(35, 35, 35);
border:1px solid black;
border-radius:5px;
margin:5px;
color:#FFFFFF;
font-weight:bold;
font-size:140%;
}

div.warning{
border: 1px red solid;
width: 100xp;
height: auto;
display: block;
background: rgba(255,0,0,0.1);
}
div.warning h2{
text-align: center;
margin: 0;
padding: 10px;
font-size: 1.25em;
}
div.warning div.text{
color:black;
padding: 10px;
font-size: 14px;
}
#p-logo a {
background-size: 100% auto;
}

MediaWiki:Mobile.css

2022-12-08T07:48:41Z

Tlohmann:

/* Das folgende CSS wird für alle Nutzer der mobilen Ansicht geladen. */

.mainheader {
background-color: #a2a9b1;
color:#FFFFFF;
text-align:left;
font-size:25px;
width:100%;
padding-left:5px;
height:120px;
padding-top:30px;
}

.mainheader .title {
height:30px;
line-height:30px;
}

.bold {
font-weight:bold;
}

@font-face {
font-family: 'Rajdhani';
font-style: normal;
font-weight: 300;
src: url('/de/resources/assets/fonts/rajdhani-v7-latin-300.eot');
src: local('Rajdhani Light'), local('Rajdhani-Light'), url('/de/resources/assets/fonts/rajdhani-v7-latin-300.eot?#iefix') format('embedded-opentype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-300.woff2') format('woff2'), url('/de/resources/assets/fonts/rajdhani-v7-latin-300.woff') format('woff'), url('/de/resources/assets/fonts/rajdhani-v7-latin-300.ttf') format('truetype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-300.svg#Rajdhani') format('svg')
}

@font-face {
font-family: 'Rajdhani';
font-style: normal;
font-weight: 400;
src: url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.eot');
src: local('Rajdhani Regular'), local('Rajdhani-Regular'), url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.eot?#iefix') format('embedded-opentype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.woff2') format('woff2'), url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.woff') format('woff'), url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.ttf') format('truetype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-regular.svg#Rajdhani') format('svg')
}

@font-face {
font-family: 'Rajdhani';
font-style: normal;
font-weight: 500;
src: url('/de/resources/assets/fonts/rajdhani-v7-latin-500.eot');
src: local('Rajdhani Medium'), local('Rajdhani-Medium'), url('/de/resources/assets/fonts/rajdhani-v7-latin-500.eot?#iefix') format('embedded-opentype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-500.woff2') format('woff2'), url('/de/resources/assets/fonts/rajdhani-v7-latin-500.woff') format('woff'), url('/de/resources/assets/fonts/rajdhani-v7-latin-500.ttf') format('truetype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-500.svg#Rajdhani') format('svg')
}

@font-face {
font-family: 'Rajdhani';
font-style: normal;
font-weight: 600;
src: url('/de/resources/assets/fonts/rajdhani-v7-latin-600.eot');
src: local('Rajdhani SemiBold'), local('Rajdhani-SemiBold'), url('/de/resources/assets/fonts/rajdhani-v7-latin-600.eot?#iefix') format('embedded-opentype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-600.woff2') format('woff2'), url('/de/resources/assets/fonts/rajdhani-v7-latin-600.woff') format('woff'), url('/de/resources/assets/fonts/rajdhani-v7-latin-600.ttf') format('truetype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-600.svg#Rajdhani') format('svg')
}

@font-face {
font-family: 'Rajdhani';
font-style: normal;
font-weight: 700;
src: url('/de/resources/assets/fonts/rajdhani-v7-latin-700.eot');
src: local('Rajdhani Bold'), local('Rajdhani-Bold'), url('/de/resources/assets/fonts/rajdhani-v7-latin-700.eot?#iefix') format('embedded-opentype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-700.woff2') format('woff2'), url('/de/resources/assets/fonts/rajdhani-v7-latin-700.woff') format('woff'), url('/de/resources/assets/fonts/rajdhani-v7-latin-700.ttf') format('truetype'), url('/de/resources/assets/fonts/rajdhani-v7-latin-700.svg#Rajdhani') format('svg')
}

* {
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
font-size: 100%;
}

.pre-content h1, .content h1, .content h2, .content h3, .mw-body h1, .mw-body-content h1, .mw-body-content h2, .mw-body-content h3 {
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
font-weight:bold;
}
.content h3, .mw-body-content h3 {
text-decoration:underline;
}

p, p *, li, li * {
font-family: Arial,Tahoma,Verdana;
}
.branding-box a span {
background-image: url(/de/resources/assets/iq-digital.png?53da3);
background-repeat: no-repeat;
background-size: 100px auto;
background-position: left center;
padding-left:100px;
height:32px;
float:none;
}

.header .branding-box {
width:90%;
}

.header {
white-space:normal;
}

a {
color:#ee7f00;
}

a:visited {
color:#ee7f00;
}

.specsBox {
position:relative;
width:320px;
margin: 16px auto 16px auto;
box-sizing:border-box;
}

.specsBox *{
box-sizing:border-box;
}

.specsBox .container{
width:320px;
padding:1em;
background-color:#ffeecc;
-webkit-border-radius: 5px;
-moz-border-radius: 5px;
border-radius: 5px;
}

.specsBox .infos {
border-top: 1px solid black;
padding-top:16px;
}

.specsBox span {
display:inline-block;
vertical-align:top;
}
.specsBox .key {
width:33%;
text-align:left;
font-weight:bold;
}

.specsBox .value {
width:66%;
text-align:left;
}

.specsBox .name {
font-weight:bold;
}

.specsBox h3 {
margin: 0 auto;
}

.content .specsBox ul {
padding-left:0;
}

.anlieferungselement {
width:320px;
background-color: #fff1e6;
border-radius: 5px;
margin-right:5px;
margin-bottom: 10px;
padding-bottom:5px;
font-size:14px;
}

.anlieferungselement *{
box-sizing: border-box;
}

.anlieferungselement:last-of-type {
margin-bottom:0;
}

.anlieferungselement .titel{
font-weight:bold;
font-size:120%;
text-align:center;
border-bottom: 2px solid #ffad66;
background-color: #ffe4cc;
padding: 5px 5px 0 5px;
border-top-left-radius:5px;
border-top-right-radius:5px;
}

.anlieferungselement .abmessung, .anlieferungselement .gewicht, .anlieferungselement .format, .anlieferungselement .alternative, .anlieferungselement .anmerkung, .anlieferungselement .abmessungExpandiert, .anlieferungselement .mandanten, .anlieferungselement .dauer, .anlieferungselement .seitenverhaeltnis{
padding-left: 5px;
padding-right: 5px;
}

.anlieferungselement .bezeichnung{
width:33%;
font-weight:bold;
padding-right:5px;
display:inline-block;
vertical-align:top;
}
.anlieferungselement .wert{
width:67%;
display:inline-block;
}
.anlieferung_kombination {
display:flex;
}

.anlieferung_kombination.horizontal {
align-content:center;
flex-direction:row;
border: 2px solid #ffad66;
flex-wrap:wrap;
justify-content:center;
}

.anlieferung_kombination.vertikal{
justify-content: center;
flex-direction:column;
align-content:center;
}

.anlieferung_kombination > .container > .anlieferung_kombination.vertikal{

}

.anlieferung_kombination > .container > .anlieferung_kombination.horizontal{
flex:initial;
}

.anlieferung_kombination.horizontal > .anlieferungselement {
flex:none;
margin: 5px;
}

.anlieferung_kombination.horizontal > .zeichen{
flex:none;
}

.anlieferung_kombination > .zeichen{
font-weight: bold;
font-size: 200%;
width: 100px;
text-align: center;
vertical-align:middle;
}

.anlieferung_kombination.vertikal > .zeichen{
font-size:300%;
line-height:80px;
height:80px;
width:320px;
align-self:center;
}

.anlieferung_kombination.vertikal .header {
background-color: #ffe4cc;
width: 100%;
text-align: center;
border: 2px solid #ffad66;
border-bottom: none;
box-sizing: border-box;
}

.anlieferung_kombination .header .bezeichnung{
font-size:200%;
font-weight:bold;
}
.anlieferung_kombination .header .text {
font-size:150%;
}

.galerie {
margin-top:1em;
margin-bottom:1em;
text-align: center;
}

.specsBox .galerie .gallery {
margin:0;
padding:0;
}

.mainpage {
display:flex;
flex-wrap:wrap;
justify-content:center;
min-width:320px;
box-sizing: border-box;
}

.mainpage * {
box-sizing: border-box;
}

.chapter {
width:320px;
min-width:320px;
margin-right:16px;
}

@media screen and (max-width: 352px) {
.mainpage, .specsBox {
margin-left:-16px;
margin-right:-16px;
}
.chapter {
width:320px;
min-width:320px;
margin-right:0;
}

.mainheader {
padding-top:15px;
}
}

@media screen and (max-width: 370px) {
.mainheader {
padding-top:15px;
}
}

@media screen and (min-width: 720px) {
.mainpage {
margin-left:-3.35em;
margin-right:-3.35em;
}

.mainheader .title{
text-align:left;
}
}

@media screen and (max-width: 672px) {
.chapter {
margin-right:0;
}

.mainheader .title{
text-align:left;
}
}

.kontakt{
margin: 15px 20px 5px 0;
width:250px;
}

.kontakt_name{
font-weight: 700;
font-size:16px;
}

.kontakt_funktion{
border-bottom: 1px solid black;
font-size:16px;
}

.included .specsBox .infos .anlieferung{
display:none;
}
.included .specsBox .infos.text{
padding-top:0;
}

div.warnung::after {
clear:both;
}

div.warnung::before {
content: "Warnung";
background:url(/de/images/c/cb/Warning.png) no-repeat;
background-position:center;
background-size:24px auto;
width:24px;
height:24px;
line-height:24px;
display:inline-block;
color:rgba(0,0,0,0);
float:left;
margin-right:10px;
}

div.warnung {
font-weight:bold;
font-size:120%;
color:#ff0000;
float:left;
}

.chapterlist {
width:320px;
border: 0.5px solid #a2a9b1;
background-color: #f8f9fa;
color: #222;
margin: 1em auto;
border-collapse: collapse;
font-size:16px;
}

.chapterlist .clheader {
font-size:22px;
background-color:#525050;
color:#FFF;
padding: 0.2em 0.4em;
font-weight:bold;
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
}

.chapterlist ul {
margin:0;
padding:0;
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
}

.chapterlist li {
list-style-type: none;
list-style-image: none;
padding: 0.2em 0.4em;
margin:0;
font-weight:bold;
border-bottom: 0.5px solid #a2a9b1;
line-height:1.6;
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
font-size:100%;
}
.chapterlist li *{
font-family: 'Rajdhani',sans-serif,Arial,Tahoma,Verdana;
}

Integration of the Google Mobile Ads SDK

2022-08-17T10:41:37Z

Tlohmann:

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app, e.g. politik (politics)
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are openingpage, swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored. Since Google's AppEventListener interface has a @NonNull annotation for data, the noad event simply passes the value "noad" for data, since the empty string is converted as null by Google.
[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Integration of the Google Mobile Ads SDK

2022-08-17T10:40:25Z

Tlohmann:

The purpose of this documentation is to explain the integration of the Google Mobile Ads SDK (GMA SDK) and the ad integration process of iq digital. It outlines the necessary and important features of this process and attempts to clarify common misunderstandings.

The documentation begins with the GMA SDK and general information that applies to all ad formats designed to run in the app. This is followed by ad format-specific explanations and, finally, an explanation of ad format-specific events that have to be taken into consideration by the app.

==Official documentation for the Google Mobile Ads SDK==
The Google Mobile Ads SDK (GMA SDK) provides everything that is necessary for ad serving in native apps.

===Getting Started with the Google Mobile Ads SDK===
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/quick-start GMA SDK iOS Getting Started]

[https://developers.google.com/ad-manager/mobile-ads-sdk/android/quick-start GMA SDK Android Getting Started]

===Downloading the Google Mobile Ads SDK===
====Android====
The GMA SDK is integrated in the Android play services and is therefore present on Android devices.

====iOS====
The GMA SDK for iOS can be downloaded here:
[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/download Download iOS]

===Ad-Manager vs. Admob===
There are two versions of the documentation for the Google Mobile Ads SDK: one for Ad-Manager users and one for Admob users. iq digital is an Ad-Manager client, which is why it is essential that the browser URL includes https://developers.google.com/ad-manager/.... The Admob documentation differs slightly from the Ad-Manager documentation.

==Brief introduction to the life cycle of ad serving with the GMA SDK==
The life cycle of ad serving is briefly explained here using the example of banner ad serving.

[[Datei:GMA_SDK.png|800px|thumbnail|Übersicht Workflow der Werbeausspielung mit GMA SDK]]

===Request===
The ad request is compiled in the app and comprises multiple components. The following components are important for successful ad serving:
;Consent String:The app requires a valid consent from the user for ad serving. This requires not only multiple relevant purposes but also Vendor 755 Google Advertising Products (see below).
;Creative Sizes:In most cases, we use multisize ad requests. This means that the ad request contains multiple creative sizes and that the ad server then checks whether it can provide a creative for one of these sizes. Examples include 320x1, 320x53, 320x80, 320x106, 320x160 etc.
;Adunit:The ad unit is the address of the ad position. The ad server then knows on which page an ad is to be served. The ad unit is the same for all ad requests of a page request. Example: /183/Rheinischer_Kurier_ios_phone/homepage
;Keywords (optional):Keywords are key-value pairs and can enhance an ad position with additional information needed for targeted ad serving. The ad positions of iq digital all contain a specific designation via which keywords are provided to the ad server. Example: kw=iqadtile1,digtransfrom&tile=1&doc=homepage

===Adserver Google Admanager 360===
If the ad server possesses a valid consent, a distribution algorithm checks whether one or more ad bookings are present for the ad unit, creative sizes and keywords. If this is the case, the ad server selects the best one for this purpose. If multiple bookings are equally important, the ad server selects one of them at random. Only in the case of a “no booking” would the ad server issue a no ad or no fill message, stating that no booking exists for the combination of ad unit, creative size and keywords.

===Serving within the app===
The app loads the response of the ad server comprising the template code and the creative components. It should be noted that the ad container is upsized to the creative size of the served creative. In the case of fullscreen ads, this size must be retroactively adapted to the display viewport size (in other words, device-independent pixels) by the app. In the case of a banner ad, the app generally receives one or more setsize events following the loading process via the AppEventHandler to be integrated and has to adapt the ad container to the new size if the new size differs from the creative size.

===Impression counting===
An impression count measuring that an ad has been viewed is automatically sent by the GMA SDK as soon as at least 1px is in the visible area of the display.

==General informationen==
===Adunits (zoning)===
For the purpose of addressing the pages, Google Ad Manager uses ad units, which can take the following forms:
*/networkId/level1
*/networkId/level1/pagetype
*/networkId/level1/level2/pagetype
*/networkId/level1/level2/level3/pagetype
*etc.

====Explanation of terms====
;networkId:The network ID of iq digital is always to be entered here: 183
;level1:This is the designation of the app in Google Ad Manager and is predefined by iq digital. The designation consists of <appname>_app_<platform>_<devicetype>.
:;appname:The name of the app
:;platform:The operating system, in other words ''ios'' or ''android''
:;devicetype:The device type, in other words ''phone'' or ''tablet''
;level2:This is the designation of a section of the app, e.g. politik (politics)
;level3 (etc.):This is the designation for a sub-section. For example: in the case of politik as level2 ausland (foreign) would be a sub-section for level3. level4 and higher are further, deeper branches of the app and are not usually created as ad units. These types of pages would then be marketed via the supraordinate level3. Example: a page politik/ausland/usa is too specific to be marketed individually. In such a case, it is a good idea that it is only tagged down to level3, in other words as politik/ausland.
;pagetype:In apps with banner ads (e.g. news apps), seitentyp designates the different page types – in other words, whether the page is, for example, an overview, article or photo gallery page. Standard values here are homepage, index, artikel, bildgal. In apps with fullscreen ads (e.g. ePaper or newspaper apps), seitentyp refers to the different ad positions within the section – in other words, whether they are the first, second or third swipe ad, for example. Standard values are openingpage, swipe_1, swipe_2, swipe_3 etc.

====Example for the fictitious Rheinischer Kurier news app with banner ads:====
*/183/Rheinischer_Kurier_app_ios_phone
*/183/Rheinischer_Kurier_app_ios_phone /homepage
*/183/Rheinischer_Kurier_app_ios_phone/politik/index
*/183/Rheinischer_Kurier_app_ios_phone/politik/artikel
*/183/Rheinischer_Kurier_app_ios_phone/politik/bildgal
*/183/Rheinischer_Kurier_app_ios_phone/sport/index
*/183/Rheinischer_Kurier_app_ios_phone/sport/artikel
*/183/Rheinischer_Kurier_app_ios_phone/sport/bildgal

====Example for the fictitious Rheinischer Kurier ePaper iPad app with fullscreen ads:====
*/183/Rheinischer_Kurier_epaper_app_ios_tablet
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/preloading_ad
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/openingpage
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_1
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_2
*/183/Rheinischer_Kurier_epaper_app_ios_tablet/politik/swipe_3

{{Warnung|text=The ad server does not permit any special characters in the ad units with the exception of the underscore "_". Umlauts and the German letter “ß” are also not permitted. level2, level3 and seitentyp must also be written completely in lower case.

The general idea behind the ad units of Google Ad Manager is that they can be dynamically and automatically generated from the CMS of the client. If the CMS is set up in such a way that it appears expedient to use different names, you must contact iq digital at the earliest opportunity to agree on a solution that is acceptable to all parties.

In the case of sections with an and” or a “&” in the name (e.g. Wirtschaft & Politik (Business & Politics), it is a good idea to list only the main words separated by an underscore (i.e. wirtschaft_politik).
}}

===Creative sizes===
Google Ad Manager lists the creative sizes for the ad sizes. The actual size of the served ad may differ from the creative size (in such cases, we talk of “pseudo-size”). The app must poll all corresponding creative sizes for an ad request for the corresponding position. The often long list of sizes is due to the many possible different ad formats and the differences in direct and programmatic marketing.

In the case of fullscreen ad and preloading ad positions, sizes for portrait and landscape mode are generally poled jointly.

====Examples for creative sizes of a banner position:====
99x1, 320x1, 320x50, 320x53, 320x80, 320x160, 320x320, 300x50, 300x75, 300x100, 300x150, 300x250
(in this example, 99x1 and 320x1 are pseudo-sizes. 99x1 calls an outbooking from the ad server and this results in blanking of the ad position. 320x1 is an historical pseudo-size used in rare cases in the position iqadtile1 for ads that deviate from the norm. Each banner position has a comparable pseudo-size with the form 320xY, where Y is the position designation; e.g. 320x1, 320x3, 320x4, 320x8 etc.

====Examples for creative sizes of a fullscreen position on an Android tablet:====
310x480, 480x310, 750x1024, 1024x750

====Links to creative sizes in the Google Mobile Ads SDK:====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#multiple_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#multiple_ad_sizes
and
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#custom_ad_sizes
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#custom_ad_sizes

===Keywords (attachment of key-value pairs)===
In the case of CustomTargeting, an ad request is always given a group of key-value pairs. Multiple values can be separated by a comma. These keywords have multiple functions:
*Certain bookings are only served if these keywords exist (e.g. for specific products or also in the case of test insertions).
*Bookings can be excluded from serving via these kinds of keywords (e.g. in order to prevent incorrect presentation of an ad booking).
*These kinds of keywords permit detailed serving reports.

iq digital uses certain key-value pairs, the most important of which are explained below:
;kw:General keyword list: multiple values are generally separated by commas. Some legacy values are standard (e.g. digtransform, nospa, enozqi). There are also designators for the app or the page (e.g. Rheinischer_Kurier_app_ios_phone) as well as the ad position designation (e.g. iqadtile3).
;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3
;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal.
;iqadtype:Specification of the platform; valid values are online, mew, app, amp.
;appver:The designation of the app version number (see below).

You can find details of which keywords are used for which position in the creative_sizes_and_keywords.xlsc table provided by iq digital at the start of the project.

====Links to CustomTargeting in the Google Mobile Ads SDK====
*https://developers.google.com/ad-manager/mobile-ads-sdk/ios/targeting#custom_targeting
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting

===Debugging===
[[Datei:Easteregg dialog.png|300px|thumbnail|Example from an Android app with text field for keywords and checkbox for USB debugging]]
An "Easter-Egg" function must be integrated in the app so that iq digital can check for problems and test new ad formats within the live app (version from the app or play store). The ad server DFP provides the option of serving test insertions via a keyword in the app.

In a rarely frequented area of the app (such as the imprint), there should therefore be the option for “insiders” to call a small dialogue. This permits insiders to attach a self-selected keyword to every future ad request. The USB debug mode can be activated simultaneously or by ticking a checkbox to inspect the ad webviews in the Android app on Desktop Chrome.

<pre>
WebView.setWebContentsDebuggingEnabled(true);
</pre>
The webviews of the app can then be viewed in Desktop Chrome under Android with chrome://inspect. This permits easier analysis of errors in the presentation of the ad.

Without a debug Easter Egg in the app, it is not possible to perform a test insertion after going live, and it is also not possible to analyse any occurring problems. This would prevent maintenance of the app by iq digital and also mean that the client would be unable to check his app himself with test advertising. The keyword function therefore serves to limit the group of people who would be able to see the test insertions.

Attachment of the keywords is explained in more detail under #Attachment of key-value pairs.

Multiple keywords are separated by commas.

There are a wide range of options for activation of the Easter Egg. Multiple/Pointless taps on UI elements or highly specific input in the search field are just some examples. However, iq digital has defined a rule that the debug Easter Egg is activated identically under Android and iOS. We are happy to be of assistance with regard to the method via which the debug Easter Egg is activated.

===Important notes on these instructions===
We will only compile the ad units for the ad positions and trial-run test advertising on the ad units at the start of the project. The ad units will then be transmitted to the clients. Please do not use the logic that is integrated in the SDK for test ads. The logic does not correspond to the way in which the advertising marketed by iq digital works and will result in misunderstandings. Instead, bookings with test ads are permanently active on the ad units, and these test ads are served by the ad server via a special test keyword in the ad request.

===Contacts at iq digital===
Please feel free to contact iq digital if you have any questions or comments. In the event that we are unable to help, we have the option of including a developer from Google in the discussion.

====Tim Lohmann (Mobile Developer Ad Technology)====
;Phone:+49 211 887 2336
;E-Mail:tim.lohmann@iqdigital.de

===WImportant documents===
====List of creative sizes and keywords for each position:====
*<date>_dfp_creative_sizes.xlsx
====List of ad units:====
(These only serve as guidance. The apps should generate these zones dynamically from the CMS)

<appname> must be replaced by the corresponding app name.
*<date>_adunits_<appname>_android_tablet.txt
*<date>_adunits_<appname>_ios_tablet.txt
*<date>_adunits_<appname>_ android_phone.txt
*<date>_adunits_<appname>_ios_phone.txt

==Preloading Ad==
{{SDKAppInfo
|info=
The ad position is a display-filling ad that is displayed during the loading screen (splash screen) of the app. It is displayed for 5s and then closes automatically. A “Close” button is displayed in a corner so that the user can access the content of the app without waiting.

[[Datei:Preloading Ad 1.png|x300px]]
[[Datei:Preloading Ad 2.png|300px]]
|position=
The position superimposes itself on the splash screen of the app like an overlay. The app can then load the content in the background.
|template=
*Scales the ad while retaining the aspect ratio in line with the dimensions of the ad container.
*Closes the ad after 5s
*Positions and centres the ad
*Displays a “Close” button in a corner via which the user can return to the content at any time.
*In the case of an orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are defined and are made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request during the splash screen
*In the event of a booking:
**Generates the interstitial with the help of the GMA SDK.
**Upsizes the ad container to display size.
*In the case of an orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*Continues to prepare the content in the background.
*In the case of no booking: the content is loaded normally.
|workflowad=
#The app is started by the user.
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the interstitial.
#The ad template scales the ad in the container.
#The ad closes automatically after 5s and the content behind the ad becomes visible.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app loads the content quite normally.
|creativesizes=
;Smartphone:320x480 and 480x320
;Tablet:768x1024 and 1024x768<br />(with Android also additionally: 320x480
and 480x320)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtilePre
;tile:0
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/interstitial
}}

==Fullscreen Ads (also called swipe ads)==
{{SDKAppInfo
|info=
The ad position is a display-filling ad displayed between two regular content pages in the app. It can be horizontally swiped like the other content pages and is not overlaid by any parts of the app (like the app header or footer). If the user generates an orientation change event, the ad adapts to the new aspect ratio.

[[Datei:Fullscreen Ad 1.png|x300px]]
[[Datei:Fullscreen Ad 2.png|300px]]
|position=
The position is dynamically embedded between two content pages. The ad position is always on the right next to the page assigned to it in the content (e.g. Politik/swipe_1 means that the first politics content page is displayed first and that the advertising page appears with the next swipe).
|template=
*Scales ads while retaining the aspect ratio in line with the dimensions of the ad container.
*Positions and centres the ad.
*In the case of orientation change or resize event: scales the ads in line with the new dimensions. It can take several hundred milliseconds until all new dimensions are determined and can be made available by the webview browser.
Depending on the display, scaling can result in black or white bars at the edges. This always happens when the display has a different aspect ratio than the ads.
|app=
*Sends the ad request 1-2 content pages before the position so that the ad server has enough time to serve the ad.
*Dynamically generates an ad page in the page flow on the right next to the assigned content page.
*In the event of a booking: upsizes the ad container to display size.
*Blanks app header and footer (if necessary)
*In the case of orientation change or resize event: adapts the ad page and the ad container to the new display dimensions.
*In the case of no booking: removes the ad page from the page flow.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app dynamically generates the ad page.
#The ad container is upsized to the display dimensions.
#The ad template scales the ad in the container.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds that it has no ad booking.
#The app does not generate an ad page or removes a previously generated ad page from the page flow.
|creativesizes=
;Smartphone:310x480 and 480x310
;Tablet:750x1024 and 1024x750<br />(with Android also additionally: 310x480 and 480x310)
{{Warnung|text=The creative sizes are pseudo-sizes; they do not correspond to the actual dimensions of the ad.}}
|keywords=
;kw:iqadtileFull
;tile:1
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Banner ads==
{{SDKAppInfo
|info=
The ad position is a banner within a content page. Depending on the ad format, this ad may permit more or less interactivity for the end user. It may be animated or may be a complex HTML ad. It is also possible that the ad may change in size due to certain events.

[[Datei:Mobile High Impact Ad.png|x300px]]
|position=
The position is between content elements of a page and requires labelling as “Anzeige” (Advertisement) above the position. There are generally multiple positions within a page.
|template=
*Handles the functionality, which may be simple or complex depending on the ad format.
|app=
*Sends the ad requests for all positions on a page.
*Integrates an ad label “Advertisement” above the position for each position.
*Creates the ad container with a size that is included in the response from the ad server to the ad request.
*Listens with the EventListener for possible setsize or noad events and changes the ad container accordingly.
*In the event of an outbooking:
**If it receives a setsize event, it must adapt the ad position and the ad container to the new size where it differs from the current size.
**If it receives a noad event, it must completely remove or blank the ad position and the corresponding ad label.
|workflowad=
#The app sends an ad request to the ad server.
#The ad server responds with an ad booking.
#The app generates the ad container with the size contained in the response of the ad server.
#It may be necessary to adapt the ad container due to a setsize event.
|workflownoad=
#The app sends an ad request to the ad server.
#The ad server responds with an outbooking as ad booking.
#The app receives a response with the size 99x1 and a short time later a noad event.
#The app blanks the ad position and ad labelling until the next page request.
|creativesizes=
320x50, 320x53, 320x80, 320x106, 320x160, 320x320, 320x416, 320x460, 300x50, 300x75, 300x100, 300x150, 300x200, 300x250, 300x600
Other sizes are possible. Depending on the
position, only an excerpt from the size list is used in the ad request. Exact assignment then takes place in a separate document.

|keywords=
;kw:nospa, enozqi, digtransform, iqadtileX*
;tile:X*
X corresponds to the number of the position, e.g. iqadtile1, iqadtile3, iqadtile4, iqadtile99, iqadtile8.
|links=
;iOS:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
;Android:https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner
}}

==Documentation of the iq digital app events==
In certain situations, the ad templates of iq digital send events to the app. The app must react to these events and change the ad container in line with the following specification. The app events always comprise the name and one "data" string.

===Important links in the GMA SDK documentation===
*[https://developers.google.com/ad-manager/mobile-ads-sdk/ios/banner#app_events GMA SDK iOS App Events]
*[https://developers.google.com/ad-manager/mobile-ads-sdk/android/banner#app_events GMA SDK Android App Events]

===setsize event===
The setsize event is called by the ad templates of iq digital to change the size of the ad view of the ad position. The "data" string has the format "width:height" for an immediate change of size.

=====Parameters=====
The parameters are separated from one another with a colon.
;width:The new width of the ad view in pixels (device-independent pixels) as a whole number.
;height:The new height of the ad view in pixels (device-independent pixels) as a whole number.
{{Warnung|text=Exception: the value max is used for adaptation to the maximum available width or height.}}

Call examples:
;<nowiki>"setsize","320:80"</nowiki>:Ad view is given the new size of 320x80 pixels.
;<nowiki>"setsize","320:240"</nowiki>:Ad view is given the new size of 320x240 pixels.
;<nowiki>"setsize","max:160"</nowiki>:Ad view is adjusted to the maximum available width and a height of 160 pixels.
;<nowiki>"setsize","max:max"</nowiki>:Ad view is adjusted to the maximum available width and the maximum available height.

===noad event===
The noad event is called by the ad templates of iq digital to signal to the app that there is no booking for the position and that the app should remove the ad position '''and the corresponding ad label'''.

The "data" string has no meaning for this event and can be ignored.
[[Kategorie:Ad Technology]][[Kategorie:APP]]
[[de:Einbau des Google Mobile Ads SDK]]

Ad Technology

2022-05-05T09:01:43Z

Tlohmann:

<div class="chapterlist">
<div class="clheader">Ad Technology</div>
*Online/Mobile Web
*[[Adcontroller]]
*[[Creative Identifier]]
*App
*[[Integration of the Google Mobile Ads SDK]]
*[[General rules for banner ads integration]]
*[[General rules for fullscreen ads integration]]
*[[Prebid Mobile SDK in Apps]]
*[[Acceptance criteria advertising integration with Google Mobile SDK‎‎]]
*AMP
*[[Structure of amp-ad tags]]
*[[AMP Ad labelling]]
*[[Change of Prebid Server to Prebid Server Premium]]
</div>
<noinclude>[[Kategorie:Ad Technology]]
[[de:Ad Technology]]</noinclude>

Acceptance criteria advertising integration with Google Mobile SDK

2022-05-05T08:59:54Z

Tlohmann:

This article is about what iq digital expects from a "test app":

==Basic requirements for a test app==
*For the acceptance of the advertising integration, iq digital requires an executable app version that already contains essential components of the final version (also realistic content scope). Otherwise, please indicate which parts cannot yet be accepted.
*The Test app has been tested on platforms (iOS, Android) and mobile devices (not only emulated) to rule out any installation problems / app crashes and to enable acceptance of the advertising integration.
*Status of the advertising integration in the test app version must be documented. Please specify when sending the test app:
**Which parts of the implementation instructions have been implemented?
**Which parts, if any, have not yet been implemented?
**If necessary corrections have already been formulated by iq digital, please respond to the individual points with brief feedback.
*Configuration of the advertising integration has been implemented according to iq digital's specifications. This means in particular the information of the adrequest such as AdUnit, Creative Sizes and Keywords.
*Random checks to ensure that an iq digital test banner is played on the advertising placements for each layout type (homepage, sections, articles, others such as image gal). Iq digital has created test placements for this purpose at the beginning of the project. Please note, if this is not the case.
*The final release version will be used by iq digital for the final approval of the advertising integration.
[[de:Akzeptanzkriterien Werbeintegration mit Google Mobile SDK]]

Acceptance criteria advertising integration with Google Mobile SDK

2022-05-05T08:59:43Z

Tlohmann:

Acceptance criteria advertising integration with Google Mobile SDK

2022-05-05T08:59:20Z

Tlohmann: Created page with "This article is about what iq digital expects from a "test app": ==Basic requirements for a test app== *For the acceptance of the advertising integration, iq digital requires an executable app version that already contains essential components of the final version (also realistic content scope). Otherwise, please indicate which parts cannot yet be accepted. *The Test app has been tested on platforms (iOS, Android) and mobile devices (not only emulated) to rule out any i..."

AMP Ad labelling

2022-03-22T08:14:23Z

Tlohmann:

Since the ad controller is not built into AMP pages, ad labelling must be done by the publisher. This guide is an example of how to "hide" the ad tag on an AMP page, provided no ad has been played on a placement.

==Example structure of an ad label==
<syntaxhighlight lang="html">
<div class="iqampcenter">
<amp-ad> … </amp-ad>
<div class="iqadmarker">Anzeige</div>
</div>
</syntaxhighlight>
*The "iqadmarker" div is positioned behind the amp-ad tag in the HTML code.
*The surrounding div container "iqampcenter" gets additional CSS styling:
<syntaxhighlight lang="css">
display: flex;
flex-direction: column;
</syntaxhighlight>
*The "iqadmarker"-div gets the CSS styling:
<syntaxhighlight lang="css">
order: -1;
display:none;
</syntaxhighlight>
:Thus it slips in front of the amp-ad and is not visible at first.
*If an ad is booked, delivered and the amp-ad is displayed as a result, the ad label will appear with the following code:
<syntaxhighlight lang="css">
.iqampcenter > amp-ad:not([hidden]) + .iqadmarker {
display: table;
}
</syntaxhighlight>
'''iqampcenter''' and '''iqadmarker''' are of course only example names, which can be replaced by better names.
==Summary==
For a quick overview, here are the code blocks used again:

===HTML structure===
<syntaxhighlight lang="html">
<div class="iqampcenter" >
<amp-ad … </amp-ad>
<div class="iqadmarker">Anzeige</div>
</div>
</syntaxhighlight>

===CSS===
<syntaxhighlight lang="css">
.iqampcenter {
display: flex;
flex-direction: column;
}

.iqadmarker {
order: -1;
display:none;
}

.iqampcenter > amp-ad:not([hidden]) + .iqadmarker {
display: table;
}
</syntaxhighlight>

[[Category:Ad Technology]][[Category:AMP]]
[[de:AMP Anzeigenkennzeichnung]]

Change of Prebid Server to Prebid Server Premium

2022-03-22T08:14:10Z

Tlohmann:

==Introduction and background==
Until now, iq digital has used Xandr's Prebid Server software to process headerbidding bids from Xandr in AMP. Xandr has created an improved version, Prebid Server Premium, to which all publishers must switch by March 31, 2022 if they want to continue using Prebid Server (Premium). The ad tags hardly change in the process. Only one word in each ad tag must be replaced by the string "psp". An adjustment of the ad tags is mandatory, otherwise errors may occur on the client side after March 31, 2022 and there may also be a loss of revenue if the header bidding provider Xandr is no longer available.

The change to Prebid Server Premium also has the advantage that the software is more modern and it will be easier to add new headerbidding partners in the future without the publisher having to manually add them to their site (as was previously the case). This will also enable us to reduce the number of headerbidding requests in an AMP page in the future, when partners can be configured within the Prebid Server Premium environment and no longer use their own configuration in the amp-rtc config.

==ToDo==
Here's what to do on publisher side for customization:

===Previous===
Example amp-ad tag for an iqadtile3 (explanation: XXXXXX are values that can be different depending on the publisher):
<syntaxhighlight lang="html" lines highlight="9">

<amp-ad data-block-on-consent="_till_accepted" width="320" height="320"
type="doubleclick"
data-slot="/183/XXXXXX"
rtc-config='{
"vendors": {
"yieldlab": {"ADSLOT_ID": "XXXXXX"},
"aps": {"PUB_ID": "3711","PARAMS":{"amp":"1"}},
"prebidappnexus": {"PLACEMENT_ID": "XXXXXX"},
"criteo": {"ZONE_ID": "1298400", "LINE_ITEM_RANGES": "0..20:0.01;20..60:0.05;60..420:1.00","PUBLISHER_SUB_ID":"XXXXXX"}
}, "timeoutMillis": 999}'
json='{"targeting":{"kw":["nospa","enozqi","digtransform","XXXXXX","iqadtile3"],"tile":["3"],"doc":["artikel"],"iqadtype":["amp"]}}'
data-multi-size="320x53,320x80,320x106,320x160,320x50,300x50,300x75,300x100,300x150,300x250"
data-multi-size-validation="false"
data-loading-strategy="1.25">
</amp-ad>
</syntaxhighlight>
In the AMP rtc-config, there is a separate configuration for each headerbidding partner used by iq digital. As seen in the example above, these are Yieldlab, Amazon, Xandr (formerly Appnexus) and Criteo. The change to Prebid Server Premium only affects the configuration of Xandr.
The corresponding line is already highlighted in the example above.

In this line, the word '''''prebidappnexus''''' must be supplemented by the string "psp" to '''''prebidappnexuspsp'''''. The value of "PLACEMENT_ID" remains the same.
===After===
<syntaxhighlight lang="html" lines highlight="9">

<amp-ad data-block-on-consent="_till_accepted" width="320" height="320"
type="doubleclick"
data-slot="/183/XXXXXX"
rtc-config='{
"vendors": {
"yieldlab": {"ADSLOT_ID": "XXXXXX"},
"aps": {"PUB_ID": "3711","PARAMS":{"amp":"1"}},
"prebidappnexuspsp": {"PLACEMENT_ID": "XXXXXX"},
"criteo": {"ZONE_ID": "1298400", "LINE_ITEM_RANGES": "0..20:0.01;20..60:0.05;60..420:1.00","PUBLISHER_SUB_ID":"XXXXXX"}
}, "timeoutMillis": 999}'
json='{"targeting":{"kw":["nospa","enozqi","digtransform","XXXXXX","iqadtile3"],"tile":["3"],"doc":["artikel"],"iqadtype":["amp"]}}'
data-multi-size="320x53,320x80,320x106,320x160,320x50,300x50,300x75,300x100,300x150,300x250"
data-multi-size-validation="false"
data-loading-strategy="1.25">
</amp-ad>
</syntaxhighlight>
{{Warning|titel=In summary|text=The rest of the adtag remains unchanged, as it has already been obstructed for each position. So it is completely sufficient to perform a search&replace action with the search term '''prebidappnexus''' and the replacement text '''prebidappnexuspsp'''!}}
[[Category:Ad Technology]][[Category:AMP]]
[[de:Wechsel Prebid Server zu Prebid Server Premium]]

Ad Technology

2022-03-22T08:13:45Z

Tlohmann:

<div class="chapterlist">
<div class="clheader">Ad Technology</div>
*Online/Mobile Web
*[[Adcontroller]]
*[[Creative Identifier]]
*App
*[[Integration of the Google Mobile Ads SDK]]
*[[General rules for banner ads integration]]
*[[General rules for fullscreen ads integration]]
*[[Prebid Mobile SDK in Apps]]
*AMP
*[[Structure of amp-ad tags]]
*[[AMP Ad labelling]]
*[[Change of Prebid Server to Prebid Server Premium]]
</div>
<noinclude>[[Kategorie:Ad Technology]]
[[de:Ad Technology]]</noinclude>

Creative Identifier

2022-03-22T08:12:49Z

Tlohmann:

==What is the iqd Creative Identifier?==
With the iqd Creative Identifier you can control and report advertisements on sites marketed by iqd. As soon as you see an ad that is obviously not displayed correctly or has inappropriate content, you can report it with a few clicks and we will take care of solving the problem.

==How do I activate the Creative Identifier?==
==Stationary==
To open the Creative Identifier on a stationary website you just have to enter the following key combination on your keyboard:
<div class="keys"><span class="box">↓</span><span class="box">↓</span><span class="box">↑</span><span class="box">↑</span><span class="box">←</span><span class="box">→</span><span class="box">←</span><span class="box">→</span><span class="box">i</span><span class="box">q</span><span class="box">↵</span></div>

Down, Down, Up, Up, Left, Right, Left, Right, i, q, Enter

[[File:Crid online.gif]]

===Mobile===
The Creative Identifier can be called on MEWs and wrapper apps so far. It is not accessible on native apps and AMP pages. The following gestures must be made to enable it:

#Scroll down to the bottom of the page
#Overscroll 5 times''. So swiping down even though you can't scroll down any further
#A small box appears under the footer of the page
#Tap 5 times in the appeared field

[[File:Crid mobile.gif]]

==How do I report advertising via the Creative Identifier?==
This process is identical for a stationary and a mobile ad. In the menu "Adtiles" you will find a list of all ads of this page impression. If you want to assign the faulty banner to the list in the menu "Adtiles" this is very easy:

#Click on "Options" (three vertical dots) after each item in the list and click on "Scroll to Adtile". Now you should automatically scroll to the adtile.
#If there is more than one ad in the current field of view of the browser window you can distinguish the ads by hovering (stationary) or tapping (mobile) on a list item of the Creative Identifier.

[[File:Crid adtiles r.jpg]] [[File:Crid adtiles options r.jpg]]

Once you have identified the ad you want to report, click on "Options" for that element again. This time you select "Report Adtile". Here you can report several different ads per page impression at the same time. You will then land in the "Report" menu. There you should briefly and concisely describe the error.

[[File:Crid melden r.jpg]]

After you have added a short description of the error you can click on the "Report" button. This will automatically open an email program of your choice and generate an email with all relevant information we need to debug the ad. Please do not delete any information from this generated email! Make a screenshot of the ad and attach it to the email. After you have sent the mail, we will take care of everything else.

'''Thank you very much for your support.'''
[[de:Creative Identifier]]

Creative Identifier

2022-03-22T08:12:35Z

Tlohmann:

Creative Identifier

2022-03-22T08:11:48Z

Tlohmann: Created page with "==What is the iqd Creative Identifier?== With the iqd Creative Identifier you can control and report advertisements on sites marketed by iqd. As soon as you see an ad that is obviously not displayed correctly or has inappropriate content, you can report it with a few clicks and we will take care of solving the problem. ==How do I activate the Creative Identifier?== ==Stationary== To open the Creative Identifier on a stationary website you just have to enter the followin..."

==What is the iqd Creative Identifier?==
With the iqd Creative Identifier you can control and report advertisements on sites marketed by iqd. As soon as you see an ad that is obviously not displayed correctly or has inappropriate content, you can report it with a few clicks and we will take care of solving the problem.

==How do I activate the Creative Identifier?==
==Stationary==
To open the Creative Identifier on a stationary website you just have to enter the following key combination on your keyboard:
<div class="keys"><span class="box">↓</span><span class="box">↓</span><span class="box">↑</span><span class="box">↑</span><span class="box">←</span><span class="box">→</span><span class="box">←</span><span class="box">→</span><span class="box">i</span><span class="box">q</span><span class="box">↵</span></div>

Down, Down, Up, Up, Left, Right, Left, Right, i, q, Enter

[[File:Crid online.gif]]

===Mobile===
The Creative Identifier can be called on MEWs and wrapper apps so far. It is not accessible on native apps and AMP pages. The following gestures must be made to enable it:

#'''Scroll down to the bottom of the page'''
#'''Overscroll 5 times''. So swiping down even though you can't scroll down any further'''
#'''A small box appears under the footer of the page'''
#'''Tap 5 times in the appeared field'''

[[File:Crid mobile.gif]]

==How do I report advertising via the Creative Identifier?==
This process is identical for a stationary and a mobile ad. In the menu "Adtiles" you will find a list of all ads of this page impression. If you want to assign the faulty banner to the list in the menu "Adtiles" this is very easy:

#'''Click on "Options" (three vertical dots) after each item in the list and click on "Scroll to Adtile". Now you should automatically scroll to the adtile.'''
#'''If there is more than one ad in the current field of view of the browser window you can distinguish the ads by hovering (stationary) or tapping (mobile) on a list item of the Creative Identifier.''''

[[File:Crid adtiles r.jpg]] [[File:Crid adtiles options r.jpg]]

Once you have identified the ad you want to report, click on "Options" for that element again. This time you select "Report Adtile". Here you can report several different ads per page impression at the same time. You will then land in the "Report" menu. There you should briefly and concisely describe the error.

[[File:Crid melden r.jpg]]

After you have added a short description of the error you can click on the "Report" button. This will automatically open an email program of your choice and generate an email with all relevant information we need to debug the ad. Please do not delete any information from this generated email! Make a screenshot of the ad and attach it to the email. After you have sent the mail, we will take care of everything else.

'''Thank you very much for your support.'''
[[en:Creative Identifier]]

AMP Ad labelling

2022-03-22T08:04:46Z

Tlohmann: Created page with "Since the ad controller is not built into AMP pages, ad labelling must be done by the publisher. This guide is an example of how to "hide" the ad tag on an AMP page, provided no ad has been played on a placement. ==Example structure of an ad label== <syntaxhighlight lang="html"> <div class="iqampcenter"> <amp-ad> … </amp-ad> <div class="iqadmarker">Anzeige</div> </div> </syntaxhighlight> *The "iqadmarker" div is positioned behind the amp-ad tag in the HTML cod..."

Since the ad controller is not built into AMP pages, ad labelling must be done by the publisher. This guide is an example of how to "hide" the ad tag on an AMP page, provided no ad has been played on a placement.

==Example structure of an ad label==
<syntaxhighlight lang="html">
<div class="iqampcenter">
<amp-ad> … </amp-ad>
<div class="iqadmarker">Anzeige</div>
</div>
</syntaxhighlight>
*The "iqadmarker" div is positioned behind the amp-ad tag in the HTML code.
*The surrounding div container "iqampcenter" gets additional CSS styling:
<syntaxhighlight lang="css">
display: flex;
flex-direction: column;
</syntaxhighlight>
*The "iqadmarker"-div gets the CSS styling:
<syntaxhighlight lang="css">
order: -1;
display:none;
</syntaxhighlight>
:Thus it slips in front of the amp-ad and is not visible at first.
*If an ad is booked, delivered and the amp-ad is displayed as a result, the ad label will appear with the following code:
<syntaxhighlight lang="css">
.iqampcenter > amp-ad:not([hidden]) + .iqadmarker {
display: table;
}
</syntaxhighlight>
'''iqampcenter''' and '''iqadmarker''' are of course only example names, which can be replaced by better names.
==Summary==
For a quick overview, here are the code blocks used again:

===HTML structure===
<syntaxhighlight lang="html">
<div class="iqampcenter" >
<amp-ad … </amp-ad>
<div class="iqadmarker">Anzeige</div>
</div>
</syntaxhighlight>

===CSS===
<syntaxhighlight lang="css">
.iqampcenter {
display: flex;
flex-direction: column;
}

.iqadmarker {
order: -1;
display:none;
}

.iqampcenter > amp-ad:not([hidden]) + .iqadmarker {
display: table;
}
</syntaxhighlight>

[[Kategorie:Ad Technology]][[Kategorie:AMP]]
[[de:AMP Anzeigenkennzeichnung]]

Ad Technology

2022-03-22T07:58:17Z

Tlohmann:

<div class="chapterlist">
<div class="clheader">Ad Technology</div>
*Online/Mobile Web
*[[Adcontroller]]
*App
*[[Integration of the Google Mobile Ads SDK]]
*[[General rules for banner ads integration]]
*[[General rules for fullscreen ads integration]]
*[[Prebid Mobile SDK in Apps]]
*AMP
*[[Structure of amp-ad tags]]
*[[AMP Ad labelling]]
*[[Change of Prebid Server to Prebid Server Premium]]
</div>
<noinclude>[[Kategorie:Ad Technology]]
[[de:Ad Technology]]</noinclude>

MediaWiki:Common.css

2022-03-22T07:52:32Z

Tlohmann:

Template:Warning

2022-03-22T07:51:56Z

Tlohmann: Created page with "<div class="warning"> <h2>{{{titel}}}</h2> <div class="text">{{{text}}}</div> </div>"

<div class="warning">
<h2>{{{titel}}}</h2>
<div class="text">{{{text}}}</div>
</div>

Change of Prebid Server to Prebid Server Premium

2022-03-22T07:51:30Z

Tlohmann:

==Introduction and background==
Until now, iq digital has used Xandr's Prebid Server software to process headerbidding bids from Xandr in AMP. Xandr has created an improved version, Prebid Server Premium, to which all publishers must switch by March 31, 2022 if they want to continue using Prebid Server (Premium). The ad tags hardly change in the process. Only one word in each ad tag must be replaced by the string "psp". An adjustment of the ad tags is mandatory, otherwise errors may occur on the client side after March 31, 2022 and there may also be a loss of revenue if the header bidding provider Xandr is no longer available.

The change to Prebid Server Premium also has the advantage that the software is more modern and it will be easier to add new headerbidding partners in the future without the publisher having to manually add them to their site (as was previously the case). This will also enable us to reduce the number of headerbidding requests in an AMP page in the future, when partners can be configured within the Prebid Server Premium environment and no longer use their own configuration in the amp-rtc config.

==ToDo==
Here's what to do on publisher side for customization:

===Previous===
Example amp-ad tag for an iqadtile3 (explanation: XXXXXX are values that can be different depending on the publisher):
<syntaxhighlight lang="html" lines highlight="9">

<amp-ad data-block-on-consent="_till_accepted" width="320" height="320"
type="doubleclick"
data-slot="/183/XXXXXX"
rtc-config='{
"vendors": {
"yieldlab": {"ADSLOT_ID": "XXXXXX"},
"aps": {"PUB_ID": "3711","PARAMS":{"amp":"1"}},
"prebidappnexus": {"PLACEMENT_ID": "XXXXXX"},
"criteo": {"ZONE_ID": "1298400", "LINE_ITEM_RANGES": "0..20:0.01;20..60:0.05;60..420:1.00","PUBLISHER_SUB_ID":"XXXXXX"}
}, "timeoutMillis": 999}'
json='{"targeting":{"kw":["nospa","enozqi","digtransform","XXXXXX","iqadtile3"],"tile":["3"],"doc":["artikel"],"iqadtype":["amp"]}}'
data-multi-size="320x53,320x80,320x106,320x160,320x50,300x50,300x75,300x100,300x150,300x250"
data-multi-size-validation="false"
data-loading-strategy="1.25">
</amp-ad>
</syntaxhighlight>
In the AMP rtc-config, there is a separate configuration for each headerbidding partner used by iq digital. As seen in the example above, these are Yieldlab, Amazon, Xandr (formerly Appnexus) and Criteo. The change to Prebid Server Premium only affects the configuration of Xandr.
The corresponding line is already highlighted in the example above.

In this line, the word '''''prebidappnexus''''' must be supplemented by the string "psp" to '''''prebidappnexuspsp'''''. The value of "PLACEMENT_ID" remains the same.
===After===
<syntaxhighlight lang="html" lines highlight="9">

<amp-ad data-block-on-consent="_till_accepted" width="320" height="320"
type="doubleclick"
data-slot="/183/XXXXXX"
rtc-config='{
"vendors": {
"yieldlab": {"ADSLOT_ID": "XXXXXX"},
"aps": {"PUB_ID": "3711","PARAMS":{"amp":"1"}},
"prebidappnexuspsp": {"PLACEMENT_ID": "XXXXXX"},
"criteo": {"ZONE_ID": "1298400", "LINE_ITEM_RANGES": "0..20:0.01;20..60:0.05;60..420:1.00","PUBLISHER_SUB_ID":"XXXXXX"}
}, "timeoutMillis": 999}'
json='{"targeting":{"kw":["nospa","enozqi","digtransform","XXXXXX","iqadtile3"],"tile":["3"],"doc":["artikel"],"iqadtype":["amp"]}}'
data-multi-size="320x53,320x80,320x106,320x160,320x50,300x50,300x75,300x100,300x150,300x250"
data-multi-size-validation="false"
data-loading-strategy="1.25">
</amp-ad>
</syntaxhighlight>
{{Warning|titel=In summary|text=The rest of the adtag remains unchanged, as it has already been obstructed for each position. So it is completely sufficient to perform a search&replace action with the search term '''prebidappnexus''' and the replacement text '''prebidappnexuspsp'''!}}
[[de:Wechsel Prebid Server zu Prebid Server Premium]]

Change of Prebid Server to Prebid Server Premium

2022-03-22T07:51:06Z

Tlohmann:

==Introduction and background==
Until now, iq digital has used Xandr's Prebid Server software to process headerbidding bids from Xandr in AMP. Xandr has created an improved version, Prebid Server Premium, to which all publishers must switch by March 31, 2022 if they want to continue using Prebid Server (Premium). The ad tags hardly change in the process. Only one word in each ad tag must be replaced by the string "psp". An adjustment of the ad tags is mandatory, otherwise errors may occur on the client side after March 31, 2022 and there may also be a loss of revenue if the header bidding provider Xandr is no longer available.

The change to Prebid Server Premium also has the advantage that the software is more modern and it will be easier to add new headerbidding partners in the future without the publisher having to manually add them to their site (as was previously the case). This will also enable us to reduce the number of headerbidding requests in an AMP page in the future, when partners can be configured within the Prebid Server Premium environment and no longer use their own configuration in the amp-rtc config.

==ToDo==
Here's what to do on publisher side for customization:

===Previous===
Example amp-ad tag for an iqadtile3 (explanation: XXXXXX are values that can be different depending on the publisher):
<syntaxhighlight lang="html" lines highlight="9">

<amp-ad data-block-on-consent="_till_accepted" width="320" height="320"
type="doubleclick"
data-slot="/183/XXXXXX"
rtc-config='{
"vendors": {
"yieldlab": {"ADSLOT_ID": "XXXXXX"},
"aps": {"PUB_ID": "3711","PARAMS":{"amp":"1"}},
"prebidappnexus": {"PLACEMENT_ID": "XXXXXX"},
"criteo": {"ZONE_ID": "1298400", "LINE_ITEM_RANGES": "0..20:0.01;20..60:0.05;60..420:1.00","PUBLISHER_SUB_ID":"XXXXXX"}
}, "timeoutMillis": 999}'
json='{"targeting":{"kw":["nospa","enozqi","digtransform","XXXXXX","iqadtile3"],"tile":["3"],"doc":["artikel"],"iqadtype":["amp"]}}'
data-multi-size="320x53,320x80,320x106,320x160,320x50,300x50,300x75,300x100,300x150,300x250"
data-multi-size-validation="false"
data-loading-strategy="1.25">
</amp-ad>
</syntaxhighlight>
In the AMP rtc-config, there is a separate configuration for each headerbidding partner used by iq digital. As seen in the example above, these are Yieldlab, Amazon, Xandr (formerly Appnexus) and Criteo. The change to Prebid Server Premium only affects the configuration of Xandr.
The corresponding line is already highlighted in the example above.

In this line, the word '''''prebidappnexus''''' must be supplemented by the string "psp" to '''''prebidappnexuspsp'''''. The value of "PLACEMENT_ID" remains the same.
===After===
<syntaxhighlight lang="html" lines highlight="9">

<amp-ad data-block-on-consent="_till_accepted" width="320" height="320"
type="doubleclick"
data-slot="/183/XXXXXX"
rtc-config='{
"vendors": {
"yieldlab": {"ADSLOT_ID": "XXXXXX"},
"aps": {"PUB_ID": "3711","PARAMS":{"amp":"1"}},
"prebidappnexuspsp": {"PLACEMENT_ID": "XXXXXX"},
"criteo": {"ZONE_ID": "1298400", "LINE_ITEM_RANGES": "0..20:0.01;20..60:0.05;60..420:1.00","PUBLISHER_SUB_ID":"XXXXXX"}
}, "timeoutMillis": 999}'
json='{"targeting":{"kw":["nospa","enozqi","digtransform","XXXXXX","iqadtile3"],"tile":["3"],"doc":["artikel"],"iqadtype":["amp"]}}'
data-multi-size="320x53,320x80,320x106,320x160,320x50,300x50,300x75,300x100,300x150,300x250"
data-multi-size-validation="false"
data-loading-strategy="1.25">
</amp-ad>
</syntaxhighlight>
{{Warning|titel=In summary|text=The rest of the adtag remains unchanged, as it has already been obstructed for each position. So it is completely sufficient to perform a search&replace action with the search term '''prebidappnexus''' and the replacement text '''prebidappnexuspsp'''!}}
[[en:Change of Prebid Server to Prebid Server Premium]]

Change of Prebid Server to Prebid Server Premium

2022-03-22T07:50:51Z

Tlohmann: Created page with "==Introduction and background== Until now, iq digital has used Xandr's Prebid Server software to process headerbidding bids from Xandr in AMP. Xandr has created an improved version, Prebid Server Premium, to which all publishers must switch by March 31, 2022 if they want to continue using Prebid Server (Premium). The ad tags hardly change in the process. Only one word in each ad tag must be replaced by the string "psp". An adjustment of the ad tags is mandatory, otherwis..."

==Introduction and background==
Until now, iq digital has used Xandr's Prebid Server software to process headerbidding bids from Xandr in AMP. Xandr has created an improved version, Prebid Server Premium, to which all publishers must switch by March 31, 2022 if they want to continue using Prebid Server (Premium). The ad tags hardly change in the process. Only one word in each ad tag must be replaced by the string "psp". An adjustment of the ad tags is mandatory, otherwise errors may occur on the client side after March 31, 2022 and there may also be a loss of revenue if the header bidding provider Xandr is no longer available.

The change to Prebid Server Premium also has the advantage that the software is more modern and it will be easier to add new headerbidding partners in the future without the publisher having to manually add them to their site (as was previously the case). This will also enable us to reduce the number of headerbidding requests in an AMP page in the future, when partners can be configured within the Prebid Server Premium environment and no longer use their own configuration in the amp-rtc config.

==ToDo==
Here's what to do on publisher side for customization:

===Previous===
Example amp-ad tag for an iqadtile3 (explanation: XXXXXX are values that can be different depending on the publisher):
<syntaxhighlight lang="html" lines highlight="9">

<amp-ad data-block-on-consent="_till_accepted" width="320" height="320"
type="doubleclick"
data-slot="/183/XXXXXX"
rtc-config='{
"vendors": {
"yieldlab": {"ADSLOT_ID": "XXXXXX"},
"aps": {"PUB_ID": "3711","PARAMS":{"amp":"1"}},
"prebidappnexus": {"PLACEMENT_ID": "XXXXXX"},
"criteo": {"ZONE_ID": "1298400", "LINE_ITEM_RANGES": "0..20:0.01;20..60:0.05;60..420:1.00","PUBLISHER_SUB_ID":"XXXXXX"}
}, "timeoutMillis": 999}'
json='{"targeting":{"kw":["nospa","enozqi","digtransform","XXXXXX","iqadtile3"],"tile":["3"],"doc":["artikel"],"iqadtype":["amp"]}}'
data-multi-size="320x53,320x80,320x106,320x160,320x50,300x50,300x75,300x100,300x150,300x250"
data-multi-size-validation="false"
data-loading-strategy="1.25">
</amp-ad>
</syntaxhighlight>
In the AMP rtc-config, there is a separate configuration for each headerbidding partner used by iq digital. As seen in the example above, these are Yieldlab, Amazon, Xandr (formerly Appnexus) and Criteo. The change to Prebid Server Premium only affects the configuration of Xandr.
The corresponding line is already highlighted in the example above.

In this line, the word '''''prebidappnexus''''' must be supplemented by the string "psp" to '''''prebidappnexuspsp'''''. The value of "PLACEMENT_ID" remains the same.
===After===
<syntaxhighlight lang="html" lines highlight="9">

<amp-ad data-block-on-consent="_till_accepted" width="320" height="320"
type="doubleclick"
data-slot="/183/XXXXXX"
rtc-config='{
"vendors": {
"yieldlab": {"ADSLOT_ID": "XXXXXX"},
"aps": {"PUB_ID": "3711","PARAMS":{"amp":"1"}},
"prebidappnexuspsp": {"PLACEMENT_ID": "XXXXXX"},
"criteo": {"ZONE_ID": "1298400", "LINE_ITEM_RANGES": "0..20:0.01;20..60:0.05;60..420:1.00","PUBLISHER_SUB_ID":"XXXXXX"}
}, "timeoutMillis": 999}'
json='{"targeting":{"kw":["nospa","enozqi","digtransform","XXXXXX","iqadtile3"],"tile":["3"],"doc":["artikel"],"iqadtype":["amp"]}}'
data-multi-size="320x53,320x80,320x106,320x160,320x50,300x50,300x75,300x100,300x150,300x250"
data-multi-size-validation="false"
data-loading-strategy="1.25">
</amp-ad>
</syntaxhighlight>
{{Warning|titel=In summary|text=The rest of the adtag remains unchanged, as it has already been obstructed for each position. So it is completely sufficient to perform a search&replace action with the search term '''prebidappnexus''' and the replacement text '''prebidappnexuspsp'''!}}
[[en:Change of Prebid Server to Prebid Server Premium]]

Prebid Mobile SDK in apps

2022-02-03T13:32:12Z

Tlohmann: Tlohmann moved page Prebid Mobile SDK in apps to Prebid Mobile SDK in Apps

#REDIRECT [[Prebid Mobile SDK in Apps]]

Prebid Mobile SDK in Apps

2022-02-03T13:32:12Z

Tlohmann: Tlohmann moved page Prebid Mobile SDK in apps to Prebid Mobile SDK in Apps

==Introduction==
The Prebid Mobile SDK serves to integrate different header bidding providers in one app, and these providers can then make initial bids for the available ad positions on a page when the page is called. The winning bid is then forwarded via the Google Mobile Ads SDK to the ad server, which compares the bid with other bookings that are present there and serves the most suitable booking.

==Integration and mode of operation==
[[Datei:Prebid SDK.png|800px]]
#Integrate the Prebid Mobile SDK
::iOS: https://github.com/prebid/prebid-mobile-ios
::Android: https://github.com/prebid/prebid-mobile-android
#Create the banner ad unit with all sizes and additional sizes that are to be included in the prebid request (the
PREBID_SERVER_CONFIGURATION_ID is taken from a separate table and assigned to the corresponding position).
#The Prebid Mobile SDK sends a request to the prebid server.
#The prebid server sends back an offer (if present).
#The ad request to Google Ad Manager is supplemented by the prebid parameters.
#Google Ad Manager reviews the request and serves the ad.
#The app displays the ad.

===Android example===
The example on the page shows that man wohl einen DFP PublisherAdView (??) and then generates the prebid banner ad unit. This is then given the prebid server request ID assigned to the banner ad unit and defines a size. Additional sizes are transmitted to the object using the add additional size method. Here, all the sizes should be transmitted that are also normally part of the ad request for the position.

The bids are then connected using fetchDemand. The result codes are defined here: http://prebid.org/prebid-mobile/pbm- api/android/pbm-api-result-codes-android.html
In general, however, an ad request should always occur, regardless of whether bids are contained or not.

==Important configurations==
In our case, the Prebid Mobile SDK works together with Prebid Server Premium and therefore needs a few adjustments:

===Set Host===
Prebid Server Premium must be configured as a custom host. This is done in Android like this:
<pre>
Host custom = Host.CUSTOM;
custom.setHostUrl("https://ib.adnxs.com/openrtb2/prebid");
PrebidMobile.setPrebidServerHost(custom);
</pre>
[https://docs.prebid.org/prebid-mobile/pbm-api/android/prebidmobile-object-android.html#sethost Anleitung Android Custom Host]<br />
[https://docs.prebid.org/prebid-mobile/pbm-api/ios/prebidmobile-object-ios.html Anleitung iOS Custom Host]

===Set Account ID===
Our account ID must also be set.
<pre>PrebidMobile.setPrebidServerAccountId("6975");</pre>

==Important Links==
*[https://docs.prebid.org/prebid-mobile/prebid-mobile.html Getting Started]
*[https://docs.prebid.org/prebid-mobile/prebid-mobile-pbs.html#developers---using-the-sdk Developers using the SDK]
*[https://docs.prebid.org/prebid-mobile/privacy-regulation.html Privacy Regulation]
*[https://docs.prebid.org/prebid-server/use-cases/pbs-sdk.html#prebid-sdk-calls-prebid-server Prebid SDK Workflow]

===iOS===
*[https://docs.prebid.org/prebid-mobile/pbm-api/ios/code-integration-ios.html Code Integration]
*[https://docs.prebid.org/prebid-mobile/pbm-api/ios/pbm-banneradunit-ios.html Banner Adunit]

===Android===
*[https://docs.prebid.org/prebid-mobile/pbm-api/android/code-integration-android.html Code Integration]
*[https://docs.prebid.org/prebid-mobile/pbm-api/android/pbm-banneradunit-android.html Banner Adunit]
[[de:Prebid Mobile SDK in Apps]]