Program and Multi-Program Management Tools

Programs establish the framework for your incentive and loyalty program. They allow you to develop and manage the community of members that you want to incentivize. Fielo is Multi-Program, which means that it can handle more than one program at a time. This allows you to:

• Create different programs for different geographical areas, such as states or countries, or for different brands or product lines within your company.
• Build different loyalty portals for your different programs.
• Set up different incentives for your different programs.

Editing Program Settings

Now that you've created your program, you can manage some important configurations. Start by accessing the Settings tab on the detail page of the program you want to edit and click on Edit Program Settings.

Manage Consents

Specify which consents you need to request of your members. You can know more about that in Consents.

Member Settings

This section defines how new members will be registered in your Program.

Request Member Authorization allows you to double-check new member registrations. If , each new Member will need to be approved via an Approval Process before being included in the Program. Until then, the Status of the member will remain Submitted for Approval.

🚧

Programs with a Loyalty Portal in Salesforce Experience Cloud

In Programs, using Request Member Authorization, Members with status Submitted for Approval will be able to log in to the loyalty portal, but will not be able to interact with the Program until they are approved.

📘

Request User

Request User is a field visible only through Classic View, which allows you to decide if a user will be associated with a new member. If , a new member will only be assigned a user if approved via an approval process. Until then, the status of the member will remain Pending User.

Because the registration component creates users directly through Salesforce, Request User cannot be used with loyalty portals on Sites.

Analytics Settings

This section's goal is to allow you to decide if the Command Center's reports will appear for a specific program or not. It is enabled by default.

Enable Program Analytics enables the Analytics to use in your program. You can uncheck this option to disable the reports for a specific program - that is, the Command Center will not display any reports.

Simulation Settings

In order to be able to use the Incentive Planner, you need to enable its use within your program first. Only after that, will you be able to see the Simulator Settings tab within the Incentives menu.

Enable Incentives Calculator enables the Incentive Planner use in your program.

Enable More Accurate Maximization shows up only when the previous field is . This field enables the delivery of more accurate results through the Simulation API maximization, meaning that it will support: all criteria operators (greater or equal, less or equal, etc.), more logical expressions (OR and custom expressions) and more than one segment per Incentive. However, it has an impact on performance, consuming more time.

Transaction Settings

Online Processing determines how Transactions are processed.

If , the transactions will be processed synchronously when recorded, that is, the rewards will be given to the member as soon as they perform the incentivized action. However, note that if several transactions are being created at the same time and the processing takes over 8 seconds (this is the default), the system will interrupt the job. Because of this, some records might not be processed and will be marked as is offline. You'll need to manually run the batches to process them or wait until they run automatically (once a day).

If , the transactions and trackers will be processed as soon as the member performs the incentivized actions (i.e., when records are created/edited), but only when the offline transactions and offline trackers batches run, will the member receive the rewards defined in promotions and challenges (i.e. currencies, funds, badges, or instant rewards).

Cap Adjustment Transactions determines whether future adjustments you make for members will be taken into account in the cap limit or not. By default, it will be unchecked.

Rewards & Redemptions Settings

This section defines how Rewards and Redemptions are handled in your Program.

Number of Code Digits sets the number of digits that the Unique Codes of Redemption Items should contain. If you enter 8, for example, your codes will consist of eight numbers. Fielo allows for anywhere between 4 and 16 code digits.

Request Redemption Authorization allows you to review redemptions before they are finalized. If , each redemption will need to be either approved or rejected via an Approval Workflow.

Budget Settings

This sections refers to the approval process for budgets.

If you want that all your budgets go through an approval process, check the Require approval for budgetary funds field so it is set to true.

Storage Optimization - New R1'25

The Storage Optimization feature allows system administrators to automatically delete records a specified number of days after they have been flagged as Obsolete (or Processed, in the case of Processed Behaviours). If you don't want records of a certain object to be deleted, leave the number of days blank.

Obsolescence and Processing Rules

Records are considered Obsolete (or Processed) under the following conditions:

• Points: obsolete when the Balance reaches zero.
• Transactions: obsolete when either:
  • All related records (Incentivized Record, Point, Redemption, Reverted Transaction) are marked as Obsolete, or
  • No related records exist.
• Redemption Items: obsolete when Status is Fulfilled, Expired, or Reverted.
• Redemptions: obsolete when either:
  • All related Redemption Item records are obsolete, or
  • No related records exist.
• Promotions: obsolete when Status is Ended.
• Challenges: obsolete when Status is Ended.
• Processed Behaviours: Considered Processed once the incentives engine has finished processing the record and generated an output (such as a Transaction and/or a Tracker).

📘

Note

Records are flagged as Obsolete/Processed starting from the first installation of this feature.

Records created prior to installation will not be automatically flagged.

To manage historical data, administrators can run UpdateObsoleteRecordsBatch batch process to evaluate and mark historical records as Obsolete.

Automated Deletion

A daily batch process deletes records according to the configuration defined by the administrator.

🚧

Important

The obsolete/processed record cleaner batch must be scheduled to run once per day in your org.

If the batch is not currently running or scheduled, make sure to schedule ObsoleteRecordsCleanerBatchSchedule

Cap Time Zone Settings - New R1'25

This setting allows you to define the time zone used to calculate a program’s capping reset time.

If left blank, the engine defaults to GMT+0.

• Time Zone: Select the program’s primary GMT time zone.
• Time Zone additional Offset (Hours): (Optional) A numeric field, empty by default, that lets you add an extra offset (in hours) to the selected time zone.

Agreement

Agreement sets the terms and conditions that Members need to accept in order to take part in the Program.

Program Management Tools

There are several tools to help you manage programs. You can access these tools in the top section or by clicking on the program detail page.

• Delete
• Export
• Save as a Model

Export

The Export tool allows you to export all data from your program. It exports all program fields (including custom fields), Agreements, Levels, Segments; Badges and Currencies (including Program Currencies), as well as all Incentives (promotions and rules; challenges and missions) that belong to your program. Upon exporting, you'll get access to a JSON file in the following format:

Program (FieloPLT__Program__c)

• FieloPLT__Reward__c
• FieloPLT__Badge__c
• FieloPLT__ProgramPointType__c
• FieloPLT__Agreement__c
• FieloPLT__ProgramAssignment__c
• FieloPLT__Segment__c
  • FieloPLT__Criterion__c
• FieloPLT__Level__c
  • FieloPLT__Criterion__c
• FieloPLT__Promotion__c
  • FieloPLT__Rule__c
    • FieloPLT__Criterion__c
  • FieloPLT__KPIDomain__c
  • FieloPLT__EmailCampaign__c
• FieloPLT__Challenge__c
  • FieloPLT__ChallengeReward__c
  • FieloPLT__Mission__c
    • FieloPLT__Criterion__c
    • FieloPLT__ChallengeReward__c
  • FieloPLT__KPIDomain__c
  • FieloPLT__EmailCampaign__c
• FieloPLT__KPIDomain__c
• FieloPLT__EmailTemplate__c
• FieloPLT__EmailCampaign__c

🚧

Unrelated Reward Records

Rewards that aren't related to your Program are only exported if they're linked to any other record in your Program.

Save as Model

Save as Model allows you to save your Program for reuse as a Model when you create a new Program. This way, you don't have to configure everything from scratch if your new Program has many of the same characteristics as this one.

The model doesn't include other features, such as promotions or rewards. It only saves the program's settings.

Multi-Program Management Tools

You can run more than one program at a time. Multi-Program support is really useful for loyalty and incentive programs that, for example, operate in several geographical areas and require different functionality for each area.

There are several tools that let you manage general configurations for all of your programs. You can access these tools by navigating to the Program tab and clicking .

Import

Select Import to upload a JSON file containing all the data from a Program you wish to import. This will create a new Program based on another one that you or a colleague has previously exported.

Since in most cases the file imported will be one that was previously exported from another Org, you won’t need to do too many changes in the file before importing. However, we do advise you to follow the steps below and to Validate the JSON file before uploading. Otherwise, the import process might fail.

1. Make sure that the Org which you are importing the Program to has the same data model as the Org from where it was exported.

Check if both Orgs have the same objects, fields, configurations, and the same customizations in general. They must have exactly the same data model because the import will fail if the configuration is not the same. E.g. an incentive that you had in the original Program was incentivizing a custom object that doesn’t exist in the destiny Org.

2. Export theFieloLocal library from the original Org and import it to the destiny Org.

To create in the destiny Org the same Behaviors Types and Actions that you have in the original Org, so as not to receive an error if any of your Incentives use them, you must export the FieloLocal library from the original Org and import it to the destiny Org.

For that, go to the Tools tab and access the library. Once there, click on Export.

When you have the generated JSON file, import it to the destiny Org using the same import feature (Programs > management tools > Import).

3. When importing a Program that uses Funds Allocation Rewarding, create the PMB beforehand.

The Program that you exported might have been using Fund Allocation to reward members who have accomplished a Rule, Challenge, or Mission. If that is the case, then you will need to create a Partner Marketing Budget (PMB) in the destiny Org.

As it was explained above - regarding the currencies - you must edit the JSON file in order to replace the old PMB ID with the new one before importing the file. You’ll be able to find the PMB ID within its view page URL, and you will replace it in the file every time that “partnermarketingbudget__c" shows up (as this field’s value).

Once you're ready, just hit Import.

Currencies

Custom currencies can be used across all of your programs. See our Currencies guide for more information.

Enable Fund Rewarding

Use this option in order to activate the Fund Rewarding option for your Promotions and Challenges. See Funds Allocation Rewarding for more details.

Enable Task Incentives

You can reward your Salesforce users for completing Tasks (standard Salesforce object), with the ability to narrow down by task type, target, related object, priority, timeliness, custom completion status, and more. To do so, enable Task incentives.

📘

Task Incentive Considerations

1. This feature should only be used in programs where there is no more than one Member per User.
2. If your org has any custom validations or required custom fields on Task, you may need to define trigger logic specific to your org.
3. Only Closed tasks are incentivized.
4. Closed Salesforce Tasks are transcribed to Fielo Event records. If you use custom picklist values on standard Task fields, you should include those values in the corresponding Fielo Event fields, as well.
5. The Task Related To Object field on Fielo Event uses the API name of the related object.
6. To stop using this feature, deactivate the trigger on the Salesforce Task object called FieloClosedTask.

Platform Cache

As of the Spring '21 release, Fielo uses the platform cache to bring some improvements to the platform.

Because of this, it is possible to overview all the configurations stored within the Fielo Cache, so you can know how it is being used. For example, if you just created an incentive and you think it is not being processed correctly, you can check what Fielo is using to process it, what is in the incentive’s cache. For that, open the App Launcher and look for "Fielo Cache".