사용자 가이드
User GuideDeveloper GuideAPI Guide🏠
English
English
  • ☄️Learn about DFINERY
  • ⚙️Getting started with Dfinery
    • Sign Up
    • Create organizations and services
    • Setting up security
      • Setting up 2-step authentication
      • Setting up CSV downloads
    • Organization Management and Authority
      • Invite and set permissions
      • Frequently Asked Questions FAQ
    • Creating events and properties
      • Designing an Event Taxonomy
      • Testing SDK Integration
      • Testing S2S API Integration
      • Frequently Asked Questions FAQ
    • Partner Integration
      • Partner Sync (Export)
        • Creating a Pipeline
        • Frequently Asked Questions FAQ
      • HTTP API (Export)
    • Console Screen Guide
  • 📊Analysis
    • Home Dashboard
      • Frequently Asked Questions FAQ
    • Report
      • Create an Insight Report
      • Summary of Report Terms and Concepts
      • Action Common FAQ
  • 📢Action
    • Off-site Campaign
      • Push message
        • Setting up push
        • Sending push messages
        • Frequently Asked Questions FAQ
      • kakaotalk
        • Setting up a KakaoTalk sending profile
        • Notification Talk
          • Create a notification template
          • Send notification message
          • Notification Talk Indicator
        • FAQFrequently Asked Questions FAQ
      • Text message
        • Register your caller ID profile
        • 080 Rejection
        • Send a text message
        • Frequently Asked Questions FAQ
      • Informational VS Advertising
      • 🚦(Must read) Notation by consent status
      • Fatigue management
    • On-site Campaign
      • In-app messages
        • Create an in-app message
        • In-App Message Size Guide
        • Priority Management
        • Frequently Asked Questions FAQ
    • Set the purchase conversion period
      • Frequently Asked Questions FAQ
    • Campaign setup information and result details data
    • Action Common FAQ
  • 🙋Customer
    • User Profile 360
      • Frequently Asked Questions FAQ
    • Audience
      • Audience Filter Rules
      • Dynamic Audience (Parameter Update Setting)
      • Audience creation example
      • Frequently Asked Questions FAQ
  • etc.
    • Glossary
    • Frequently Asked Questions FAQ - Other Common
Powered by GitBook
LogoLogo

디파이너리 팀은 고객의 편의와 성장을 위해 최선을 다하고 있습니다.

  • 도입 문의
  • 이용 문의

디파이너리|㈜IGAWorks

On this page
  • Pre-check
  • Global Fatigue Management Settings
  • Go to the Fatigue Management tab
  • Activate toggle and enter number of times per unit time
  • Enable and disable fatigue management by campaign
  • Fatigue setting criteria
  1. Action
  2. Off-site Campaign

Fatigue management

Excessive or frequent campaign delivery can sometimes cause customer fatigue and lead to churn. Therefore, DFINERY supports CRM optimization by providing a function to limit the number of deliveries per hour for each offsite campaign channel.

Pre-check

  • Only service administrators can configure additional channel settings.

Global Fatigue Management Settings

Go to the Fatigue Management tab

Channel

Additional Settings > Channel Additional Settings > Global Settings > Fatigue Management

Activate toggle and enter number of times per unit time

After activating the toggle for the channel that requires fatigue management, please enter the maximum number of messages sent per unit time.

  • You can configure fatigue management settings for each channel, and when set, it will be applied as a default to all campaigns.

  • Fatigue management time can be set from a minimum of 24 hours (1 day) to a maximum of 336 hours (14 days).

  • The number of fatigue management times can be set from 1 to 99 times.

Enable and disable fatigue management by campaign

In some cases, some campaigns may not require fatigue management. Depending on your needs, go to the individual campaign creation page and enable or disable the toggle in the Schedule Settings field. If disabled, it will be excluded from fatigue management settings.

Fatigue setting criteria

  • Sliding Window Method The sending time moves continuously. It is updated every time it is sent and is pushed back N hours. 1 Day = Reception time + 24 Hours Example 1) When the maximum sending time is 10 per hour, only a maximum of 9 additional messages can be sent during the next hour based on the last sending time. Example 2) Assuming the fatigue management setting is 1 hour / 3 times limit

1

1 count

2

2 counts

3

3 counts

4

3 times or more *All campaigns attempted to be sent until 13:50 are restricted from being sent

5

1 time re-count

  • A user can receive a message up to {N} times during {N} periods from the time the message was received.

  • Receiving per user

  • It may take up to 10 minutes for settings to be reflected when changed.

Previous(Must read) Notation by consent statusNextOn-site Campaign

Last updated 3 months ago

12 : 50 Sent

12:51 Sent

12:52 Sent

12:53 Sending limit

13:51 Sent (Restart)

📢
✅
✅
✅
⛔
✅