Binom Documentation

Go to navigation

Adspect integration

Adspect is one of the best traffic filtering services. With Adspect you can detect bots and proxy/VPN traffic.

Filtering criteria will be exactly the same, however all stats will be visible in Binom only (not in the Adspect panel).

You will need to register and get a subscription. By using the Binom promocode you will get a 15% discount for any license.

Setting up Binom

Step 1

In order to integrate with Adspect, you will need Account ID and API key, that you can find inside the settings of Adspect in General Information and Postback and API key sections respectively:



Inside the tracker, go to Settings -> Integration -> Adspect settings. Press the Add account button. Provide your Account ID and API key and press the Save button:

Step 2

Now you need to create a Bot rule. With the help of Bot and NOT Bot values you will be able to direct traffic according to your need:

Adspect can be used with с Click API.

Nothig is sent to Adspect. Your stats are private and are kept withing your tracker.

Checking bot detection

Here is how you can check if your Adspect integration has been enabled.

  • — To check Adspect's primary bot filter, you can substitute your real IP with 8.8.8.8 using the HTTP header.
  • — To check Adspect's Use fingerprint option (more info below), you can substitute your User Agent for one of a different browser than the one you are using (e.g., put in Mozilla Firefox UA when using Google Chrome).
Such clicks should be marked as Bot clicks in Clicklog (value of 1 in the Is Bot column).

Additional settings

Use fingerprint

This option will turn on an additional traffic filter to make your bot detection even better.

IP/ASN White-list

The IP/ASN white-list field will allow you to add the IP and ASN (Autonomous System Number) exceptions.
If your ASN ranges are not working, check if you have whois installed on your server.

Enabled tags

The Enabled tags field allows to select tags that the tracker will be checking against when determining whether the click should be considered a bot.

Please note that not all tags indicate that the click is fraudulent or is a bot.
Fraud — possibly fraudulent (not human) click.
False+ — a possibility of false-positive detection.

TagFraudFalse+Description
CLOAKMediumLowCloaking-specific Adspect filters triggered
EXTMediumMediumCloaking-specific Adspect extended filters triggered
BOTYesLowOpenly declared bot
APPMediumNoClick coming from or triggered by an application
DCHHighLowIP address belongs to datacenter, hosting company, or IP transit
CDNHighLowIP address belongs to CDN infrastructure
SESYesLowSearch engine spider
GOVLowLowGovernment institution
MILLowLowMilitary facility
EDULowLowUniversity, college, school, or similar
LIBLowLowPublic library
ANONHighLowPublic proxy, VPN service, or anonymizer
TORHighLowTor exit node
UNKYesLowUnmapped IP address (bogon)
RSVYesNoReserved IP address: local area network, class D, etc
EMBEDMediumNoEmbedding detected (<iframe>, <embed>, <object>, etc)
FAKEHighLowBrowser is faking information about itself
DTHighNoDevTools protocol is in use (web automation or develope tools)
AUTOYesNoWeb automation
HWMediumMediumHighly suspecious hardware
DATALowNoMissing or malformed fingerprint data (for POST requests)