Content

A content is an object representing which files a node should dispatch during a campaign and how those files are dispatched.

A content is basically composed by:

information relative to the content type (for example whether or not it is a two-way messaging content)

Delivery Policies

Simple, the content is composed by one and only one file that is sent to every detected device.

Class of devices, the content is composed by one or more files and each file must be addressed to a different class of devices (ex. cell phones, smartphones, etc...). This policy allows to set a default file, that has to be sent when the remote mobile device is not included in other class settings. For example, in the picture below, the file 'mms1.gif' would be sent only to devices of the class 'cellular' while the file 'mms5.gif' would be sent to every device whom class can't be detected

Device identification, the content is composed by one or more files and each file must be addressed to a different subset of mobile device models. The selection of each set of device models is based on the supported features and characteristics of mobile devices (refer to Device identification for further details on how to select target models) . This policy allows to set a default file that has to be sent when the remote mobile device is not included in the other files settings. For example, you can create a content with two files: an mp3 file that has to be delivered to mobile devices that support mp3 and a midi (default) file for all others mobile devices.