Key takeaways
- On the AI Selena page (/selena) you set HVT/MVT/LVT thresholds, Sensitivity, Smart Filter Mode, and the Conversion Score profile.
- AI fields (thresholds, balance, interests, GA4/GTM/Metrica) are saved with a cooldown ≈ 4 hours.
- The working click-filter contour: server bot-check + Smart Traffic (SDK) + visit statuses; safe mode especially affects blocking.
- HVT/MVT/LVT thresholds in the current redirect runtime do not classify clicks — set them deliberately and read the honest block below.
Settings map
| Блок | Где | Why it is in the product |
|---|---|---|
| HVT / MVT / LVT | AI Selena → thresholds | UI segments of traffic value (points) |
| Sensitivity Level | Conservative / Balanced / Aggressive | Sensitivity profile in settings |
| Smart Filter Mode | off / safe / normal / aggressive | Filter mode on the user (users.sf_mode) |
| Conversion ideals | time, scroll, frequency | Profile for conversion_score 0–100 |
| Smart filtering | Checkbox on the link + delay/events | SDK, pending → confirm, pixels |
| Data Retention | AISelenaDaysLong 30/60/90 | Retention period; used by PII cleanup |
HVT / MVT / LVT thresholds
In the interface: High / Medium / Low Value Traffic (points). Validation on save:
- HVT — default 75, range 50–100
- MVT — default 65, range 30–89
- LVT — default 30, range 0–49
These numbers are stored in the ai_selena table. In RedirectController / SmartFilter / ConversionScoreService they are not currently read for the «allow / block the click» decision. Do not promise the client that «I set HVT=80 — and everything below 80 is cut automatically».
Sensitivity Level
AISelenaBalance: 1 = Conservative, 2 = Balanced (default), 3 = Aggressive. The field exists in the model and UI («Sensitivity Level»).
Like the HVT/MVT/LVT thresholds, balance does not change the isBot signal list and does not switch SDK branches in the current code. It is a profile setting in the Selena account, not a separate «aggression engine» on every click.
Smart Filter Mode
The mode is written to users.sf_mode (and may be taken on the link as link.sf_mode ?? user):
| Режим | Meaning in the UI | What the redirect code shows |
|---|---|---|
| off | No filtering (UI label) | It is saved; there is no separate full «turn everything off» implementation as in marketing copy |
| safe | Observation | Strong effect: bot → action would_block, without a hard block |
| normal | Normal (often the default) | Hard-bot is blocked; soft (ip/rate) with Smart Traffic may soft_pass |
| aggressive | Stricter / PoW in the UI description | The mode is saved; not all UI promises are fully wired in the client SDK |
On first enabling SF ≠ off a disclaimer is shown → sf_disclaimer_accepted_at. Conversion fields (ideals + sf_mode) are saved without the 4-hour AI-fields cooldown.
Conversion Score — the «ideal» profile
Ideal-visit settings affect the conversion_score (0–100) calculation after confirm:
- sf_ideal_time — seconds on site (1–3600, default 30)
- sf_ideal_scroll — scroll depth % (1–100, default 50)
- sf_ideal_frequency — rare / monthly / weekly / daily / frequent
Weights in ConversionScoreService: events 35%, frequency 20%, time 15%, scroll 10%, behavior 10%, fingerprint 10%.
Score is a quality metric of a confirmed visit in the Audience tab, not a separate «ban by HVT threshold».
Smart filtering on the link
Separate from the Selena page: on the link you turn on smart_traffic, delay 1–60 s (default 5), events click/scroll/form_submit/custom with AND/OR.
- The visit starts as pending; pixels wait for SDK confirm.
- Without a custom domain and without Smart Traffic, pixels on the redirect effectively do not fire.
- The «AI Selena traffic analysis» checkbox (links.ai) is saved, but is not read in redirect runtime.
Tie-in with audience collection: retargeting playbook.
4-hour cooldown
After saving AI settings (thresholds, balance, interests, integrations, retention), a repeat change is blocked for ≈ 4 hours (canSaveSettings / last_saved_at). Conversion fields (sf_ideal_*, sf_mode) can be changed without that window.
If the old UI somewhere shows «24 hours» — go by 4 hours from the current AISelena model.
What actually affects the click
- Server isBot (UA, headers, datacenter IP, rate) — before the redirect.
- sf_mode === safe → log would_block instead of block.
- Smart Traffic + SDK (delay, events, fingerprint/behavior, confirm).
- Visit statuses: bot_server / pending / confirmed / bot_filter.
- conversion_score after confirm — for Audience analysis.
HVT/MVT/LVT thresholds, Sensitivity, and audience interests are part of the Selena account; do not substitute them for the Smart Traffic and bot-signal checklist.
Detailed detect breakdown: how ClikBy and Selena catch fraud.