From Mobitouch cube
Blacklists are a simple way to tell the system what to do when a relevant event occurs. Basically the system waits a specific time before trying to send the same content to the same user.
Mobitouch CUBE considers the following relevant events:
- Accepted: the user has successfully downloaded the content.
- Rejected: the user has specifically rejected the content.
- Ignored: the user has ignored the notification message for N-times, where N is configurable.
- Failed: the transmission of content to the specific mobile phones has failed N-times, where N is configurable.
After one of these events the Bluetooth Address of the mobile phone that was being processed is put in one of the 4 blacklists called "Accepted Blacklist", "Rejected Blacklist", "Expired Blacklist", "Failure Blacklist". The identifier of the mobile phone will stay in one (and only one) of these blacklists until a specified time interval elapses.
Blacklist time can also be set to "forever" thus avoiding a device which has undergone a specific event to be contacted again within the same campaign.
Blacklists are campaign-specific (they are reset when a new campaign start) but can be kept if a campaign is periodic (i.e. if you have a campaign that runs every Sunday, the blacklist data is not reset the 2nd Sunday when the campaign re-starts).
All these parameters however are configurable and can be set with the CMS. Blacklist timings are campaign-specific (each campaign can have its timings). If no timings are set for a campaign, the system defaults to the node-specific blacklist settings.
Blacklist Options
Blacklist persistend enabled
This flag tells the system how to behave when power-off occurs. If this flag is checked, the system periodically saves blacklist data to persistent flash memory (every 5 minutes). If it is not checked, then the system doesn't do this and a power off can clear all blacklists.
Blacklist Clear before campaign starts
This flag tells the system how to behave when running periodic campaigns or campaigns with multiple time-schedules. If it is checked, the system clears blacklist before the beginning of each new schedule or new active interval. If it is not checked then blacklist data coming from the previous schedule is re-loaded.