Common Guide
This section provides an overview of the different integration methods available for NetFUNNEL client-side agents.
Overview
NetFUNNEL supports client-side agent integration. Different integration methods can be applied depending on the application type (web app or mobile native app).
NetFUNNEL's agent integration methods are broadly divided into two types: URL Trigger Integration and Code-based Integration.
The types of code-based integration are divided into Basic Control and Section Control methods depending on the complexity of the steps you want to apply.
For web applications, both URL navigation and button-based actions are possible, so both URL Trigger Integration and Code-based Integration (Basic Control, Section Control) are supported.
For mobile applications, URL navigation is not supported, so only Code-based Integration (Basic Control, Section Control) is supported. (Excluding hybrid apps)
Control Types
The NetFUNNEL JavaScript Agent supports three control types:
| Control Type | Purpose | Best For | Key Management |
|---|---|---|---|
| URL Trigger Integration | Controls page entry speed | Landing pages, promotion URLs, external links | Automatic key return - protect page entry |
| Code-based Integration - Basic Control | Controls action speed | Button clicks, API calls, page navigation | Key returned quickly after action completes |
| Code-based Integration - Section Control | Maintains concurrent user count | Multi-step processes, checkout flows | Key held until section exit (entire process completes) |
Control Type Comparison
URL-Triggered Integration
What it does:
- Controls how fast users can access specific pages
- Traffic control is applied automatically when URL patterns match
- Key is returned automatically when page loads
- No code changes required
Key Management: Key is returned automatically by default (data-nf-return-key).
Use cases:
- Landing page protection
- Promotion URL control
- External link defense
- Campaign page management
Example flow:
Code-based Integration - Basic Control
What it does:
- Controls how fast users can perform specific actions
- Each user gets a key when they start an action
- Key is returned quickly when the action completes
- Next user can enter only after previous user returns their key
Key Management: Key is returned immediately after the specific action completes (e.g., screen loads, API call finishes).
Use cases:
- Button click rate limiting
- API call throttling
- Login attempt control
- Screen navigation protection
Example flow:
Code-based Integration - Section Control
What it does:
- Maintains a fixed number of concurrent users in a specific section
- Users wait in queue until a slot becomes available
- Key is held until user completes the entire section
- Next user enters only when current user exits the section
Key Management: Key is held throughout the entire multi-step process, only returned when the entire section/process is complete (e.g., checkout finished, payment processed).
Use cases:
- Checkout process control
- Payment flow management
- Multi-step form completion
- Resource-intensive operations
Example flow:
Need help with decision?
Follow the diagram below to choose the appropriate integration method.
Help
Q. Can I use UTI and CBI together?
A. Yes! You can use multiple integration methods in the same application:
For more details, see FAQ.
Q. Can I use basic control and section control together?
A. Yes! You can use both code-based control types in the same application:
For more details, see FAQ.