Attributes for Responsys Mobile App behavior filters

Important: Responsys behavior filter types are available only if the Responsys integration is configured for your CX Audience account. For questions about your CX Audience account's integration configurations, see your Account Administrator.

For Responsys behavior filters, the list you have selected must also be the one configured in the Responsys integrations settings to receive the Responsys behavioral data. The message "Responsys Integration Enabled" is displayed on the Manage Customer Data page when that list is selected, and you can quickly identify it in the Change List drop-down list by the check mark by the list name.

Responsys Mobile App behavior filter attributes

Important: Data available only if the Mobile App channel is enabled for your Oracle Responsys account.

When creating Mobile App behavior filters, you can include Device Profile attributes or Mobile App behavior attributes.

Device Profile attributes

Device Profile attributes' criteria include the following fields from the App Channel List:

  • 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.
  • CHANNEL_PERMISSION_STATUS_: Indicates whether the user has opted in to receive push notification from this device. Contains "I" when the device is Opted-In and "O" when the device is Opted-Out.
  • LOCALE_ : Locale of the device. Usually expressed as a combination of the two character ISO language code and the two character ISO country code.
  • 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.
  • DEVICE_ID_ : A unique key for a mobile app on a specific device, generated upon first run of the mobile app. This means that different apps on the same device will have different device IDs. This ID changes when a mobile app is uninstalled and re-installed.
  • APP_VERSION_ : Last known app version on the device.
  • CARRIER_ : Indicates the service carrier code, which is sent by the mobile platform.
  • CHANNEL_DELIVERABILITY_STATUS_ : Indicates whether an app is currently installed on the device ("D" - Deliverable) or if the device can no longer be reached, such as when the app has been uninstalled on a device ("U" - Undeliverable).
  • 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_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 when the mobile app is first run on the device, which is when Responsys detects that the mobile app was installed.
  • MOBILE_COUNTRY_CODE_ : Country code of the device. Populated when available.
  • OS_VERSION_: Operating system version of the device.
  • PLATFORM_TYPE_— Platform of the device. Values are:
    • APNS - Apple iOS platform
    • SAPNS – Apple iOS Development platform
    • GCM - Google Android platform
    • WNS - Windows platform (Legacy item, not currently supported by Responsys but may be present in some App Channel List records)
  • 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. When blank, the user is unknown. Use this field to find devices related to known users.
  • SCREEN_HEIGHT_ : Screen height of the device, in pixels.
  • SCREEN_WIDTH_ : Screen width of the device, in pixels.
  • DEVICE_MODEL_ : Model identifier of the device.
  • MANUFACTURER_ : Device manufacturer.
  • TIME_ZONE_ : Time zone of the device.
  • UPDATED_AT_DATE_ : Date when the mobile app last communicated with the Responsys system; this may be due to a user interaction or other cause (such as background location update).

Push behavior attributes—target recipients based on the count and timing of the most recent customer Mobile App interaction:

  • Push Sent
  • Push Bounced
  • Push Opened
  • Push Clicked
  • Push Converted

Tips for creating filter conditions

When specifying filter conditions, keep in mind the following:

  • Drag and drop the behavior table from the Custom tables column to the Custom Table Attributes region. You can include the table multiple times when building your conditions.
  • Click the Refine icon to add the criteria from the segment table. For example, you would see criteria such as CAMPAIGN_NAME and MARKETING_PROGRAM. You can include up to ten criteria for the "Where" part of each table.
  • Form your conditions by selecting the operator and the value. The AND and OR operators will be the same between tables and within a table's "Where" statement. If you have a table for each segment, and then change AND to OR between the first two, all of the ANDs will change to ORs. The same occurs within a table.
  • For your criteria conditions, click the value field to view the available choices. For example, if you choose CAMPAIGN_NAME as one of your criteria, and then click the field where you specify the value, the list of campaign names from your Responsys account is displayed. If you know the value you want to select, start typing it in the field, and the list will automatically filter itself to match what you type. If you choose "matches one of" for your operator, you will be able to select one or more choices in the list.
  • The "does not contain" condition applies only to records that contain a value, not for records with a null value. This means that your result set will include records that contain any value except the specified one, but not records with no values. For example, the rule “State does not contain California" will include records in New York, Pennsylvania, and Texas, but not records in California nor ones that contain no value. To include empty records as well, add OR "State" - "is null” to the rule.
  • "By Date" condition date fields are all initially set to the current date. The “Between” condition includes the first and last dates of the defined date range. By default, both fields are set to the current date.

    Note: SQL queries using the BETWEEN condition do not include the final day in a date range. To ensure consistency, add a + 1 to the SQL end date.

Learn more

Using filters in CX Audience

Creating filters

Managing filters

Audiences