At a glance: HUAWEI Ads, an AppsFlyer integrated partner, is a paid presentation service, which provided by Huawei for pan-ecosystem partners. It aims to help partners set up a communication bridge with Huawei device users so they can provide valuable information and quality services for users. HUAWEI ADS provides slots for displaying mainstream ads such as native ads, rewarded video ads, banner ads, and interstitial ads to more than 570 million Huawei device users around the world.
HUAWEI Ads introduction
HUAWEI Ads is integrated into several third-party apps and Huawei apps such as HUAWEI Browser, HUAWEI Video, HUAWEI Assistant, HUAWEI Reader, and HUAWEI Music. Only Huawei Ads display network supports ad attribution. AppGallery and Search network do not support any third-party ad attribution.
Setting up HUAWEI Ads
HUAWEI Ads Global requires to use OAID for attribution. Refer to our Android SDK guide for fetching OAID on HUAWEI devices. In addition, HUAWEI App Gallery referrer attribution is highly recommended for the apps in the store, see our Android SDK guide.
To activate the integration with HUAWEI Ads:
- In AppsFlyer, go to Configuration > Integrated partners.
- Select HUAWEI Ads Global.
- In the Integration tab, enable Activate partner.
Learn more about the partner configuration window header.
The Integration Tab is divided into different sections:
To enable the configuration, activate the partner.
This toggle must be turned on for as long as you work with the partner.
To connect your HUAWEI Ads account with AppsFlyer, enter your secret key in secretKey field.
To get your secretKey:
- Make sure your account is allowlisted by HUAWEI Ads team.
- In HUAWEI Ads dashboard, Go to Toolbox > Tracking > Edit > Key page, and copy the secret key.
Enable view-through attribution
To attribute view-through installs from HUAWEI Ads, turn this toggle on. The view-through lookback window slider is available in the Attribution link tab.
AppsFlyer sends automatic postbacks to HUAWEI Ads following user installs from users attributed to HUAWEI Ads only. Learn more about default postbacks.
In-app events settings
Configure in-app event postbacks that are sent to HUAWEI Ads.
To configure in-app event postbacks:
- Enter your HUAWEI Ads secretKey.
- Turn In-app event postbacks on.
- Set the In-app events postback window.
- To add an SDK Event to the list, click Add event.
- Select the following parameters for each event:
Parameter name Description SDK event name The name of the event, as received by AppsFlyer either from the SDK or from server-to-server events.
Tip: If you don't see the event you want in the list, activate this event on a device with a non-organic installation and recheck.
Partner event identifier
Enter the unique name or ID of each event as defined on HUAWEI Ads. Select the most suitable pre-defined event for your SDK event:
collection(adding to favorites)
addToCart(adding to shopping cart)
Sending option The postbacks can be sent only for the events performed by users attributed to HUAWEI Ads. Send event data
- No values & no revenue: sends only the event itself without the event value.
- Values & no revenue: sends all the parameters excluding the revenue value.
- Values & revenue: sends all the event parameters, including the revenue value (if exists in the event).
- Click Save Integration.
Attribution link tab
Adding parameters to the attribution link enables you to perform thorough drill-down analyses. Parameters that are already defined on the attribution link can be edited by adding them and their new values here.
To generate an attribution link:
- Select a parameter from Parameter name and set a value. Note that some of the parameters' values are macros predefined by HUAWEI Ads. Full list of attribution link parameters.
- To add more parameters, click Add parameter and repeat the previous step.
- Set the duration of the click-through/view-through lookback window.
- Copy the attribution link and add it to your campaign on HUAWEI Ads.
Attribution link parameters
|Parameter||Parameter name||HUAWEI Ads macro||Description|
|__CID__||Add it to compare different campaigns running with HUAWEI Ads.|
|__ADSETID__||Use to differentiate adsets.|
|__ADID__||Use to differentiate between creatives within the adset.|
|Site and subsite ID||af_siteid
Use to attribute installs to specific publishers.
Good practice! If there are multiple publishers,
|Subscriber parameters||af_sub1, af_sub2, af_sub3, af_sub4, and af_sub5||
Use to insert additional useful values.
Cost data is not supported by this partner.
Ad revenue tab
Ad revenue data is not supported by this partner.
In this tab, you can select the permissions to grant HUAWEI Ads. Note that even if attribution is disabled for HUAWEI Ads, the permissions tab is active and you can grant control to HUAWEI Ads.
Configuring campaigns on HUAWEI Ads Global
To configure campaigns on HUAWEI Ads:
- Create a Promotion Task
- Set the tracking URLs:
Note：On the Huawei Ads dashboard, the conversion data(eg. Install/Activations) has 2 data sources, the one is AppsFlyer the other one is HMS. When you want to compare the data, such as install, between AppsFlyer and Huawei Ads dashboard, please select the 'Activations’ instead of 'Activations(HMS)' on the Huawei dashboard.
Huawei impressions < AF impressions
AppsFlyer records all the impressions that Huawei sends to AF, while Huawei Ads would do some data processing before displaying the impressions on Huawei Ads dashboard.
Huawei clicks < AF clicks
AppsFlyer records all the clicks that Huawei sends to AF, while Huawei Ads would do some data processing before displaying the clicks on Huawei Ads dashboard.
AF does not have this metric.
Activations are from AppsFlyer; Activations HMS is from Huawei
Huawei Activations > AF installs
Huawei’s activations are AF's installs. The data discrepancy results from different data reporting logics.
For example, a user downloaded the app from AppGallery on Dec 24th, and first-opened the app on Dec 25th. In this case, AF will record the install on Dec 25th, while Huawei Ads will record this activation on Dec 24th.
Day2 retention and other in-app events
For non-HMS ones, the data sources are AppsFlyer.
Huawei > AF
The data discrepancy results from different data reporting logics.
Following the example above, the user registered in the app on Dec 26th, AF overview dashboard will display the registration data on Dec 25th, same as the install date. While Huawei Ads promotion dashboard will display the registration on Dec 24th, the same as the download date.