Set up Anura fraud detection

This article shows how to add Anura, which checks a lead's IP and browsing signals for bots and fraudulent traffic. Use it when you are paying for traffic and need to know whether a real person filled in the form.

Two ways to pay

Anura is the one integration you can turn on without your own account.

Start managed if you want to try it, and switch to your own instance later once volume justifies a direct contract. Entering an Instance ID is what moves the billing.

Prerequisites

• Admin access to Integrations
• An Anura Instance ID, only if you are using your own contract
• A campaign whose leads carry an IP address

Turn it on

1. Open Integrations from the sidebar and open the Anura row.
2. Leave Instance ID blank to use the managed key, or enter your own.
3. Set Timeout in seconds. The default is 2, and 5 is the maximum. A fraud check should never be the slowest thing in your ingest.
4. Save.
5. Open the campaign, go to its Integrations tab, and enable Anura there.
6. Add the rules that decide what happens to a suspect lead.
7. Send a test lead and read the result.

A globally configured integration does nothing until it is also switched on for a campaign.

What Anura returns

Two values are available to rules and filters.

Result is the verdict. Rule Sets tell you why, which is what you need when you want to reject on one kind of signal but not another.

Both are written onto the lead as enriched fields before filters run, so campaign filters, distribution steps, and buyer payload mappings can all read them.

Decide what a suspect lead means

Anura gives you a verdict. What happens next is a rule you write on the campaign's integration settings.

Start by accepting everything and watching the numbers for a week. Rejecting on the verdict from day one, before you know what proportion of your traffic Anura calls suspect, is how a good source gets switched off by accident.

When you are ready, a simple rule rejecting on a suspect result is usually enough. Reach for Rule Sets when you want to reject only on specific signals.

Coverage

Anura covers the United States and Europe. Leads from other countries are not checked.

Expected result

A test lead comes back with a result and any rule sets that fired, visible on the lead. The Usage tab under Integrations logs each call with its request, response, response time, and outcome, which is also where you watch what the managed option is costing you.

Troubleshooting

• Nothing is being checked. The global integration is on but the campaign link is not. Both must be active.
• Everything comes back unchecked. The leads carry no IP address, or their country is outside the supported list.
• Good traffic is being rejected. Your rule is rejecting on the verdict alone. Look at which Rule Sets are firing and narrow the rule to those you actually care about.
• You expected to be billed by Anura and were not. The Instance ID is blank, so the managed key is being used and Datahubb is billing you per verification. Enter your Instance ID to move billing to your own contract.
• Checks are timing out. Raise the timeout, up to the maximum of 5 seconds. Beyond that, take it up with Anura rather than waiting longer at ingest.