Page Comparison

 Back to Getting Started Guides for CRM.COM

...

Sub-module	Type	Classification	Navigation	Dig In
Access Tokens Definition	Configuration		CONFIGURATIONFOUNDATION APPLICATIONACCESS TOKENSSET UP ACCESS TOKEN DEFINITIONS	/wiki/spaces/WIP/pages/10010278Configuring Access Token Definitions
Access Token Classifications	Configuration		CONFIGURATIONFOUNDATION APPLICATIONACCESS TOKENSSET UP CLASSIFICATIONS	Configuring Access Token Classifications

...

Access Token Definitions are used to control the creation of Access Tokens, by defining the policies governing the format of the Access Token User Identifier, Pass Code and Authentication Code.  You can define whether Access Tokens can be created without an Identifier and Pass Code or deactivated when their last entity association (Rewards Participant or Accounts Receivable) is removed. 
Additional settings relating to Access Tokens may also be defined, concerning Accounts Receivable and Rewards Participants, as well as Communication (Access Tokens can be automatically communicated to customers once created).

...

• Reward Offer Categories: Reward Offer Categories are used to classify Reward Offers into generic groups based on common attributes. Reward Offer Categories following a hierarchical tree structure. Each Reward Offer can be classified in only one category. 
• Reward Offer Templates: Reward Offers Templates can be used during the creation of a new Reward Offer.  A Reward Offer Template has a similar structure to Reward Offers to facilitate the transfer of information to the newly created Reward Offer. 
• Reward Settlement Run Definitions: Reward Settlement Run Definitions are used to execute runs that will evaluate Customer Events and Spend Transactions, to debit or credit the accounts of participating Merchants, based on the Awards provided or redeemed, using Contribution Rules defined for each Merchant. For example, when an Award is given via a Customer Event that was created by a Unit C merchant, then Unit's C merchant account is debited with the Award amount. When a Spend Request Customer Event is created by a Unit C merchant, then Unit's C merchant account is credited with the spent amount. The debiting amount is calculated based on the Contribution rules set on the Rewards Participating Merchants.
• Wallet Balance Expiration Run Definitions: Wallet Balance Expiration Run Definitions are used to define the rules by which Runs will be performed, to identify the Wallet amount that should be expired and debit the Wallet for the unspent amount of money (the identification process is performed based on the specified Expiration Date and the amount already spent). The resulting debit that reflects the expired amount is directly allocated against the expired credit amount.
  The Expiration Date is specified either manually or automatically, as part of a Reward Offer Award that has a specific Expiration Date. 
  If you have Reward Offers for awards that should be applied only up to a specific date or time after it is awarded, make sure to configure the Expiration Run so that expired awards are removed from the participant's balance. 

...

Module	Navigation	Dig In
Rewards Participant	REWARDSREWARDSMANAGE REWARDS PARTICIPANTS	/wiki/spaces/WIP/pages/10008611Managing Rewards Participants
Customer Events	CRMCUSTOMER EVENTSACCESS CUSTOMER EVENTS	Managing Customer Events
Reward Offer Evaluation Run Definition	REWARDSREWARDSPERFORM REWARD OFFERS EVALUATION RUNS	Using Reward Offers Evaluation Run Definitions

...

Once a Reward Offer Run Evaluation Definition is executed, the System evaluates Rewards Participants and their information against the Reward Offers and creates Award & Spend Transactions for each one, debiting or crediting the participant's Wallet. Specifically:

1. The Reward Schemes to be evaluated are retrieved, based on the Reward Schemes selected in the Definition.
2. The Reward Offers to be evaluated are retrieved, based on the Reward Offer Types selected in the Definition.
   
   
3. Customer Events which are not of Type Spend Request are evaluated to decide whether they should be awarded.
4. Award Reward Transactions are created for each awarded Customer Event.
   
   
5. Rewards Participants, Contact Information and Subscriptions are evaluated based on Reward Offers not related with Customer Events
6. Award Reward Transactions are created for each awarded Rewards Participant.
   
   
7. Customer Events which are of Type Spend Request are evaluated to decide whether the specified amount can be spent.
8. Spend Reward Transactions are created for each valid Customer Event.

...