# Frequency Capping Push notifications are a highly effective messaging channel, but sending them too frequently can lead to **faster user churn.** You can resolve this by setting up Frequency Capping, which helps you manage user fatigue levels by limiting the maximum number of notifications each user receives. ## Setting Up Frequency Capping Frequency Capping can be configured on a project basis. On the FlareLane console’s project page, you can choose between the following options: * **No limit**: No restrictions are applied to notification sending. This is the default setting. * **Set the maximum number per user**: Set a maximum limit on notifications each user can receive within a specified timeframe and track the number of sent notifications. The count resets each time you adjust the settings.

If the number of notifications exceeds the set frequency cap for a particular device, the message will not be sent, and the "Capped" count in the message statistics will increase accordingly.

Here’s what each term in the chart represents: * **Sent**: The total number of devices where the message was successfully delivered. * **Clicked**: The total number of devices that clicked on the message and were redirected to the specified URL. * **Remaining**: The total number of devices still waiting to receive the message. * **Failed**: The total number of devices where the delivery was unsuccessful. *** ## Overriding the Set Limits The Frequency Capping settings you previously configured can apply across the entire project. However, you can also configure notifications to bypass these limits. Here are examples: ### New Message You can override the frequency capping settings by checking the box under the send options in a new message. Here's an example:

### Customer Journey Automation Alternatively, you can override the frequency capping settings when making customer journeys. Simply tick the box in Send Options as shown below: