Filter Attributes

Note: This topic also applies to classic filters. Your account may still have classic filters if it was provisioned before 19C. If you have an account without Audience Designer and would like this feature enabled, please log in to My Oracle Support and create a service request. When Audience Designer is enabled for an account, existing classic filters can still be run, edited, and saved as another classic filter, but new classic filter cannot be created in the Filter Designer.

Filter attributes fall into one of the following categories:

Profile data
System-defined fields such as recipient geographic data, and custom fields such as gender.
Recency
Dates of the most recent interactions, such as Last Sent Date.
Interaction
Behavior, such as Opened an email or Clicked a link.
Table membership
A Profile Extension Table is a logical extension of your main list. This contains additional behavioral, demographic, or profile preference characteristics of your contacts. Like your main list, each customer in a profile extension table is uniquely identified by a RIID_.
Program
A recipients’ presence in a program.
Import
A recipient’s presence in a specific import load.

Note: The Filter Designer does not support tables that include fields of the Maximum Text Field (to 4000 chars*) data type. As a result, you will not be able to use any table that includes such fields.

List of filter attributes

After clicking Create Filter and selecting whether to create a List filter, App Channel List filter (if Mobile App is enabled for your account), or a Web Push filter (if Web Push is enabled for your account), you can select which type of attributes you want to use:

Profile data
Email behavior
Form behavior
Web behavior
SMS behavior
Push behavior (only available if you select Create App Channel List Filter)
Web Push behavior (only available if you select Create Web Push Filter)
Others

Profile data filter attributes

Profile attributes

You will see Profile attributes if you select Profile data for a List Filter, App Channel List Filter, or Web Push Filter.

These include all system-defined fields, as well as any custom-defined fields in your list. For a list of system-defined fields, see System-Defined List Fields.

Note: An asterisk (*) indicates an indexed attribute. These attributes are fields optimized for queries used to generate the filter result set. You index fields when creating or editing a table schema (i.e. the structure of your Profile table or Profile Extensions).

Attributes from any Profile Extension are displayed under a separate heading.

App Channel attributes

You will see App Channel attributes if you select Profile data for an App Channel List Filter.

Important: App Channel is available only if Mobile App is enabled for your account.

ADMIN_AREA1_: last known geographical classification of the device, such as State, Province, and Region. You can use this attribute to geo-target your campaigns.
Important: Make sure to get explicit consent from your users to log this attribute.
ADMIN_AREA2_: last known sub-geographical classification of the device, such as County, or District. You can use this attribute to geo-target your campaigns.
Important: Make sure to get explicit consent from your users to log this attribute.
API_KEY_: unique identifier of an installed app. Use this field to target recipients by app.
APP_ID_: App Id / Mobile App Identifier of the app installed on the device.
APP_LOCATION_PERMISSION_: indicates whether or not the app user has granted the app access to location services on the device. Learn more about the possible values for this filter attribute.
APP_VERSION_: last known app version on the device.
CARRIER_: service carrier of the device.
CHANNEL_DELIVERABILITY_STATUS_: indicates whether an app is currently. installed or has been uninstalled on a device.
CHANNEL_PERMISSION_STATUS_: indicates whether the user has opted in to receive push notification from this device. Learn more about the possible values for this filter attribute.
CREATED_DATE_: date and Time when the record is created in Responsys. This attribute can also be used to create a segment of users that were first registered by Oracle Responsys at a specific time, on a certain day, or over a certain period of time.
DEVICE_CITY_: last known city of the device. You can use this attribute to geo-target your campaigns.
Important: Make sure to get explicit consent from your users to log this attribute.
DEVICE_COUNTRY_CODE_: last known country code of the device. You can use this attribute to geo-target your campaigns.
Important: Make sure to get explicit consent from your users to log this attribute.
DEVICE_MODEL_: the model of the device.
DEVICE_POSTAL_CODE_: last known postal or zip code of the device. You can use this attribute to geo-target your campaigns.
Important: Make sure to get explicit consent from your users to log this attribute.
INSTALLED_AT_DATE_: date the app was installed on the device.
LOCALE_: locale of the device.
MOBILE_COUNTRY_CODE_: country code of the device.
OS_VERSION_: OS version of the device.
PLATFORM_TYPE_: platform of the device.
PROFILE_RIID_: RIID of a known user. For known users, the PROFILE_RIID field in the App Channel List is set to the corresponding RIID in Profile List. Use this field to find devices related to known users.
PUSH_PERM_BADGES_: This column indicates whether the iOS user has opted in to App Icon Badging on this iOS device. This could be set to either I (Opted-In) or O (Opted-Out), to reflect the user preferences on the iOS device. Learn more about the possible values for this filter attribute.
Note: This field is only applicable to iOS devices.
PUSH_PERM_AUTH_STATUS_: When an iOS app implements iOS Provisional Authorization, this column indicates whether the iOS user is still in the Provisional Authorization state (P) or not. When an iOS app is installed with Provisional Authorization, the application is automatically opted-in to Push Notifications and is provisionally authorized to "Deliver Quietly" (that is to only share non-interruptive notifications with the user), and Push Notifications do not interrupt the user by appearing on the device's lock screen or as banners. For such iOS apps, this column is set to P (Provisionally Authorized) when the user is still Provisionally Authorized and has not updated Push Notification permissions on the device after app installation. The purpose of this column is to let marketers take decisions based on whether or not a certain user is Provisionally Authorized. Learn more about the possible values for this filter attribute.
Note: This field is only applicable to iOS devices.
RIID_: Oracle Responsys recipient ID for the device.
SCREEN_HEIGHT_: screen height of the device, in pixels.
SCREEN_WIDTH_: screen width of the device, in pixels.
SDK_VERSION_: Oracle Responsys Mobile App SDK version.
TIME_ZONE_: time zone of the device.
UPDATED_AT_DATE_: date the app was updated on the device.
USER_IDENTIFIER_: for logged in users, it contains the value of the USER_IDENTIFIER (match key) from the mobile app. For logged out users, it contains null. Used when the mobile app retrieves a logged in user’s Message Center messages from Responsys. This attribute can also be used to create segments of logged-in or logged-out users.

Web Push Channel attributes

You will see Web Push Channel attributes if you select Profile data for a Web Push Filter.

Important: Web Push Channel is available only if Web Push and Audience Designer are enabled for your account.

RIID_: RIID_ of Record in Web App Channel List.
PROFILE_RIID_: Profile List RIID_ of the Known User.
CHANNEL_PERMISSION_STATUS_: Web Push Permission Status from the End User (Opted In or Opted Out).
CHANNEL_DELIVERABILITY_STATUS_: Web Push Deliverability Status for this End User. Possible values are D and U.
CHANNEL_PERMISSION_REASON_: Web Push Permission Reason.
CHANNEL_PERM_DATE_: Log the Date / Time whenever the Web Push Permission Status is updated.
CREATED_DATE_: Date and Time when the record is created in Responsys.
APP_ID_: Application ID. Any number of Web Push apps (APP_ID_) can be associated with the same Web Push Channel list
API_KEY_: Identifies the platform for the Web Push app.
PLATFORM_TYPE_: Identifies the user's platform type. Open standard-compliant browsers identified by platform type standard.
VISITOR_ID_: Every visitor to the Website will be assigned a unique Visitor ID.
REGISTRATION_UPDATED_DT_: This is the date when the website last communicated with the Responsys system; this may be due to a user interaction or other cause (such as background location update).
FIRST_OPT_IN_AT_DATE_: Date / Time when the End User first Opted Into Web Push on the Browser.
APP_VERSION_: Version of the website that this User last visited.
SDK_VERSION_: Oracle Web Push Cloud Service SDK version.
BROWSER_: Browser name being used when the last registration was received.
BROWSER_VERSION_: The browser version being used when the last registration was received.
OS_TYPE_: The operating system being used by the end user.
OS_VERSION_: The operating system version.
MANUFACTURER_: The device manufacturer.
DEVICE_MODEL_: Model identifier of the device.
SCREEN_WIDTH_: Screen width of devices, in pixels.
SCREEN_HEIGHT_: Screen height of device, in pixels.
SCREEN_DENSITY_: Screen density multiplier.
DEVICE_LOC_PERM_STATUS_: Location Permission Status indicates whether the user has given the Website Location Service Permission. Values for this field are NO_SUPPORT, NOT_DETERMINED, ALLOWED, NOT_ALLOWED, and Empty / NULL value.
DEVICE_COUNTRY_CODE_: Last known country code of the device. You can use this attribute to geo-target your campaigns.
DEVICE_CITY_: Last known city of the device. You can use this attribute to geo-target your campaigns.
DEVICE_POSTAL_CODE_: Last known postal or zip code of the device. You can use this attribute to geo-target your campaigns.
ADMIN_AREA1_: Last known geographical classification of the device, such as State, Province, and Region. You can use this attribute to geo-target your campaigns.
ADMIN_AREA2_: Last known sub-geographical classification of the device, such as County, or District. You can use this attribute to geo-target your campaigns.
LOCALE_: This identifies the locale / language that has been set by the user in the browser settings.
TIME_ZONE_: Time zone of the device.
EXT_DEVICE_TRACKING_ID_: Identifier for data captured by other SDKs, such as external analytics data about a device.
IP_ADDRESS_: IP of the device.
USER_IDENTIFIER_: For logged in users, it contains the value of the USER_IDENTIFIER (match key) from the mobile app. For logged out users, it contains null.

Table membership attributes

Members of table

Use the attribute to target members of a specific profile extension table (PET). For Classic Filters, this attribute is available under the Import Attributes group.

Email behavior filter attributes

Email Recency Attributes

Use these attributes to target recipients based on the timing of the most recent customer interaction:

Last sent date
Last bounce date
Last open date
Last click date
Last conversion date
Last modified date

Email Interaction Attributes

Use these attributes to target recipients based on their behavior and related activities:

Sent
Skipped
Bounced
Opened
Clicked
Converted
Purchased
Cumulatively Purchased

Form behavior attributes

Use these attributes to target recipients based on their form behavior:

Viewed Form: target recipients based on when they viewed a form.
Submitted Form: target recipients based on when they submitted a form.

For Classic Filters, these attributes are grouped with Email Interaction attributes.

SMS behavior filter attributes

Important: Available only if Oracle Responsys SMS is enabled for your account.

SMS Recency Attributes

Use these attributes to target recipients based on recent SMS interactions, such as SMS Sent and SMS Clicked. The following attributes are available:

Last SMS sent date
Last SMS received date
Last SMS link click date
Last SMS conversion date
Last SMS purchase date

SMS Interaction Attributes

Use these attributes to target recipients based on recent SMS interactions:

SMS Sent
SMS Received
SMS Clicked
SMS Converted
SMS Purchased
SMS Delivered (supported for simple filters design only)

Web behavior filter attributes

Web Recency Attributes

Use these attributes to target recipients based on their web behavior:

Last abandoned date
Last browsed date
Last purchased date

This section might also include Partner Data: such as last abandoned date, last browsed date, and last purchased date: or Web Analytics, if available for your account.

Push behavior filter attributes

Available if you selected Create App Channel List Filter.

Important: App Channel is available only if Mobile App is enabled for your account.

Push Recency Attributes

Use these attributes to target recipients based on their mobile behavior:

Last Push sent date
Last Push bounce date
Last Push opened date
Last Push Button click date (these interactions occur when a mobile app user clicks an Interactive Notification button in a Push notification)
Last Push click date
Last Push conversion date
Last App Uninstall date
Last Msg. Center sent date

Push Interaction Attributes

Use these attributes to target recipients based on recent Push interactions:

Push Sent
Push Opened
Push Clicked
Push Converted
Push Skipped
Push Bounced
Msg. Center Sent
App Uninstalled

Web Push behavior filter attributes

Important: Web Push Channel is available only if Web Push and Audience Designer are enabled for your account. These attributes are available for simple filters only.

Available if you selected Create Web Push Filter.

Web Push Recency attributes

Last Web Push sent date
Last Web Push skip date
Last Web Push bounce date
Last Web Push open date
Last Web Push conversion date
Last Web Push purchase date
Last Web Push close date
Last Web Push button click date

Web Push Interaction attributes

Web Push Sent
Web Push Skipped
Web Push Failed
Web Push Bounced
Web Push Opened
Web Push Converted
Web Push Purchased
Web Push Cumulatively Purchased
Web Push Closed
Web Push Button Clicked

Others filter attributes

Program Attributes

Use these attributes to recipients based on their presence or absence in a published program:

In Program
Entered Program - Only available if enabled for your account
Note: This attribute is not available in the new filter designer.
Ended Program - Only available if enabled for your account
Note: This attribute is not available in the new filter designer.

For Classic Filters, these attributes are grouped with Email Interaction attributes.

Import Attributes

These are useful in filters based on how and when customer data was loaded from external files. Examples include Created in load and Members of load. When adding one of these attributes to the rule, specify which load you want to use in the rule. You can use the Member of table choice to locate individuals who are listed in a Profile Extension Table. For example, to locate female customers who live in California and are also listed in a Profile Extension Table.

Target recipients based on how and when customer data was loaded from external files:

Created in load
Last modified in load
Members of load

Display Cookie Recency Attributes

Use this attribute to select Last cookie refresh date as a filter attribute.

Device Targeting Attributes

Note: These attributes are only available for Classic Filters.

Use these attributes to target customers based on device parameters such as operating system, browser, device type, and operating system vendor. Note that the query might return a recipient more than once. This is because these attributes capture the recipient-device combination. For example, if a recipient opened a message on a mobile phone and then on a tablet, the recipient will be returned twice. To get results for email recency, specify Any device type and Any time conditions.

The following attributes are available:

Note: Responsys uses a data device detection framework that allows us to detect a large number of devices and their attributes with improved accuracy. The values of various device attributes display differently than past legacy device attributes. Legacy device attributes are still available but will be deprecated in the future. If a filter is already created with device data, you can still open and modify an existing filter condition. You cannot, however, save both legacy and newer device data conditions at the same time in a classic filter.

Last clicked on (Legacy Data)
Last opened on (Legacy Data)
Last clicked on
Last opened on

Recency and interaction attributes and their data sources

The following table provides information about data sources for recency and interaction filter attributes.

Category	Filter Attributes	Data Source
Recency¹	Last sent date
	Last bounce date
	Last open date
	Last click date
	Last conversion date	Responsys Conversion Tracking
	Last modified date
	Last abandoned date	Adobe Analytics Integration³
	Last browsed date	Adobe Analytics Integration3
	Last purchased date	Adobe Analytics Integration3
Interaction²	Sent
	Skipped
	Bounced
	Opened
	Clicked
	Converted	Responsys Conversion Tracking
	Purchased
	Cumulative Purchased	Responsys Conversion Tracking
	Viewed Form
	Submitted Form
	Entered Program Note: This attribute is not available in the new filter designer.
	In Program	Program Entry Table
	Ended Program Note: This attribute is not available in the new filter designer.
	Is/Is not in Program

¹ Recency attribute data is aggregated by user (profile RIID and device, if applicable). It is updated when there is a new recency event. For example, if a recipient clicked a link in an email message on April 9, 2020, that date is recorded as the Last Click Date. If they clicked a link in another email message on June 14, 2020, that date replaces the data as the Last Click Date. Recency data is available from the time your organization's Responsys account became active. Recency data is retained for profile RIIDs as long as your Oracle Responsys account exists, unless you delete a recipient's profile RIID from the system.

² Interaction data is available depending on how you define your filter:

If the filter condition refers to a specific campaign, link, form, or program, or a specific categorization of one of those: You can only define attributes when the event’s occurrence was within 180 days of the time the filter is executed. Responsys retains this detailed behavioral data for 180 days, as part of our standard data retention policy. For example, a filter that looks for recipients who clicked a link in the campaign named MyCampaign would only be able to look back a maximum of 180 days.
When no specific campaign, link, form, program, or a categorization of one of those is designated: Your filter can reach beyond the 180-day time window, as those statistics are retained for profile RIIDs as long as your Oracle Responsys account exists, unless you delete a recipient's profile RIID from the system. For example, a filter that looks for recipients who clicked any links (sent to them from your organization's Responsys account) "Anytime" could find recipients who clicked a link further in the past than 180 days.

³ These Recency attributes are standard web events tracked by Adobe Analytics. You can use them to build filters that target Web behaviors. You can also combine web events tracked by Adobe Analytics with email events that are tracked by Responsys. This allows you to request all contacts who have clicked in the last 30 days and have also abandoned in the last 2 days. Or, you can filter for all contacts who have not purchased in the last 6 months, but have clicked in the last 7 days. You must set up this aggregated data in Connect.

For general information on filter data retention policy in Responsys, see the My Oracle Support knowledge base article What is the Data Retention Policy for Filters? (Doc ID 1774691.1).