Session Time Filter
What it detects
Section titled “What it detects”Conversions that happen nearly instantly after a click suggest automated injection. Conversions that arrive days or weeks after a click suggest cookie stuffing. The Session Time Filter rejects both patterns by enforcing a valid time window between click and conversion.
How it works
Section titled “How it works”Integr8 measures the session time — the duration between the recorded click timestamp and the conversion timestamp. If the session time falls below min_session_time or above max_session_time, the conversion is rejected.
The filter applies to conversions only. Clicks are not evaluated.
Configuration
Section titled “Configuration”Navigate to Offers > Fraud Detection Groups > select a filter group > Session Time.
| Parameter | Default | Range | Description |
|---|---|---|---|
min_session_time |
15 sec | 0 sec–24 h | Minimum allowed time between click and conversion |
max_session_time |
24 h | 1 min–90 days | Maximum allowed time between click and conversion |
Both thresholds can be set in days, hours, minutes, and seconds.
What happens when triggered
Section titled “What happens when triggered”When a conversion falls outside the configured window:
- The conversion is rejected with
fraud_reason: session_time_filter. - The originating click is not attributed.
- The event is logged and visible in Reports > Conversion and Events Report.
Set min_session_time based on realistic user behavior for your offer type. A lead generation form might convert in under 60 seconds legitimately; a mobile app install typically takes 2–5 minutes. Too aggressive a minimum will block real conversions.
Related filters
Section titled “Related filters”- Low Session Time Anomaly — dynamically detects publishers with abnormal proportions of short sessions
- Click Spam — detects cookie dropping and long-session fraud at the publisher level