At a glance : Trackier has an integrated anti-fraud capability that can be utilized to counter fraudulent and illicit activities on its platform, thereby preserving your funds and bolstering the general welfare of your venture.
Trackier has an in-built feature to optimize your business activities and maintain healthy
installs and events on the platform by preventing fraudulent and unethical practices.
Where to find this?
You will find this option as part of the manage section. Inside rules, user will find the option for global and custom rules.
Global rule will be applied to all the incoming traffic be it from partner, organic or deep links in case enabled
Custom rules - To create exceptions for the fraud settings (Bypass or scan for other conditions).
Flow for the Process
Global rule - This rule be implemented to all the traffic. Whatever the user will enable or disable as part of the predefined anti fraud settings will be applied to all the incoming traffic
Custom Rule - In case the user want to create exceptions as part of the global rule they can create custom rules and add conditions as per the requirement
a) Click on the "+ Add custom rule" button
b) Rule Name - Give your custom rule an appropriate name
c) Apply On - To whom the rule will be applied it. It could partners, deeplinks or both of them
d) Application
e) Engagement metrics to apply - Metric on which this will be applied - It could be either install, in app , specific in app events or both
i) Mark as rejected on custom setting - Choose to block the traffic based on the conditions that will be defined as part of this section
ii) Mark as rejected on predefined setting - Analyze and block or bypass the pre-defined fraud settings on the traffic
iii) Bypass - The traffic will bypass the fraud shield based on the conditions that the user have mentioned
f) Custom Condition - Choose the custom conditions on which you want to mark the traffic as fraud or want to bypass the fraud. We currently have ITET(Install to event time), CTIT(Click to install time), Campaign, Campaign ID, Ad, Ad Id, Ad set, Ad set ID, Site ID, Geo, Os version, app version, SDK version, SDK Param {1-10}
g) In case the user selected "Mark as rejected on predefined setting", they can click on next button and move to pre defined anti fraud settings. Further, enable or disable the settings and click on finish. If chosen "Mark as rejected on custom setting" or "Bypass" then post adding conditions user can simply to go next step and click on "Finish"
Manage Rules
The user can change the status of the rule and can choose to either enable or disable based on the use cases
One can edit or delete the rule if needed from the options inside the actions
Elaboration on each attribute
Attribute | Description |
SDK Spoofing |
|
Untrusted Device |
|
Blacklist IP | It is possible that analysis can be empty in case the IP is blacklisted in our database. but if not the analysis could show below -
|
Duplicate IP |
|
Emulator |
|
Fake Device |
|
Signature Mismatch |
|
Validation Rule Block |
|
Note: You can also apply this fraud setting on organic events such as ( Installs / InApp Event / Uninstall / Session ) by scrolling to the settings option.
Override fraudulent event settings
If you want your in-app events not to be marked as fraud with anti fraud settings, you can select the event name from the drop down box, post which you can select if same applies to all the media sources/partners or you can select the specified partner or media source from the provided option. You can add multiple events for this option to override the fraudulent events.
We are delighted to have assembled a world-class team of experienced professionals who are ready to take care of your queries and answer any questions you may have. Feel free to reach out to us at anytime through emailing us at support@apptrove.com or by using the in-platform chat feature. We'd love to hear from you!
