321
edits
Integration of the Google Mobile Ads SDK: Difference between revisions
Jump to navigation
Jump to search
Integration of the Google Mobile Ads SDK (view source)
Revision as of 15:45, 26 November 2021
, 26 November 2021no edit summary
(Created page with "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...") |
No edit summary |
||
| Line 115: | Line 115: | ||
iq digital uses certain key-value pairs, the most important of which are explained below: | iq digital uses certain key-value pairs, the most important of which are explained below: | ||
;kw: | ;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: | ;tile:The number of the ad position; in the case of an iqadtile3 therefore as value 3 | ||
;doc: | ;doc:The designation of the page type; valid values are homepage, index, artikel, bildgal. | ||
;iqadtype: | ;iqadtype:Specification of the platform; valid values are online, mew, app, amp. | ||
;appver: | ;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 | ====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/ios/targeting#custom_targeting | ||
*https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting | *https://developers.google.com/ad-manager/mobile-ads-sdk/android/targeting#custom_targeting | ||
===Debugging=== | ===Debugging=== | ||
[[Datei:Easteregg dialog.png|300px|thumbnail| | [[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> | <pre> | ||
WebView.setWebContentsDebuggingEnabled(true); | WebView.setWebContentsDebuggingEnabled(true); | ||
</pre> | </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)==== | ====Tim Lohmann (Mobile Developer Ad Technology)==== | ||
; | ;Phone:+49 211 887 2336 | ||
;E-Mail:tim.lohmann@iqdigital.de | ;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> | |||
*< | <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 | |||