I. Set at offer level
|
🪄 Usage scenario: When optimizing a particular offer, or when doing targeted settings for a specific offer only. |
- User Acquisition - Offer List - Edit-Target App - Fulfill Targeting Info - Advanced Targeting - Target App - Custom App - Exclude App
-
Block apps: Fill in the IDs of the sub-sources, separated by commas or by newlines.
-
App ID
-
App ID is MTG ID, usually is mtg&number。
-
You can select App ID in Performance Monitor to see the App ID of the sub-sources.
-
-
Store ID
-
The Store ID for iOS is usually id&number.
-
Store ID for Android is usually "com" & letters.
-
-
-
Effective logic: App ID and Store ID are concatenated and effective at the same time.
-
For example:
-
Fill in the App ID of sub-source 1, sub-source 2, and sub-source 3 in the [App ID].
-
Fill in the Store ID of sub-source 3, and sub-source 4 is filled in [Store ID].
-
The final sub-sources blocked are sub-source 1, sub-source 2, sub-source 3, and sub-source 4.
-
-
II. Set in Performance Monitor
| 🪄Usage scenario: When optimizing lots of offers, it is suggested to block here. |
A. Block traffic by CSV
-
Reports-Performance Monitor-Block traffic by CSV
-
-
Upload the CSV file according to the following form:
-
|
Offer Name |
Target Logic |
App ID |
|
Offer 1 |
exclude |
mtg1234567890,mtg2345678901,mtg3456789012 |
|
Offer 2 |
include |
mtg1234567890,mtg2345678901,mtg3456789012 |
-
Target Logic：
-
Exclude: Block the three apps from the offer 1.
-
Include: Unblock the three apps from the offer 2.
-
-
Tip: blocking traffic via CSV allows you to set the different blacklists for different offers (highly recommended when you have more offers).
B. Optimize Traffic
-
Reports-Performance Monitor-Breakdown by app id-Block Traffic
-
-
Effective scenario: when the button is green, it means that the sub-source is not in the blacklist, when the button in white, it means that the sub-source is blacklisted.
-
III. Set at the account level
| 🪄Usage scenario: when you no longer want to run to some sub-sources, you can block from the account dimension, since the same sub-sources may perform differently on different offers, it is not recommended to enter the configuration from here. |
- User Acquisition - Target Setting - Target App - Custom app - Exclude App
-
⚠️ Please use [Update All] with caution.
-
If this option is checked, the targeting of all the offers associated with the campaign will be updated to the current setting; if it is not checked, the application targeting set here will only take effect for the newly created offers. (❗️It is not recommended to select ❗️)
-
For example: There are three existing offers when configuring the blacklist in the account dimension, which are old offer1, old offer2 and old offer3, and a new offer4 is created after the configuration.
-
Old offer 1: The offer has been configured with a whitelist before the blacklist is configured. After checking [Update All], only this blacklist will be configured and the previous whitelist will be invalidated.
-
Old offer 2: The offer has been configured with a specific blacklist before the blacklist is configured. After ticking [Update All], only the "New Blacklist" will take effect and the previous "Old Blacklist" will be invalidated.
-
Old offer 3: No black/white list targeting has been done, after ticking [Update All], it becomes configured with "This new Blacklist".
-
New offer 4: No matter whether it is ticked or not, any new ad unit will be configured with "This new Blacklist" after the blacklist is set in the account dimension.
-
-