The Reward Offer Template that if selected it will carry over predefined information, such as offer classificationOffer Classification, award Award and spend conditionsSpend Conditions.

Visit View Configuring Reward Offer Templates for more information

The life cycle state Life Cycle State of the reward offer Reward Offer which can be 'Effective' or 'Not Effective'. By default, reward offers are created as Reward Offers are created as 'Not Effective'.

The latest date that the rewards offer become effectiveReward Offer become 'Effective'. This information is set or updated each time the life cycle state Life Cycle State of the reward offer Reward Offer changes from 'Not Effective' to 'Effective'.

The

Category of the

Reward Offer.

This is filtered based on the allowed categories defined in the Reward Offer Type

The group that owns the specific Reward Offer

The privacy level of the specific Reward Offer. It is always read only and can be changed through a dedicated action

Reward offer validity .

The method that will be used to evaluate the Offer. For the evaluation of the specific Reward Offer Type, only one option is available:

• Batch Process:
  When this option is selected, Awards will be evaluated and provided only during the execution of the Reward Run.
  i.e. Customer events are not processed by the Offer immediately but by the Reward Run (even if the Process Immediately option is checked on the customer event). Results will not be available immediately on the execution of the event.

The Award given if the Offer Award Conditions are met. Only one of the available options can be selected, and it is mandatory that at least one is defined.

If enabled then the Reward Offer will be applicable only if the provided award is the best award (highest amount) among other Reward Offers that might be applicable. By default, this option is set as disable

Offer Validity is used to define the period ranges that the

Reward Offer is valid for. Two validity options are available:

• Valid from latest effective date onward (default option)
  If selected

• , only

• Customer Events which were created from the latest effective date (inclusive) onward

• are awarded.
• Valid for a specific

• period
  • Valid From (inclusive)
  • Valid To (exclusive)
    If selected

• • , only Customer Events created within

• • the period, are awarded.

  Status
  colour

• Yellow title

• Available from CRM.COM R11.1.0

• Valid During Birthday Period
  
  • Valid X days before birthday date
  • Valid X days after birthday date
    If selected, only Customer Events created within the period, are awarded.
• Valid During Name Day Period
  • Valid X days before name day date
  • Valid X days after name day date
    If selected, only Customer Events created within the period, are awarded.
• Valid During a Recurring Period
  • Valid From (inclusive) Day and Month
  • Valid To (inclusive) Day and Month
    If selected, only Customer Events created within the period, are awarded.

Reward Award Validity is used to define the period for which an award is valid for the participant to spend. By default all awarded offers will always be always valid unless a Reward Award Validity period is defined in the Reward Offer based on which the Award Transaction was created. Reward Award Validity settings can either specified as:

• Always validValid: No validity period is defined so awarded amount can be spent at any time
• Valid for a specific period: The awarded amount can be spent only in a specific period of time and this can either be:
  • Valid up to X UOT after the Award Transaction's creation date
  • Valid up until to a specific date

The method that will be used to evaluate the offer. For the evaluation of the specific reward offer type, only one option is available:

• Batch Process
  With this option selected, only during the execution of the Reward Run, awards will be evaluated and provided
  i.e. If a customer event needs to be processed, then the related reward offer will only be evaluated when the next Reward Run is executed. Results will never be available immediately on the execution of the event.

It defines Determines how many awards Awards can be provided to each customer by this offerOffer. The supported options are the following:

• Only One
• Multiple

A list of segments which are used to filter in the customer events that are allowed to be awarded.  The criteria consist of the following:

• Segment:  A select box with all the segments having a segment entity equal to one of the following:
  • Accounts Receivable
  • Rewards Participant
  • Contact Information

    Status
    colour Green title Available from CRM.COM R10.0.0

  • Award Reward Transaction

    Status
    colour Green title Available from CRM.COM R10.0.0

  • Spend Reward Transaction

    Status
    colour Green title Available from CRM.COM R10.0.0

A list of segments which are used to excluded exclude the customer events that are not allowed to be awarded. The criteria consist of the following:

• Segment: A select box with all the segments having a segment entity equal to one of the following:
  • Accounts Receivable
  • Rewards Participant
  • Contact Information

    Status
    colour Green title Available from CRM.COM R10.0.0

  • Award Reward Transaction

    Status
    colour Green title Available from CRM.COM R10.0.0

  • Spend Reward Transaction

    Status
    colour Green title Available from CRM.COM R10.0.0

A list of Areas, Cities or Districts that should be associated with the Rewards Participant's active addresses

A list of productsProducts, product types or product families Product Types or Product Families that the reward Reward can be spend spent on.

The Group that owns the specific Reward Offer, which automatically defaults to the Group of the signed in User.
Reward Offers are an Explicit Viewing Entity which means that only non-super Users that belong to the Owned By Group, or belong to a Group that collaborates with this one, or are Super Users can access and view this Reward Offer

The Privacy Level of the Reward Offer
It is always Read-only and can be changed through a dedicated action or automatically set by the Privacy Level Assignment Rules (PLAR)