AI-generated Key Takeaways
-
This guide explains how publishers can use Google Mobile Ads SDK to display ads from Fluct via bidding.
-
Fluct supports banner, interstitial, rewarded, and native ad formats for bidding.
-
Publishers need to configure mediation settings in their AdMob account and add Fluct as an ad source.
-
No additional SDKs, adapter libraries, or app code changes are required after setting up Fluct mediation.
- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization scopes
- Examples
- Try it!
Update the specified mediation group under the specified AdMob account.
HTTP request
PATCH https://admob.googleapis.com/v1beta/{mediationGroup.name=accounts/*/mediationGroups/*}
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
mediationGroup.name |
Resource name for this mediation group. Format is: accounts/{publisherId}/mediationGroups/{mediationGroupId} Example: accounts/pub-9876543210987654/mediationGroups/0123456789 |
Query parameters
Parameters | |
---|---|
updateMask |
List of mediation group fields to be updated. Updates to repeated fields such as items in a list will fully replace the existing value(s) with the new value(s). Updates to individual values in a map can be done by indexing by the key. The following field masks are supported for mediation group updates:
To update a mediation group with a new mediation group line, use a distinct negative number for the "mediation_group_line_id". For Example: updateMask { paths: "mediationGroupLines["123456789012345"].cpm_micros" } This is a comma-separated list of fully qualified names of fields. Example: |
Request body
The request body contains an instance of MediationGroup
.
Response body
If successful, the response body contains an instance of MediationGroup
.
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/admob.monetization
For more information, see the OAuth 2.0 Overview.