* Sales Performance Management *

@Nicolas Destombes

Welcome to Spiff. I started learning Spiff myself not too long ago and kept notes as I went, so let me share the sequence that stuck with me, because your seven questions really collapse into getting the foundation right (before you touch a plan) 

I'd go with the order -  

1. Data and participants.  

Get your people into Spiff with the right roles and your sales transaction data flowing cleanly from Salesforce. 

2. Hierarchy and assignments.  

Define who rolls up to whom. i.e., your RSM likely gets paid on their team's numbers, and that depends entirely on the hierarchy.  

3. Quotas and territories.  

Load quotas per role, since Territory Managers and Inside Sales measure against different targets. 

4. Build the plans.  

A plan is measures (what you're counting), rules (how it pays), and payout logic.  

While testing and understanding SPIFF flow, I built one role end to end, validated the numbers against a manual calc, then cloned the pattern for the next role. 

On the multiple-roles question, don't build four plans in isolation. The thing I wish I'd understood earlier is to build shared components once and reuse them across roles. for ex, Territory Managers and Clinical Specialists might share a base commission measure but differ on accelerators. Model the common pieces as reusable components so a rate change touches one place. 

For onboarding a new country specifically, the sequence I'd follow is: data feed, participants, hierarchy, quotas, then plans, then a parallel run where you calculate a full period and reconcile against a manual or legacy result before going live. I wouldn't launch a country without that parallel reconciliation step.  

A couple of resources that helped me  

The Salesforce Spiff Trailhead modules - Hands-on to learn Spiff Designer and payout rules:  

Official Guide and links:  

@Ashwini Garwandha,  

One additional follow up I have is related to the Marker Pop-Up. I have a Marker Layer with Base Object Contact (Mailing) that filters by the Account Name. On the Maker Pop-Ups section, I have added fields to the Details Tab that are showing up appropriately. But when I click on a marker that has more than 1 contact located at that Account I can see in the top right corner '1 of 3' etc. As I flip through them, one of them seems to be for the Shape Layer that I also have on the map. Is there a way to remove that as the end user really doesn't need to see it?  

It also seems to display as either the first or last based on if the Shape Layer is added before or after the Marker Layer. If it is default and there is no way to remove it, I will ask users to add their shape layer first and then the Marker Layer. However, when I do this the Marker Layer always shows '0 visible'. I researched and this seems to be a known issue.  

Thanks! 

Hi Isma, I'm not a Spiff user, but if Spiff follows the same release best practices as other Salesforce products, the best way to learn the details of product updates is to view the official release notes pages:

I am not aware of proactive notifications, although some products have release readiness emails you can subscribe to. It's part of the admin's responsibilities to proactively inform themselves on product changes whenever release notes become available! Hope this helps.

Solution found: 

Root Cause: The route options JSON was missing required fields that Maps uses to determine route type.

Fix: Updated route options configuration in WeeklyRouteOptimizer.cls and DailyRoutePlannerController.cls to include:

Map<String, Object> routeOptions = new Map<String, Object>();
routeOptions.put('DriveProfile', 'driving');  // Geographic routing mode
// TimeBasedOptions required for Standard type (Enabled:false disables time enforcement)
Map<String, Object> timeOptions = new Map<String, Object>();
timeOptions.put('Start', '09:00');
timeOptions.put('End', '17:00');
routeOptions.put('TimeBasedOptions', timeOptions);
routeOptions.put('Enabled', false);  // Disables time constraint validation
route.maps__Options__c = JSON.serialize(routeOptions);

Key Insight: TimeBasedOptions with Enabled:false is required for Standard route display (counterintuitively, it signals "I understand time windows but won't enforce them").

Result: ✅ Routes now display correctly as Standard type with proper geographic optimization. 

Hello Glenda, 

My Accounts won’t work here because that filter is based on the Account owner, not the Task owner. In Maps, I’d start with All Accounts, then add an Activity Filter for without activity in the last 30 days, and see whether the Task Assigned To/Owner ID field can be filtered as a Dynamic User. If your org supports Dynamic User Marker Layers, that is the native path. If that field is not available in the activity sub-filter, then this specific ‘no activity by logged-in user’ scenario usually needs a helper field/automation rather than just standard Maps filters. 

If you need this functionality this can be achieved with code if you need.