Domains & integrations
Nevect Protect
Configure campaign-level detection and review the resulting traffic records.
Check availability
Confirm the installation's license and the Protect state before configuring detection. An expired or disabled entitlement may affect licensed functions independently of the campaign's normal settings.
Configure a campaign
Open the campaign editor and expand Nevect Protect. Review the available detection methods, thresholds and modes. Start with a deliberate limited change and keep the existing routing configuration recorded.
Research and enforcement
A research or passive setting lets you inspect detection results before relying on them for routing, where that mode is available. Enforcement can change the visitor's destination. Make the intended behavior explicit and verify the legitimate visitor path as well as a detection case you can safely reproduce.
Review results
Inspect the campaign's bot or detection fields and click-level data. Consider the complete request context; a single signal is not proof of a particular user's intent. Adjust thresholds only after understanding the recorded values.
Interaction with other settings
Campaign rules, other filters and Protect can all influence the final route. Check which decision acted first and keep a usable default path. Optional external services have separate accounts and entitlements.
If it stops working
Check license state, module connectivity and the exact error before changing unrelated campaign settings. Contact support with the Nevect version, time and affected campaign; keep credentials and private visitor data out of the report.