Customer segment attributes
The customer segment properties view in Management Center provides many attributes for defining customer segments, such as a customer's age, address, or purchase history. Customer data for each attribute are stored in specific tables in the WebSphere Commerce database.
The following tables list the attributes you can use to define customer segments in Management Center. There is one table for each tab in the customer segment properties view.
| Attribute | Description |
|---|---|
| Registration status | Target customers based on their registration status (registered
or guest). Database table: USERS.REGISTERTYPE |
| Registration date | Target customers who registered at the site on, before, or since
a specified date or number of days. Database table: USERS.REGISTRATION |
| Last registration update | Target customers who last updated their registration information
on, before, or since a specified date or number of days. Database table: USERS.REGISTRATIONUPDATE |
| Attribute | Description |
|---|---|
| Gender | Target customers based on their gender, or specifically target
those customers who have not specified. Database table: USERDEMO.GENDER |
| Current age according to supplied birth date | Target customers of a specific age or whose age falls within a
specified range. The server calculates the customer's age from the supplied birth date; therefore,
the age will remain accurate over time. Database table: USERDEMO.DATEOFBIRTH |
| Age group | Target customers whose age falls within a specified range.
Multiple ranges can be targeted by promotions or activities, and the ranges can be customized as
necessary. Database table: USERDEMO.AGE |
| Annual income | Target customers whose income falls within a specified range.
Multiple ranges can be targeted by promotions or activities, and the ranges can be customized as
necessary. Database table: USERDEMO.INCOME |
| Marital status | Target customers based on their marital status, or specifically
target those customers who have not specified. Database table: USERDEMO.MARITALSTATUS |
| Children | Target customers who have a number of children that falls within
a specified range. Multiple ranges can be targeted by promotions or activities, and the ranges can
be customized as necessary. Database table: USERDEMO.CHILDREN |
| Household size | Target customers whose household size falls within a specified
range. Multiple ranges can be targeted by promotions or activities, and the ranges can be customized
as necessary. Database table: USERDEMO.HOUSEHOLD |
| Attribute | Description |
|---|---|
| City | Target or exclude customers based on the city in which they
reside. Database table: ADDRESS.CITY |
| State or province | Target or exclude customers based on the state or province in
which they reside. Database table:ADDRESS.STATE |
| Country or region | Target or exclude customers based on the country or region in
which they reside. Database table:ADDRESS.COUNTRY |
| ZIP code or postal code | Target or exclude customers based on their ZIP or postal code.
This supports string comparison, so you can target partial codes, as long as the string starts with
the first number or character of the code. Database table: ADDRESS.ZIPCODE |
| Phone number | Target or exclude customers based on their telephone number. This
supports string comparison, so you can target area codes or specific exchanges, as long as the
string starts with the first number of the full telephone number. Database table: ADDRESS.PHONE1 Database table: ADDRESS.PHONE2 |
| Email address | Target or exclude customers based on their email address. This
supports string comparison, so you can target domain names. Database table: ADDRESS.EMAIL1 Database table:ADDRESS.EMAIL2 |
| Attribute | Description |
|---|---|
| Amount spent since registration | Target customers whose total amount spent at the store falls within a specified range. Multiple ranges can be targeted by promotions or activities, and the ranges can be customized as necessary. Note that this total only captures the amount spent on orders in the database, and may not reflect an amount spent prior to database pruning. |
| Orders | Target customers whose number of orders at the store falls within a specified range. Multiple ranges can be targeted by promotions or activities, and the ranges can be customized as necessary. |
| Last purchase date | Target customers that made a purchase from the site on, before,
or since a specified date or number of days. For example, you can target customers who have made
purchases in the last 30 days to follow-up with a coupon. Database table: USERS.LASTORDER |
| Attribute | Description |
|---|---|
| Last store visit date | Target customers that have visited the site on, before, or since
a specified date or number of days. This works similarly to the Last purchase date attribute. These
two attributes can be used in combination too, such as targeting customers that have not made a
purchase in the last 60 days, but who have visited the site in the last week. Those customers might
be looking to make a purchase, and might be good candidates for an email that gives them an
incentive to place an order. Database table: USERS.LASTSESSION |
| Job function | Target or exclude customers based on their specified job function, such as senior management, or professional. These job functions can be customized as necessary. |
| Interests | Target or exclude customers based on their specified
interests. Database table: USERDEMO.HOBBIES |
| Company name | Target or exclude customers based on their specified
employer. Database table: USERDEMO.COMPANYNAME |
| Currency | Target or exclude customers based on their preferred
currency. Database table: USERS.SETCCURR |
| Language | Target or exclude customers based on their specified preferred
language. Database table: USERS.LANGUAGE_ID |
| Preferred method of communication | Target or exclude customers based on their specified preferred
method of communication. Database table: USERPROF.PREFERREDCOMM |
The following table lists Account attributes. These attributes are applicable to B2B store models only. This data is stored as member attributes in the MBRATTR table, (with the exception of the Account and Account sales attributes, which are stored in the tables and columns indicated). Your store must populate these member attributes if you want to use them in B2B customer segments.
| Attribute | Description |
|---|---|
| Account | Target customers who belong, or do not belong, to specific
accounts. Database table: ACCOUNT.NAME |
| Account size | Target customers who belong to accounts with a particular size, as specified during account creation. |
| Account geographical location | Target customers who belong to accounts that are based in a
particular location, as specified during account creation. Database table: MBRATTR Name of member attribute: OrgEntityGeographicLocation |
| Account country or region of operation | Target customers who belong to accounts that operate in a particular location, as specified during account creation. This is distinct from the geographical location in that an American account may operate in the US, Canada, and the UK. |
| Account industry | Target customers who belong to accounts that are within a particular industry, as specified during account creation. |
| Account business | Target customers who belong to accounts that are within a particular business, as specified during account creation. Includes options like manufacturing, wholesale, and retail. |
| Account sales | Target customers who belong to accounts with an amount spent that falls within a specified range. This is the total of all orders made under the contract |