Prebid Mobile SDK in Apps - Revision history

Tlohmann at 09:17, 13 August 2026

2026-08-13T09:17:55Z

← Older revision		Revision as of 11:17, 13 August 2026
Line 115:		Line 115:
	====Example iOS:====		====Example iOS:====
	<pre>		<pre>
	Targeting.shared.storeURL = "https://apps.apple.com/app/id111111111""		Targeting.shared.storeURL = "https://apps.apple.com/app/id111111111"
	</pre>		</pre>

Tlohmann at 08:24, 7 August 2026

2026-08-07T08:24:51Z

@@ Line 103: / Line 103: @@
 """)
+)
 </pre>
@@ Line 128: / Line 141: @@
+     }
 """.trimIndent()
 </pre>

Tlohmann at 06:55, 7 August 2026

2026-08-07T06:55:21Z

← Older revision		Revision as of 08:55, 7 August 2026
Line 131:		Line 131:

	===Store-URL===		===Store-URL===
	The app should include the URL ~~of the website page associated with the app so that bidders can understand the page~~ and ~~bid accordingly. This~~ typically increases bids ~~and is therefore relevant to~~ revenue.		The app should include the corresponding App Store/Play Store URL. Bidders pay attention to this, and it typically increases bids, so it has an impact on revenue.

	====Example Android:====		====Example Android:====
	<pre>		<pre>
	TargetingParams.setStoreUrl("https://~~faz~~.~~net~~/~~aktuell~~");		TargetingParams.setStoreUrl("https://play.google.com/store/apps/details?id=com.example.app");
	</pre>		</pre>

	====Example iOS:====		====Example iOS:====
	<pre>		<pre>
	Targeting.shared.storeURL = "https://~~www~~.~~faz~~.~~net~~/~~aktuell~~"		Targeting.shared.storeURL = "https://apps.apple.com/app/id111111111""
	</pre>		</pre>


	==Appendix: How Prebid Mobile SDK and GMA SDK work==		==Appendix: How Prebid Mobile SDK and GMA SDK work==

Tlohmann at 10:50, 6 August 2026

2026-08-06T10:50:41Z

← Older revision		Revision as of 12:50, 6 August 2026
Line 137:		Line 137:
	TargetingParams.setStoreUrl("https://faz.net/aktuell");		TargetingParams.setStoreUrl("https://faz.net/aktuell");
	</pre>		</pre>
			====Example iOS:====
			<pre>
			Targeting.shared.storeURL = "https://www.faz.net/aktuell"
			</pre>


	==Appendix: How Prebid Mobile SDK and GMA SDK work==		==Appendix: How Prebid Mobile SDK and GMA SDK work==

Tlohmann at 10:49, 6 August 2026

2026-08-06T10:49:19Z

← Older revision		Revision as of 12:49, 6 August 2026
Line 84:		Line 84:
	The Headerbidding partners should be informed which DisplayManager and which version is being used.		The Headerbidding partners should be informed which DisplayManager and which version is being used.

	====Example:====		===Example Android:====
	<pre>		<pre>
	~~TargetingParams~~.~~setGlobalOrtbConfig(~~		adUnit?.impOrtbConfig = """
	"""		{
	{		"displaymanager": "Google",
	"displaymanager": "Google",		"displaymanagerver": "${MobileAds.getVersion()}"
	"displaymanagerver": "${MobileAds.getVersion()}",		}
	"~~ext~~": {		""".trimIndent()
	"~~myext~~": {		)
	"~~test~~": 1		</pre>
	}		====Example iOS:====
	}		<pre>
	}		adUnit.setImpORTBConfig("""
	"""~~.trimIndent(~~)		{
			"displaymanager": "Google",
			"displaymanagerver": "\(string(for: MobileAds.shared.versionNumber))"
			}
			""")
	)		)
	</pre>		</pre>
Line 124:		Line 128:
	}		}
	""".trimIndent()		""".trimIndent()
			</pre>

			===Store-URL===
			The app should include the URL of the website page associated with the app so that bidders can understand the page and bid accordingly. This typically increases bids and is therefore relevant to revenue.

			====Example Android:====
			<pre>
			TargetingParams.setStoreUrl("https://faz.net/aktuell");
	</pre>		</pre>

Tlohmann at 07:26, 20 May 2026

2026-05-20T07:26:00Z

← Older revision		Revision as of 09:26, 20 May 2026
Line 20:		Line 20:

	*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 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'''		*Prebid Server Url: '''https://iqdigital-pbs.relevant-digital.com/openrtb2/auction'''

	===Example===		===Example===
Line 26:		Line 26:
	PrebidMobile.setPrebidServerAccountId("<<<PREBID_SERVER_ACCOUNT_ID>>>")		PrebidMobile.setPrebidServerAccountId("<<<PREBID_SERVER_ACCOUNT_ID>>>")

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

	PrebidMobile.initializeSdk(		PrebidMobile.initializeSdk(
	applicationContext,		applicationContext,
	"https://~~client~~-pbs.relevant-digital.com/openrtb2/auction") { status ->		"https://iqdigital-pbs.relevant-digital.com/openrtb2/auction") { status ->
	if (status == InitializationStatus.SUCCEEDED) {		if (status == InitializationStatus.SUCCEEDED) {
	Log.d(TAG, "SDK initialized successfully!")		Log.d(TAG, "SDK initialized successfully!")

Tlohmann at 09:38, 30 April 2026

2026-04-30T09:38:34Z

← Older revision		Revision as of 11:38, 30 April 2026
Line 107:		Line 107:
	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!		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		*'''gpid''' corresponds to the AdUnit plus the iqadtile identifier used for the iqadtile, which is appended with a hyphen "-", e.g. /183/FAZ_app_android_phone/homepage-iqadtile3
	*'''pbadslot''' is ~~a combination of AdUnit,~~ the ~~character~~ '#' ~~and the iqadtile~~, example /183/FAZ_app_android_phone/homepage#iqadtile3		*'''pbadslot''' is the same value as '''gpid''', example /183/FAZ_app_android_phone/homepage-iqadtile3
	*'''relevant_slotInstance''' is the number of the iqadtile, example 3 for iqadtile3		*'''relevant_slotInstance''' is the number of the iqadtile, example 3 for iqadtile3

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

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

2026-02-11T13:21:01Z

Step 3 - Create BannerAdUnits per placement

← Older revision		Revision as of 15:21, 11 February 2026
Line 45:		Line 45:
	For each ad placement (iqadtile), a BannerAdUnit must be created and configured:		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		#'''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)		#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)

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

2026-02-11T13:20:18Z

Step 2 - Initial global configuration

← Older revision		Revision as of 15:20, 11 February 2026
Line 19:		Line 19:
	At the beginning, the endpoint and account ID must be set in the SDK and placed in an initialization method		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 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'''		*Prebid Server Url: '''https://client-pbs.relevant-digital.com/openrtb2/auction'''

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

2026-02-11T13:20:06Z

Step 2 - Initial global configuration

← Older revision		Revision as of 15:20, 11 February 2026
Line 19:		Line 19:
	At the beginning, the endpoint and account ID must be set in the SDK and placed in an initialization method		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'''		*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===		===Example===