Documentation
Website
  • Getting Started
  • Customer Journey
    • Creating Customer Journey
    • Understanding the Journey
    • Performance Dashboard
    • Pre-built Templates
  • Channels
    • Mobile Push
    • Web Push
    • In-App Message
    • SMS/LMS
    • Webhook
  • Audience
    • Segments
    • Device Management
  • Engagement Tools
    • Dashboard
    • Message Personalization (Liquid)
    • Template
    • Sending Test Messages
    • AI Messaging
    • API Templates
    • Rate Limiting
    • Frequency Capping
    • Tracking Events
    • Inviting Members
  • Data Integration
    • User ID
    • Events
    • Tags
    • Integrating Google Tag Manager
    • Integrating Amplitude
    • Integrating Mixpanel
  • Guide for Developers
    • Mobile SDK Setup
      • Android SDK Setup
      • iOS SDK Setup
      • React Native SDK Setup
      • Flutter SDK Setup
      • Additional Setup
        • Android: FCM Setup (v1)
        • Android: Notification Icons
        • iOS: APNS Setup
        • iOS: Disable Swizzling
    • Web SDK Setup
    • REST API Reference
    • Mobile SDK Reference
    • Web SDK Reference
Powered by GitBook
On this page
  • Configuring Rate Limiting
  • How It Works In Practice
  1. Engagement Tools

Rate Limiting

PreviousAPI TemplatesNextFrequency Capping

Last updated 6 months ago

If messages, such as push notifications, are sent too rapidly, a sudden surge of traffic on the client’s server can occur, potentially leading to service outages. FlareLane's Rate Limiting feature provides an optimized speed control feature to prevent such situations and ensure smooth message delivery.

Configuring Rate Limiting

Dispatch speed control can be configured on a per-project basis. Within the FlareLane console, you can choose between two options on the project page:

  1. No limit: No restrictions are applied to the notification dispatch speed.

  2. Set the speed limit for sending messages: You can specify the number of messages to be sent per minute.

How It Works In Practice

The configured messages per minute are converted to messages per second for more stable dispatching. For example, if 1,019 messages are set to be sent per minute, it is converted to 16 messages per second by rounding down to the nearest whole number. The conversion method is as follows:

(1019 ÷ 60) = 16.98333333...

In practice, FlareLane sends 16 messages per second, totaling 960 messages per minute.

16 x 60 = 960 

In summary, messages are sent per second at a steady rate, allowing clients to maximize the use of their server resources.

Image by FlareLane