Back to Bidders

HuaweiAds

Features

Bidder Code huaweiads Prebid.org Member no
Prebid.js Adapter no Prebid Server Adapter yes
Media Types display, video, native Multi Format Support check with bidder
TCF-EU Support yes IAB GVL ID 856
GPP Support check with bidder DSA Support check with bidder
USP/CCPA Support check with bidder COPPA Support yes
Supply Chain Support check with bidder Demand Chain Support check with bidder
Safeframes OK no Supports Deals yes
Floors Module Support check with bidder First Party Data Support check with bidder
User IDs none ORTB Blocking Support check with bidder
Privacy Sandbox check with bidder Prebid Server App Support yes

Note

The Huawei Bidding adapter requires setup and approval before implementation. Please contact us at developereu@huawei.com, also you can submit a ticket online.

Bid Params

Name Scope Description Example Type
publisherid required Publisher Id '2001000399' string
signkey required Sign Key '5d********82c38594f8b2bdfd9f********a398dca734932898e3********8d' string
keyid required Key Id '2' string
slotid required Slot Id 'u42ohmaufh' string
adtype required Ad Type 'banner','native','interstitial','rewarded' string

Notes:

  1. The following parameters need to be registered on the HuaweiAds platform, and at the same time, the permission to access the server interface needs to be opened on the HuaweiAds platform.
  2. You can find publisherid, signkey, and keyid on the platform after registration.
  3. You need to create your advertising creative on the platform and get the corresponding slotid and adtype.
  4. We require OAID (Open Advertising ID) or GAID (Google Advertising ID) in the request. OAID and GAID are non-permanent device identifiers that allow personalized ads to be served to users while protecting user data privacy. In most cases, OAID is used for HMS phones and GAID is used for GMS phones. GAID is collected by default. For OAID on HMS phones, app developers should call the AdvertisingIdClient.getAdvertisingIdInfo(mContext) method to obtain the OAID, then add the OAID to the request using the Prebid SDK as shown below.
  5. The auction will use the Prebid Server time zone, but this can be by developers if they send the clientTime targeting parameter to the HuaweiAds Adx server using the Prebid SDK. For example: TargetingParams.addUserData("clientTime", "2018-11-02 16:34:07.981+0800").

Obtain the OAID

// Add the OAID to user data in prebid initialization
if ( isHmsAvailable() ) {
    TargetingParams.addUserData("oaid", AdvertisingIdClient.Info info = AdvertisingIdClient.getAdvertisingIdInfo(getApplicationContext()).getId());
}

//Determine the HMS availability
public static boolean isHmsAvailable(Context context) {
    boolean isAvailable = false;
    if (null != context) {
        int result = HuaweiApiAvailability.getInstance().isHuaweiMobileServicesAvailable(context);
        isAvailable = (com.huawei.hms.api.ConnectionResult.SUCCESS == result);
    }
    Log.i(TAG, "isHmsAvailable: " + isAvailable);
    return isAvailable;
}

"Send All Bids" Ad Server Keys

These are the bidder-specific keys that would be targeted within GAM in a Send-All-Bids scenario. GAM truncates keys to 20 characters.
hb_pb_huaweiads hb_bidder_huaweiads hb_adid_huaweiads
hb_size_huaweiads hb_source_huaweiads hb_format_huaweiads
hb_cache_host_huawei hb_cache_id_huaweiad hb_uuid_huaweiads
hb_cache_path_huawei hb_deal_huaweiads

Back to Bidders