Making the most of Affino's new Loyalty Scheme SaaS Solution

The Loyalty Scheme then Uses a number of existing core Affino Elements as follows :

• Conversion Events as Badges - the central Badge mechanic is rendered via Conversion Events which track key customer activities and yield Achieved/Claimed badges once targeted task is completed / tracked. Affino currently has 64 Conversion Event Types also known as 'Trigger Events'.
• Product Template Articles - These are how the individual Rewards are rendered where in a similar way to Conversion Events - these can either be straight up Products / Catalogue Items which are transacted directly, or else they link via URL to some 3rd party content utility - which in the case of FG Rewards is actually Dynamic Forms - but more of that later.
• Store Credits - This is the unit of exchange. We're using the Store Credits - as then can be directly exchanged / transacted to the value of Catalogue Items / Product Templates. Note that we do not use Conversion Event Points because those drive the sales and marketing engagement metrics.
• Conversion Events as Store Credit Resolvers - If you're not using Catalogue Items to directly transact Rewards (easy to do if you have ecommerce running) - which means automated allocation and subtraction of Store Credits. You need to use a secondary balancing Conversion Event - as FG Rewards do for their Dynamic Forms approach. Whenever a customer with the appropriate Badges / Store Credits total applies for a Reward - the value of those Store Credits needs to be removed from the account. For this to happen on Dynamic Forms - you need separate Conversion Events which is simply triggered when the Form is submitted, and reduces a customer's points total.
• Articles - Each Badge / Conversion event can lead to a secondary destination, as can each Reward - this can be the destination of where the Key Activity occurs, or a Standard Article used to describe that particular Badge activity or Reward further - you simply enter a reference URL on the Conversion Event (Badge) or Product Template (Reward).
• Dynamic Forms - For the FG Rewards Loyalty Scheme, AgriBriefing chose not to use direct Catalogue Items for transacting the Rewards, but rather each Product Template links to a specific Dynamic Form which is then used to fire of a request for the Reward. So the customer needs to accrue the appropriate Loyalty Points / Store Credits to be able to exchange them for that specific Reward - as limited by 'Number Of Store Credits Required' set on Product Template.
• Content Security Right - You can additionally use Content Security Rights to limit access to certainly elements within the process - and use Conversion Events to grant those as privileges - they can even become part of the Rewards - in giving access to otherwise hidden VIP content for instance.
• Design Styles / Custom CSS - For the Claimed / Active Badge state you can incorporate a 'Design Style Feature Icon' to emphasise the claimed badge. Custom CSS might also be applied for Feature Rewards - where you don't apply 'Number Of Store Credits Required' - but instead link off to a feature description page - you might wish to style the Featured Reward Cell differently to the rest - to emphasise and delineate.