Skip to main content
Version: 4.6.1-saas

Integration Methods Overview

NetFUNNEL React Native Agent supports code-based integration.

Code-based integration sets traffic control points by directly calling NetFUNNEL functions in application code. You can apply queues at precise timings such as button clicks, API calls, etc.

URL-Triggered Integration Not Supported

React Native Agent does not support URL-Triggered integration. Only code-based integration can be used.


Code-based Integration

Code-based integration provides two control types:

Basic Control

Best for: Button clicks, API calls, single-step operations

How it works:

  • Key issuance and waiting room display when start function (nfStart) is called
  • Key return when stop function (nfStop) is called
  • Manages service load by controlling entry rate

Example:

// Start
Netfunnel.nfStart(projectKey, segmentKey, callback);

// Stop
Netfunnel.nfStop(projectKey, segmentKey);

For details, refer to the Basic Control Method document.

Section Control

Best for: Payment processes, multi-step processes, maintaining concurrent user count in specific section

How it works:

  • Key issuance and waiting room display when start function (nfStartSection) is called
  • User is considered to be in active section until stop function (nfStopSection) is called
  • Maintains concurrent user count within specific section at a fixed value

Example:

// Start section
Netfunnel.nfStartSection(projectKey, segmentKey, callback);

// End section
Netfunnel.nfStopSection(projectKey, segmentKey);

For details, refer to the Section Control Method document.


Integration Method Selection Guide

When to Choose Basic Control

  • ✅ Apply queue on button click
  • ✅ Apply queue before API call
  • ✅ Single-step operations
  • ✅ When entry rate control is needed

When to Choose Section Control

  • ✅ Apply queue to entire payment process
  • ✅ Multi-step processes (e.g., signup → information entry → completion)
  • ✅ When concurrent user count must be maintained at a constant value in specific section
  • ✅ When next user's entry must be blocked while user remains in specific section