Skip to main content

Cheetah Loyalty Release Notes

  • Updated

Detailed information about the latest releases of Cheetah Loyalty.

Loyalty Version 22.0 Release Notes

Major Feature: Multiple Language Campaigns

This enhancement has been enabled in preview mode for the current release, meaning that it can be deployed into customer staging environments for assessment.

Background

Marketers very often run campaigns across multiple markets meaning that content
must be provided in multiple languages or locales*.
Currently, content objects such as Offers, Rewards and Challenges can only be
configured in a single language.
This results in complexity for the marketer as they must configure one duplicate
object for each language with no easy mechanism to input translations. Categories are assigned to each object so that calling applications such as Mobile Apps and websites know which object to target for the required language.
It also results in complexity for the data analyst since responses to objects such as
multi question surveys are received in multiple languages and therefore need to be
translated to a single language in order to conduct data analysis.

 

Solution

A major content management enhancement to Offers, Challenges and Rewards so that:

  • marketers can more easily configure and manage multiple language campaigns
  • data analysts can easily report on multiple language campaigns

This initial release includes support for:

  • All Offer types
  • All Challenge types except Ratings, Multiple Choice and Text Surveys since they
    are covered under Multi Question Surveys
  • All Reward types
    The solution does not currently support Punch Cards, Badges and Wallet

Availability

This enhancement can be made available in staging environments upon request to all customers who upgrade to Release 22.0.0. Please contact your Cheetah Representative.
Where campaigns are already in operation across multiple languages / locales, please discuss with your Cheetah representative to assess any actions required to transition to the new approach.


Updated Member API documentation has been published to the CES Help Center here


Details on how to configure the required languages / locales in Program Settings is here under "Member Content Locales"

Other online help updates have been completed in the applicable sections.


Supported Use Cases by Persona, via the Loyalty UI

Admin:

  • Configure the program to support the required languages and/or locales
  • Set a default language to serve as the “stored” language used for data analysis
    and to return when requested language is not configured

Marketer:

  • Create new content objects and easily configure member facing text or other translatable content** in the languages / locales configured for the program
  • Export configured member facing text from a single content object in the correct
    file structure to enable addition of all translations applicable to the defined
    object and configured languages
  • Import translations created offline for a single Content Object using the
    previously exported file
  • Preview and amend content for each language from within the Content Object.

Data Analyst:

  • Analyze responses received in multiple languages without manual intervention
    to translate and aggregate responses
  • Analyze data about the languages / locales from which the responses were
    received

Member:

  • Calling application (website or mobile application) determines the required
    language and requests it via the Member API

* locale means a language and its associated region, so that regional variations in languages can be
accounted for where required, e.g. French (France) French (Senegal) or English (US) English (UK) English (Canada). Where the term language is used alone in this document, the term locale applies equally.

** translatable content means content other than member facing text that needs to be different due to language / currency / clothing sizing differences by locale. If content varies for any other reason, it is treated as a different campaign.

 

Prevent “Double Dipping” with POS Integration

Background

Where Loyalty programs use multiple channels or methods to submit transactions, and each channel uses different unique identifiers, there can be a risk of points being accrued to an account twice from duplicate orders.

Solution

Introduction of a globally unique identifier for use on Cheetah orders and for
eCommerce and POS integrations, through both the POS API and Sparkfly API.
For online ordering flows the eCommerce system can submit an order both to Cheetah directly, and to the Point of Sale system for fulfilment that in turn relays it to Cheetah after fulfilment. This means that Cheetah receives the order twice.
The presence of a globally unique identifier allows Cheetah to recognize a single order coming through both channels and therefore is able to prevent creating a duplicate order.
Details on how to use this new functionality will be available in online help later this
month.

Availability

This enhancement is available to all customers upgrading to this release. 


Notable Fixes

  • Added system retry support to SVS Gift Card integration.
  • Added support to get Vantiv Gift Card balance when getting a Gift Card by Id.
  • Added support for Gift Cards to be returned when using Sparkfly integration with staff-selected rewards.
  • Fixed an issue where points were incorrectly calculated when an OLO order included a non-Cheetah discount.
  • Fixed an issue where Cheetah coupon offer discounts were incorrectly calculated when an Aloha discount was applied to the order.
  • Fixed an issue where Triggered Actions caused an unexpected Tier change.
  • Fixed an issue where admin user roles were incorrectly assigned when authenticated via an external Auth Provider.

 

Loyalty Version 16.0 Release Notes

Configurable Point of Sale Message (via Sparkfly)

Background

When a loyalty program Member is making a purchase, such as paying a bill at a  restaurant, the server can enhance the customer experience if they can view details of  the Member’s account. For example:  

  • Advising the Member of their current points balance enables the Member to  make the decision whether to redeem their points.  
  • Status and lifetime value information provide the server with context for  interacting with the Member.  
  • Displaying rewards available to the Member enables the server to provide  personalized service by helping the Member use their rewards, increasing  emotional loyalty. 

Solution

This release introduces a new Program Setting called “Discount Display Message  Content.” This feature is intended for Loyalty programs that use our Point of Sale (POS)  integration via the Sparkfly POS system. 

This new feature enables a marketer to configure a template for a pop-up message to  display at the POS when the Member is added to the check or bill.  

Optionally, you can configure the POS message to utilize a “relative” time zone when  displaying Offer expiry times. Loyalty program Members register with the program in the  specific time zone according to their residential address. However, for programs that  operate across multiple time zones, redeeming an Offer could take place in a different  time zone. If an Offer is being redeemed in a different time zone than the Member’s  residence, the exact expiry date/time can be adjusted accordingly. For example, let’s say  a Member has traveled to a different time zone, and they want to redeem an Offer that  expires at midnight. The Offer will expire at midnight local time, as opposed to the time  zone in which the Member resides. 

For instructions on configuring the POS message template, please see Appendix I in the PDF file "Version 16.0" attached below. This enhancement is available to all Cheetah Loyalty customers upon upgrade to Release 16

 

OAuth Application Enhancement for JSON Web Tokens

Background

OAuth is a protocol that lets external apps request authorization to access Member  data, such as Loyalty Member Profiles. OAuth enables that authorization to be  monitored, throttled, or revoked at any time.  

A registered OAuth application in the Loyalty platform is assigned a unique Client ID and  Client Secret, which can be used by the client application. For example, mobile apps or  websites can request authorization to Member data via Cheetah Member and Program  APIs. 

For Cheetah Loyalty, some applications use JSON Web Tokens (JWT) for authenticated  API access to the Loyalty Member Profiles or other Member data. A JWT is a public key or  standard way of encrypting and decrypting data. This method is used by some  applications for data sent from an external application via API, to enable OAuth  authenticated access to data in the receiving application, in this case Cheetah Loyalty. 

The sending application “signs” the JWT string, and the consuming application, Cheetah  Loyalty, verifies that signature using a public certificate provided by the sending  application. 

Upon verification, the platform will decode and accept the data; however, the data can  be decoded without verifying the signature. Therefore, no sensitive or Personal  Identifying Information (PII), such as email address, password, or credit card details,  should be sent using JWT. 

Within the Loyalty platform, you can manage your OAuth configurations on the Admin >  Access > OAuth Applications screen. You can find additional information about this screen within the Loyalty Online here.  

 

Solution

Additional support for OAuth using JWT has been added in this release of Cheetah  Loyalty. The platform now supports the use of a shared secret key with a specific  encryption algorithm namely “HS256.” 

Cheetah Loyalty is now able to decrypt the HS256 algorithm for applications that use it  for OAuth, using a shared secret key. 

This enhancement is available to all Cheetah Loyalty customers using OAuth with JWT upon  upgrade to Release 16.

 

Configurable Landing Page

Background

Currently, the Dashboard is displayed when a user signs into Cheetah Loyalty. However,  some roles may prefer a different landing page. For example, it may be beneficial for  Customer Service Representatives to automatically view the Member CSR screen when  logging into the platform, as this is the screen where they do most of their work. 

 

Solution

This release of Cheetah Loyalty now offers the following three choices for the landing  page when users log into the platform. The landing page can be specified at a global  level, and for a specific Role. For screen shots please see the PDF file "Version 16.0" attached below and for instructions on configuring the default landing page, please see Appendix II in the same document. 

 

Notable Fixes

  • Incorrect and different numbers of decimal places were showing in different  places, such as: Members > Members and Members > CSR > People. This  discrepancy is now fixed so that a single decimal place displays throughout the  application. 
  • Sparkfly Point of Sale integration incorrectly processed orders that attempted to  redeem multiple Reward Offers. This issue has been resolved, so that the  platform correctly processes those orders and redeems multiple Offers when  present. 
  • Some Punch Cards were not displaying the configured Prizes within the platform  user interface. Prizes now display correctly as configured. 
  • When a user clicked an Order record in Cheetah Digital’s Engagement Data  Platform (EDP), the user was incorrectly routed to a page in Loyalty. The platform  now routes the user correctly to the Order record. 
  • An issue where Order details were not displaying correctly in Members > Orders  has been fixed. 
  • The purchase or addition of credit to Vantiv Gift Cards was not processed  correctly; this issue has been resolved. 
  • An issue with the Member Merge feature not operating correctly is now fixed.
  • An issue with editing tab names in the application is now fixed.
  • An issue where Visitors were receiving a New Member Email Confirmation is now  fixed. 
  • Confirmation instructions were not being sent to imported visitors that  converted to a full Member via an application using Single Sign On (SSO). This  issue has been resolved. 
  • An internal server error message displayed on the Content Page is now fixed. 

 

 

Archive

 

Was this article helpful?
0 out of 0 found this helpful
Return to top

Related articles