Eskimi DSP Anti-fraud Settings
As an admin,Eskimi youDSP canuser, seeit's thatcrucial to harness the power of anti-fraud settings to ensure the effectiveness and integrity of your campaigns. Here's a breakdown of each option available on the approval page for campaigns you are able to enable some anti-fraud settings. Below is a description ofand how eachthey offunction those options works technically on Eskimi DSP:technically:
1. Exclude
Users
newNew (non-Non-DMP) users-
This thesetting systemis willdesigned notto allowfilter winning bids forout users who don't have a DMPData Management Platform (DMP) ID in ourthe Eskimi system. ThereforeBy basicallyenabling thethis option, your campaign mightwill show ads only forprioritize users whoalready are alreadypresent in our DMP.DMP, enhancing the targeting precision and reducing the risk of fraudulent activities.
Eskimi DSP monitors bid requests for each user, and this setting kicks in when a user's daily Apps/Sites count Similar to the previous setting, Eskimi DSP evaluates the number of bid requests per user. If a user's daily page views exceed a specified limit, the system excludes them from winning bids. This helps maintain campaign quality and ensures engagement with authentic users. To combat click fraud, Eskimi DSP employs a code implementation that distinguishes between genuine users and bots mimicking legitimate clicks. Users exhibiting suspicious clicking behavior are automatically disqualified from winning bids, safeguarding your campaign from fraudulent activities. This setting targets domains attempting to mimic popular websites with slight variations in variables or letters. By excluding these spoofed domains, such as forb1s.com instead of forbes.com, Eskimi DSP fortifies your campaign against potential fraudulent traffic. This anti-fraud measure ensures that bid requests are By leveraging these anti-fraud settings, Eskimi 2. Exclude
usersUsers with highHigh Daily Apps/Sites Count-surpasses a predefined threshold. By excluding users with unusually high activity, the system checksmitigates howthe manyrisk of engaging with potentially fraudulent or non-genuine users.3. Exclude Users with High Daily Page Views
4. Exclude Fake Clickers
5. Exclude Domain Spoofers
6. Exclude ads.txt Mismatching Apps/Sites
beingaccepted made for a particular user. If it exceeds a certain threshold that user would be excluded.
3. Exclude users with high daily page views - the system checks how many bid requests are being made for a particular user. If it exceeds a certain threshold that user would be excluded.
4. Exclude Fake clickers - in the system, we have an implementation of code <a hreaf="/fake-click"> ... </a> where a real user is not going to click but a BOT is going to think that it's legit and will keep clicking. Therefore we will not allow winning bids for users with such behavior.
5. Exclude Domain spoofers - exclude domains that are similar to popular websites but with different variables, letters. For example: once the option is selected the well-known domain forbes.com can be reached, while forb1s.com suppose to be excluded
6. Exclude ads.txt mismatching apps/sites - the system will not allow getting trafficonly from the apps/sites where the Exchange or SSP which sendsending the bids requestsis aren't presentedpresent in the ads.txt list. For example:instance, if a popular website like foxnews.com lacks Eskimi in theits ads.txt listlist, for https://www.foxnews.com/ads.txt there is no eskimi in the list. Onceenabling this anti-fraud option is enabled the system will reject bids that comeoriginating from foxnews.comEskimi SSP via foxnews.com, preventing potential fraud.SSP.DSP empowers users to maintain campaign integrity, enhance targeting accuracy, and safeguard against various fraudulent activities in the digital advertising landscape.