SMS subscription lists are aimed on SMS services. You can create a SMS campaign where the service will be closed to a list of users or you can use it as a contact list to send a broadcast.
The subscription lists have a name, which is useful to identify them easily when using them. The use of any string of characters is allowed as long as it meets the following conditions:
In order to create and manage a campaign based on Segmentation service, the file with the information must comply with following guidelines:
Filters can be applied to segmentation lists. Since segmentation lists require the type of data for each column to be known, lists are indexed and analyzed so fast search and filtering can be executed. Once a segmentation list has been created the Add Filter button can be used to create segments based on filters. Filters and segments created in the segmentation interface can then be used in other campaigns to send interactions only to the selected segment.
For example, the following list has 250,000 subscribers, each of whom has 7 fields:
Using the Subscription List Wizard located in Menu → Utils → Subscription List → List Wizards the data type for all the columns is automatically detected. In the parameters interface, You must select the Key column to designate which column in the file contains the values that uniquely identify the users in your list. The Analyzed column allows you to toggle search analysis for that column, when deactivated, segmentation by that field will be made only through values that exactly match the search criteria values:
The Subscription Lists interface displays that list as (please note that 250,000 records are displayed):
Clicking on the *Add Filter* button will display the filtering and segmentation interface, letting you add filters to the fields depending on the type detected or selected at creation time. In this example we are adding a filter to display subscribers with PLAN_ID of 40:
Clicking on Continue applies the filter and shows only the data for users that match the criteria, in this case we went down from 250,000 records to 231,883:
Filters can be as complex as needed. For example the following filter will only select users with a PLAN_ID of 3, a PAYMENT_METHOD different than 0, and in STATE_ID 40 or 3:
The resulting user list only contains 8,387 records: