Segments: New/Edit Segment: Advanced

The Segment Advanced Settings page allows you to set special parameters for your segment.

Join Other Tables

By default, ListManager only has access to its own database tables. To access data in other tables in your database, list the table names here, separated by commas. Carriage returns are not allowed in this field, to prevent errors resulting from not separating correctly with commas. The standard members table is already included, and need not be specified. The fields in the tables specified here will be available for mail merging.

Example:

demographics.customers, demographics.info

Adding additional tables here will make their fields appear when inserting a clause.

NOTES

• A join statement must be part of your query in order for the table join to function properly. See Joining to Another Table for more information.
• If you are using MSSQL, do not use brackets when naming your external table. Example: Use dbname.dbo.tablename and not [dbname].[dbo].[tablename]

Columns to display

This setting is only relevant for testing purposes, to see what data is returned when you test your segment. If blank, only MemberID_ and EmailAddr_ will be displayed when you test your subset. These fields will always be retrieved and need not be specified. To specify additional fields, separate them with commas. Carriage returns are not allowed in this field, to prevent errors resulting from not separating correctly with commas.

Example:

domain_, fullname_

Sorting

Using an SQL "ORDER BY" clause, specify the order in which to return results.

Example:

members_.EmailAddr_ ASC

After SELECT

This setting is useful for those using ListManager with an Oracle database to tell it to use a specific index, thus improving performance. The Oracle optimizer will not always choose to use an index, even if one has been built, so this feature allows the name of the index to be added as a hint after the SQL for the subset.