Configure a Reward - Dynamic

This article describes the configuration options available within the Dynamic Reward type. This Reward type effectively serves as a "blank" Reward. This Reward type allows you to manage the Metric deduction within the Loyalty platform, but all other aspects of the Reward benefit are defined and managed outside of the platform.

Unlike every other Reward type, the Dynamic Reward type does not have a fixed "cost" in Metrics. This Reward type lets you define a variable Metric cost in an external system, then submit that cost to the Loyalty platform via the Redeem Dynamic Reward API. Using this API, you can calculate the cost of the Reward and apply an applicable discount, debit the Metrics from a Member based on the number of points converted to a discount, or (in the case of a return), credit the Metrics previously deducted.

The variable Metrics and corresponding discounts must be configured outside of the Loyalty platform. Dynamic Rewards and its related API are meant to provide the capability and mechanism to debit or credit Metrics only. You must define the Metric-to-discount conversion rate, calculate the conversion rate, and apply the applicable discount to the transaction within your systems, applications, Point of Sale, web, or mobile offerings.

Note: The Dynamic Reward type serves a similar purpose as the Debit Reward type. The key difference between these two Reward types is that the Metric cost of the Reward is fixed in the Debit Reward type. Conversely, the Metric cost of the Reward can be variable in the Dynamic Reward type.

This article assumes that you have already created a Reward by either copying a Reward, or by creating a new Reward from scratch.

The Definition tab of the Reward Details screen is used to configure the properties and details of this Reward. The tab includes several sections, each of which is described below.

Reward Details

Within the header area of the screen, you can configure the following properties of the Reward:

  • Thumbnail Image: Click Upload to browse to an image file on your local PC. Select the desired image, then click Open. Please note that the thumbnail image is not used within the Reward content that gets configured on the Content Editor.

The Reward Details section contains many high-level properties about the Reward:

  • Display Name: The name of the Reward as displayed throughout the platform. When copying a Reward template, this value will automatically be the name of the template followed by an incremental counter, such as “(1).” This field supports the use of localized content.

  • Description: A description of the Reward. This field supports the use of localized content.

  • Reward Type: If you copied a Reward, this field is automatically populated with the Reward Type of the base Reward; you may optionally select a different option. If you change the Reward Type, the configuration properties displayed on the Reward Details screen will update accordingly.

  • Required Metric: Enter the number of Metrics the Member must spend in order to claim this Reward. From the drop-down menu, select the desired Metric.

  • SKU: Enter the Reward product SKU. This field is typically used as a reference for external systems.

  • Categories: Reward Categories are used to organize Rewards, often for controlling what Rewards get displayed on your website or app. From this drop-down menu, optionally select one or more Reward Categories to assign to this Reward. For more information, please see Reward Categories.

  • Tag: Tags are used to help search, filter, and organize objects within the platform. To reuse an existing Tag, begin typing all or part of the Tag name, and select it. You can also type in a new Tag value.

  • Rank: Optionally, enter a ranking for this Reward. This value is used only when sorting the Rewards screen by Rank.

The following fields are available by clicking the Show More link at the bottom of the Reward Details section.

  • Internal Name: This field is automatically populated based on the Display Name value. This field is disabled by default. To edit the Internal Name, click the lock icon to make the field editable. A confirmation dialog box is displayed; click OK. The Internal Name must be unique and can not include any special characters or spaces; only numbers, letters, and underscores are allowed.

Note: The recommended best practice is to change the Internal Name when you initially copy an Reward, in order to avoid issues with duplicate Internal Name values. After this initial change, you should not edit the Internal Name again. Never edit the Internal Name after you publish the Reward.

  • Integration ID: This field allows you to enter a unique code that is meaningful to your Point of Sale system, so that your system will recognize this Reward; this value is not used internally within the Loyalty platform. You can optionally use Integration IDs that are unique per Reward, or have a single Integration ID used across multiple Rewards. This field is disabled by default. To edit the Integration ID, click the lock icon to make the field editable. A confirmation dialog box is displayed; click OK.

  • Tracking Code: Optionally, specify a value to track clicks to the Rewardwhen you share its URL on external channels such as email or Facebook. The platform adds this Tracking Code value to the Reward URL. Please note that the Tracking Code is not used for tracking Members logged into your loyalty program app.

  • Stores: Optionally specify one or more Store Tags for which this Reward applies. Please note that this field is available only if the Local Store Marketing feature is enabled in your account.

  • Optional: Toggle this option On to enable retailers to opt-in or opt-out of this Reward. Please note that this field is available only if the Local Store Marketing feature is enabled in your account.

  • Extra JSON: Optionally, to define additional JSON as part of the API payload, click Add JSON. The Edit Reward pop-up window is displayed. Enter the additional JSON, then click Save.

Effectivity Period

Rewards are governed by an overall Effectivity Period that controls when, and for long, the Reward is visible to Members on your website or app.

In addition to the overall Effectivity Period for the Reward, the platform allows you to set more granular schedules that control when a Member can respond to the Reward (called the Response Period), and when a Member can use the Reward (called the Usage Period).

See Define Reward Operational Ranges for more information.