Set Up a Challenge

A challenge is an interactive verification that the visitor sees (similar to a Cloudflare check). It is useful when you don't want to fully block suspicious traffic but want to filter out bots while keeping real users.

When to Use

Suitable Scenarios

• Traffic is suspicious but not definitively fraudulent
• You don't want to lose potential customers due to false positives
• You need additional verification for a specific segment

Step 1. Create a Rule with the Challenge Action

Go to Rules > Add Rule.

Define the conditions under which the challenge should be shown. For example:

Scenario	Conditions
All proxy traffic	is_proxy equals true
Traffic from India with a timezone mismatch	geo_country equals IN AND is_tz_mismatch equals true

Select the Show Challenge action and set a challenge rate — the percentage of visits that will receive the verification.

Why limit the percentage?

If you are unsure about the scale of the fraud, start with 20-30%. This allows you to collect statistics on challenge pass rates without significantly affecting all traffic. If most visitors fail the check — increase the percentage.

Step 2. Attach the Rule to an Integration

Open the relevant integration and add the created rule to the list. Once added, a Challenge section will appear in the integration settings with additional parameters:

• Probability — can be adjusted at the integration level
• Design — choice of verification template

Step 3. Monitor the Results

Challenge metrics are available in Statistics:

Metric	What it shows
Challenge Total	How many times the challenge was shown
Challenge Pass	How many times it was successfully passed

A low pass rate confirms that the traffic is indeed fraudulent. A high pass rate may indicate that you should adjust the rule conditions.

What's Next

• Handle Fraudulent Traffic — flag, redirect, or take other actions
• Set Up Scheduled Reports — automated monitoring of results
• Metrics Reference — all metrics, including Challenge Total and Challenge Pass