The super admin or platform admin has obtained Google AdMob authorization in the Platform management - Ad authorization section.
Roles and permissions
Feature | Role
Super admin
Platform admin
Superapp admin
Senior superapp developer
Superapp developer
Superapp operator
Approver
Bind AdMob apps or GAM ads
-
-
✓
-
-
-
-
Ad unit - View the list and details
Read-only
Read-only
✓
✓
✓
✓
✓
Approval list - View the pending list
Read-only
Read-only
✓
✓
✓
-
✓
Approval list - Approval
-
-
✓
-
-
-
✓
Approval list - View the approved list and details
Read-only
Read-only
✓
✓
✓
-
✓
Super admin and platform admin have read-only access to the Ad management module. They can view the list and details of ad units, as well as the approval lists—including pending and approved requests and their details. However, they cannot bind AdMob apps or GAM ads, nor can they approve ad unit usage requests.
Superapp admin: Has access to the Ad management module, with permissions to view the list and details of ad unit, view the pending approval list and approved list/details, bind AdMob apps or GAM ads, and approve requests for using ad units.
Senior superapp developer/Superapp developer: Has access to the Ad management module, with permissions to view the list and details of ad unit, view the pending approval list and approved list/details, but cannot bind AdMob apps or approve requests for using ad units.
Superapp operator: Has access to the Ad management module, with permissions to view the list and details of ad unit, but cannot view the pending approval list and approved list/details, cannot bind AdMob apps or GAM ads, and cannot approve requests for using ad units.
Approver: Has access to the Ad management module, with permissions to view the list and details of ad unit, view the pending approval list and approved list/details, and approve requests for using ad units, but cannot bind AdMob apps or GAM ads.
Obtain ad unit
After a super admin or platform admin selects the ad platform and completes authorization, the actions required by the superapp vary depending on the chosen platform.
If you have integrated AdMob, you need to complete the following steps:
Bind AdMob app
Create AdMob ad units
Please note that you need to add the same types and numbers of ad units separately for both Android and iOS apps.
For example: if you add five rewarded ad units and ten banner ad units under the Android app, you must also add five rewarded ad units and ten banner ad units under the iOS app.
The steps to create AdMob ad units are as follows:
2. Click Add ad unit and select either Banner or Rewarded ad unit type. Currently, the Super App as a Service (SAS) only supports these two types.
3. Fill in the required information and click Create ad unit.
Note:
Please make sure the ad unit name prefix is “Tencent.” Otherwise, SAS will be unable to fetch the ad units from AdMob.
After completing the above steps, please log in to the SAS console with the superapp team’s administrator account to bind your AdMob app and fetch the latest ad units. The operation is as follows:
Bind AdMob app to the superapp
After obtaining Google ad authorization on the platform, the superapp needs to bind Google AdMob apps to pull the ad unit list.
Click Bind AdMob app, select the AdMob apps for both iOS and Android, and click Bind.
Confirm the information of the AdMob apps being bound.
After binding, you can pull the ad unit list from AdMob.
Note:
The ad unit list is not synchronized with Google AdMob in real time. You can click the Data synchronization to manually refresh the list.
If you have integrated GAM, you need to complete the following steps:
Bind GAM ad group
After obtaining Google Ad Manager authorization on the platform, the superapp needs to bind Google Ad Manager ad groups to pull the ad unit list.
GAM ad group and ad unit creation
1. Log in to the GAM console and click New ad unit. This ad unit is used exclusively for SAS integration. We recommend naming it “SAS Team.”
Note:
You should create a dedicated ad unit group in your GAM account specifically for SAS integration to keep it separate from your other advertising business.
2. Under the “SAS Team” group, create different child ad units based on the ad unit type. Currently, SAS only supports rewarded ads and banner ads.
We recommend the following names based on the ad type:
Rewarded ads: SAS Team Rewarded
Banner ads: SAS Team Banner
3. Further differentiate the ad units under each ad type by Android and iOS platforms. Under both SAS Team Rewarded and SAS Team Banner ad units, add child ad units for each system with suggested names as follows:
Rewarded ads:
iOS: SAS Team Rewarded_iOS
Android: SAS Team Rewarded_Android
Banner ads:
iOS: SAS Team Banner_iOS
Android: SAS Team Banner_Android
4. Create child ad units under Android and iOS separately for integration with mini programs or mini games.
The final ad unit hierarchy example looks like this:
Bind GAM ad groups to your superapp
In Superapp management > Ad management, click the Bind group on the right side.
iOS group ID: enter the ID for “SAS Team Rewarded_iOS”
Android group ID: enter the ID for “SAS Team Rewarded_Android”
Banner ads:
iOS group ID: enter the ID for “SAS Team Banner_iOS”
Android group ID: enter the ID for “SAS Team Banner_Android”
After filling in the information, carefully verify that all entries are accurate. Once confirmed, click Bind.
Note:
Before any mini program or mini game uses the ad units, you can modify the bindings. Once a mini program or mini game starts using an ad unit, the binding cannot be changed.
After binding, you can pull the ad unit list from AdMob.
Notes:
The ad unit list is not synchronized with Google GAM in real time. You can click the Data synchronization to manually refresh the list.
Approval of the request for using ad units
After the mini program or mini game submits a request for using ad units, the superapp team admin or approvers can navigate to Approval list - Pending, and click Approve to approve the request.
After selecting the approval result, click Confirm to complete the approval.
The superapp team admin or approvers can select Approve or Reject. If Reject is selected, the reason for rejection is required to be filled in to inform the developer why the request is rejected.
The approval record can be found in the Approved section under the Approval list.
