1 Feature Summary

This chapter describes the feature enhancements in this release.

Noteworthy Enhancements

This guide outlines the information you need to know about new or improved functionality in the Oracle CrowdTwist Loyalty and Engagement update and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, tips or considerations that you should keep in mind, and the resources available to help you.

Column Definitions

• Feature: Provides a description of the feature being delivered.

• Module Impacted: Identifies the module associated with the feature, if any.

• Scale: Identifies the size of the feature. Options are:

  • Small: These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

  • Large: These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

• Delivered: Is the new feature available for use immediately after upgrade or must the feature be enabled or configured? If no, the feature is non-disruptive to end users and action is required (detailed steps below) to make the feature ready to use.

• Customer Action Required: You must take action before these features can be used. These features are delivered disabled and you choose if and when to enable them.

Table 1-1 Noteworthy Enhancements

Feature	Scale	Delivered	Customer Action Required?
User Interface	Small	Enabled	No
Segmentation	Small	Enabled	No

User Interface

Code Reward Expiration Configuration

When configuring a code reward within CrowdTwist, you can also configure the number of days from issuance when that code expires.

The computed expiration date is available in CrowdTwist APIs and visible in the Reward History widget.

Note:

Downstream systems are responsible for confirming code validity before allowing a member to use it at point-of-sale or online. CrowdTwist does not validate code expiration.

Segmentation

Commerce Criteria

You can now create segments with commerce criteria directly in the self-service segment builder. The following is a breakdown of the five new options:

• Average Order Value

  • The average amount spent by a member in a single transaction (lifetime)

• Latest Purchase Date

  • The most recent purchase date of a member

• Purchase Count

  • The total number of purchase transactions made by a member

• Purchased SKUs

  • The SKUs that a member has/has not purchased

• Total Spend

  • The total amount spent by a member (lifetime)

Note:

Allow segments that include commerce criteria up to six hours to refresh. These are not considered real-time segments and will not count toward your real-time segment limit.