Oracle CrowdTwist has introduced the User Profile v3 API, a faster and more efficient way to retrieve member data from your Oracle CrowdTwist environment.

This new version lets you to specify optional include parameters, so the API returns only the data your application needs. By limiting the response payload, integrations can improve performance and reduce unnecessary data transfer.

Available include options include:

Integrated systems with valid API Keys can use this endpoint.

For implementation details along with request and payload examples, see the User Profile v3 API documentation.

Oracle CrowdTwist now integrates with the Olo Ordering Platform. Using Olo’s Order Closed event, qualifying orders are converted into CrowdTwist Purchase transactions in real time. The integration also supports Olo’s Test event to assist with setup and validation.

The Oracle CrowdTwist Control Center Settings experience has been updated with a modernized interface built on the latest Oracle APEX framework. This release consolidates and reorganizes administrative settings into a more intuitive experience while maintaining existing functionality. In addition to the updated user experience, several new administration capabilities have been introduced to improve configuration and user management workflows. The following updates are exclusive to New Control Center Settings pages.

A new Badge Management page is now available within Settings, which serves as the centralized global settings management page for Badges.

This change allows access to the Badges page directly from the new Oracle Apex interface homepage.

All program administrators that create or view Badges will require a Role with appropriate read or write permissions to access the Badges feature.

The following sections contain more information on Badge Custom Attributes.

User Management and the new User Roles feature have been enabled under Settings in the new Oracle Apex interface.

Roles allow administrators to create and manage reusable permission sets that can be assigned to Control Center users. Instead of configuring permissions individually for each user, administrators can now define permissions at the role level and assign users to the appropriate role. User Roles will enable faster user onboarding, consistent permission assignment across teams, and reduce the potential for erroneous permission assignments.

Every program will begin with six standardized roles representing common Control Center access levels: Administrator, Program Manager, Customer Service Manager, Customer Service Agent, Data Analyst, and No Access.

Existing Control Center users have been migrated to a standard role when their current permission set exactly matches one. If no standard role matches exactly, a custom role was created with the same permission set.

Client admins should review User Role assignments and manage roles going forward. Custom roles can be created, modified, or cloned as needed.

Access to User Roles requires the appropriate Settings and User Roles permissions.

This change aligns user administration with other platform-level configuration settings and provides a more consistent navigation experience.

The introduction of Custom Badge Attributes allows tracking of badge events with custom detail across the following data types: Integer, String, Date, Boolean, Decimal.

Easily filter and sort on Badges based on business specific criteria. For example, Badges from 2025 onwards and Badges with the Attribute Name "Badge_Type" and value "Streak."

All program administrators that create or view Badges will require a Role with appropriate read or write permissions to access the Badges Custom Attributes.