Marigold Codes lets members register product purchases by entering product codes. Using Codes is as an alternative to receiving a POS feed from vendors or other POS integrations. For example, using Codes is a tactic that CPG companies can use to learn about member purchases without collecting purchase information from third-party vendors. Each Code (e.g. a sticker on a shampoo bottle) has many Code Certificates (e.g. code certificate “BK1232”). Marketers can provide prizes, such as points, entries into sweepstakes, or rewards to incent members to enter Codes. Although codes require that consumers register the code and may have possibilities of fraud, using Codes can have the benefit of collecting additional member information, such as location, and opportunities to surprise-and-delight members.
Note: Marigold Loyalty Codes are also used by Marigold Loyalty Receipts for mapping UPC symbols on printed receipts to valid product codes (see Code Values below).
There are no Program Settings for Codes.
Use the Products | Codes screen to manage your Codes.
The Codes screen includes a variety of facilities to make it easy for you to search, filter, sort, and export/import records.
Searching. Use the Search text box to search records by Name, Label, or UPC.
Filtering. Use the Status and Effectivity dropdowns to filter records.
Sorting. Use the Sort dropdown to sort records by date created, date updated, or display name.
Export / Import. Use Marigold Loyalty’s built-in export and import capability to export existing Codes to and from .csv files.
Use Marigold Loyalty’s Content Management capabilities to manage your Codes:
Status. Use status to specify when a Code is in use. Change the status to change the visibility of the Code to members. Valid statuses are ‘Draft’, ‘Published’, and ‘Archived’.
Effectivity. Change the effectivity to designate the timeframe for which members can view and respond each Code. Valid effectivities are ‘Always’ and ‘Schedule’.
Categories. Organize records into categories. Client applications use categories to show subsets of records to members.
Tags. Add one or more tags to help you search, filter, and organize your records. Tags are only visible and usable in the Marigold Loyalty Marketing Console: you can modify and create tags, but your members are not be able to see or access the tags.
Assignee. Choose an assignee to give ownership or responsibility to one or more Marketers. You can easily find the tasks assigned to a specific Marketer by searching for a name in the Search textbox.
For more information about Marigold Loyalty’s powerful Content Management capabilities, see Content Objects.
Following is a list of the main attributes:
UPC (optional). Use the UPC field to store the unique UPC value for the Product Item that the Code represents. For example, if your brand sells shampoos, then store the UPC for the shampoo in this field.
Amount with Metric (optional). Specify the metric that a member receives whenever they submit an approved response.
Use the Code | Definition screen to view the valid set of responses that members can submit.
Use Code Entries to manage the list of valid values that members can submit in return for a prize. Each Code can have zero or more Code Entries.
Each Code Entry has the following attributes:
Value. A string that uniquely identifies the Code Entry.
Status. Indicates whether the code is ‘Unused’ or Redeemed’.
You can manually create Code Entries, import new Code Entries from a .csv file, or use the “Generate” button to generate new Code Entries.
Each Code can have zero or more Code Values. Marigold Loyalty Receipt Scanning uses Code Values to lookup receipt items against a list of valid Product Codes. Each Code Value has a vendor-specific string that identifies a product on the vendor’s receipt. For example, the same book has a unique UPC (e.g. 890055551234) printed on the back of the book, but each vendor may use a vendor-specific string to identify the book on their printed receipts (e.g. Walmart uses 890234, while Target uses BK-2128).
Each Code Value has the following attributes:
Vendor (aka Retailer). The name of the vendor for this Code Value.
Code Value. A string that identifies the Code for this vendor.
The combination of Vendor and Code Value must be unique within a Code.
Define Code Effectivity Code are governed by acoden overall Effectivity Period that controls when a Code is considered active and available for use. In addition to the overall Effectivity Period for the Code, the platform allows you to set more granular schedules that control when a Member can respond to the Code (called the Response Period), and when the platform considers responses to be usable for reporting and analytics (called the Usage Period). Optionally, you can click the Recurring checkbox to define a new recurring schedule for an item's effectivity when the Select Period Type is Fixed. Note: Depending on the Code type, the effectivity period options may vary slightly. You may see some, or all, of the options described below. Response PeriodTo define the response period:
Usage PeriodTo define the usage period:
Define Recurring ScheduleDefine Recurring Schedule
To define a new recurring schedule for this item's effectivity:
|
Use segments and locations to specify which members can see and respond to a Code.
Segments. Specify one or more eligible segments for each Code. Use segmentation to target a specific demographic with the Code by including or excluding segments to be eligible for the Code. View the Members | Segments page to create member segments.
Locations. Specify one or more eligible locations for each Code. Target specific locations with individualized Codes by including or excluding locations. View the Admin | Locations page to create locations.
Use the Advanced tab to manage the advanced settings.
Limits. Use limits to specify the total maximum submissions for all members, the maximum submissions for each individual member, and the minimum amount of time between submissions.
Business Value. Use business value to give a monetary value for each response.
Prizes. Use prizes to add incentives for members to submit responses. You can specify a metric to award to the member for submitting a response, or you can award secondary prizes such an entry into a sweepstakes or a reward from your reward catalog. Awarding only occures on approval of the response.
Use the Code | Responses screen to view responses for one Code. Use the Products | Code Responses screen to view responses across all Codes.
Each response has a status:
Submitted. The member has submitted the response but it is not yet accepted nor rejected.
Approved. The response has been approved, either manually by a Marketer or automatically with the auto-approve feature
Rejected. The response has been rejected by a Marketer and is ineligible to receive any prizes. You must manually reject a response. You can add a message to the member regarding the rejection and give the member the opportunity to re-submit a response.
Returned. The response has been rejected, but the member has the opportunity to re-submit a response.
Operations you can perform on a Code Response include:
You can add a comment
You can delete a response
Use the Code | Dashboard screen to analyze the responses for one Code. You can analyze:
Views. The number of times that a Code was viewed.
Submits. The number of approved code responses.