Implementing New Lead Scoring

[Anonymous]

Thanks Julie! Very helpful. This might be a better question for Justin, but we have multiple workspaces all using the same API within Marketo.  Would it be looking at the scores of ALL leads, not just those in my workspace?  Many workspaces aren't using MSI or scoring leads.

[Justin_Norris1]

Chantelle Juffs​, great question and I'm totally not sure.

So what we know is

To calculate the number of stars and flames, first your leads and contacts are sorted by score or score change (for Relative Score and Urgency, respectively).  Then they're divided into tiers -- the top tier receives the most stars or flames, the next receiver fewer, and so on down.

As scores change, urgency, priority, and relative score values are immediately recalculated. The urgency and relative score tiers are automatically calculated every night on Marketo servers.

https://docs.marketo.com/display/public/DOCS/Priority%2C+Urgency%2C+Relative+Score%2C+and+Best+Bets

What we don't know (or I couldn't find it) is whether those tiers are calculated across the entire Lead Database or just the partition that lead belongs to (I assume you mean partition rather than workspace in your question, since leads belong to partitions whereas workspace refers to the assets and campaigns a user has access to).

If anyone knows or finds out I'd be interested in the answer too!

[Anonymous]

Justin Norris According to Marketo support, the MSI score settings are for the global instance and not workspace/partition specific.  So my issue is that my leads are being compared to other leads in the system that I can't see! Oh well... I'll try to find a workaround.

[Justin_Norris1]

Chantelle Juffs​ that's a pity, but good to have that confirmed from support!

I suspect it'll be difficult to work around that since those relative calculations can be difficult.

The only way I've ever done something similar is when I had a BI resource extract all my data into a data warehouse, perform the calculations in an ETL tool, then reimport to SFDC (this was for calculating RFM metrics not the MSI scores, but same principles). However then you are really baking your own cake and it may be a lot more trouble than it's worth.

Would be interested to hear if you find a viable work around.