Domains & integrations
Other external traffic filters
Configure an available provider using its own credentials and response contract.
Check the available integration
Open the campaign's Integrations controls and the relevant provider settings. Only configure a provider that is actually offered by your installation and available in your account. External services set their own eligibility, credentials and charges.
Configure the provider
Obtain the required key, endpoint or stream configuration from that provider. Enter it in the dedicated integration fields. Check whether the service expects a server-side request, a redirect or page code; these approaches are not interchangeable.
Map the outcome
Understand which provider response is considered a match and how the campaign should route it. Keep a valid fallback for errors or unavailable results. Avoid enabling several new filters at once because their combined result becomes harder to explain.
Test the real request path
Use a controlled campaign visit. Compare the tracker record, provider record and final destination. Verify that visitor properties and parameters survive any intermediate redirect.
Investigate failures
Check account validity and service response before modifying tracker rules. A generic timeout or API error is not a classification result. Contact the provider for its service-side error and Nevect support for the tracker's integration behavior, without sharing private keys.