Setting up Frequency Capping
Last updated
Last updated
Knowing when not to send a message can be as critical to your messaging campaigns as knowing when to send one. There must be a balance between under- and over-engagement. And the Frequency Capping feature does exactly that.
Frequency Capping allows clients to put a hard stop on how many messages customers will receive on a daily, weekly, and monthly basis. If you are simultaneously running multiple automations and campaigns, you can use this feature to specify a limit on the number of automated messages a customer can receive in a given time period.
For example, you can impose a limit of 5 email messages in a 24-hour period, preventing customers from receiving more than 5 email messages in a day.
On the Growlytics dashboard, you can set the limit for each messaging channel: email, sms, WhatsApp, web push, etc.
For each channel, you can define the maximum number of messages that can be sent.
If the limit exceeds max allowed messages for that channel, the messages will be ignored and will not be sent to customers.
You can decide at the campaign level whether to follow 'Frequency Capping' or not. This will help you ignore frequency capping and send messages any way for transactional campaign messages.
You can use the following steps to set up frequency capping limits:
Login to your Growlytics dashboard => Click on Settings from the left menu => Click on Campaign Settings => Click on Frequency Capping Tab.
2. You will see a table like the one in the screenshot above. Here you can specify the maximum number of messages that can be sent to customers on different channels.
3. You can also set the 'Max Allowed Messages combining all the messaging channels.
While creating a campaign, on the first Basic Info step, you will see a 'Follow Frequency Capping' checkbox, set it to true if you want to follow Frequency Capping, keep it false otherwise.
While saving journey settings, you will see the 'Follow Frequency Capping' checkbox, set it to true if you want to follow Frequency Capping for the journey, keep it false otherwise.
