Happy Friday, Community!
It's been a while since I've asked a Friday question and today I have a few (will separate by post).
I never realized that my instance could use/had access to RCM and Success Path Analyzer (I checked it out thanks to the awesome Marketo & Mochas: 5 Marketo Features to Know in 2025 webinar), so I set up a revenue model this week and approved it for use with the analytics report.
Yesterday, I adjusted the reporting time frame in the Success Path Analyzer to "This Year" (I think it defaulted to All Time) and it's been "loading" ever since, whether I hit "refresh analyzer" from the setup tab or simply wait on the report page itself. With that in mind, I have two questions:
*The webinar said that it is better to "leverage an Operational Program to power the stage transitions instead of building the logic into the AJA model" - however, a) we have an operational program that manages our Lifecycle in general but I'm not sure how this would connect to the model and b) one has to set the smart list filters in the model transitions or it can't be saved (or is this something separate/in addition?).
I am sure, as usual ๐, that I've missed something in my understanding or setup, so appreciate any direction or insight anyone might have!
TIA ๐
Michelle
Happy Friday, @michellechopin! Great to see you back here. ๐
It's not unusual for Marketo to take a little while for loading the report, especially if thereโs a large volume of records, it shouldn't be stuck indefinitely. Try clearing your browser cache or running the report in an incognito window to rule out browser-related issues. If it's still stuck, you might want to try a couple of hours later, if it still takes indefinite to load the report, I'd recommend opening a support ticket. While trigger campaigns are sure more resource and processing power than batch campaigns, however, it shouldn't have too much impact on report loading as it's the historic data based on the RCM stage transitions.
As for leveraging an Operational Program for stage transitions, the idea is to centralize and standardize lifecycle movement in one place rather than embedding complex logic into the RCM model. You'd need to add use the "Manual Stage Transition" in each RCM model transition -- w/o the manual stage transition trigger or trigger(s) + optional filter(s) added directly to the mode, you'd not be able to approve it.
You can validate the model as well to ensure you haven't missed out on adding the triggers to any transition in the model.
If you already have the lifecycle program -- you'd need to ensure that you're updating this model's rcm stage in the respective lifecycle campaign's flow using the Change Revenue Stage flow step -- you'd need this only if you've added the Manual Stage Transition trigger in the transiotion (the recommended way); however, if you're managing the transitions in the model itself, you'd not need to update the stage via a campaign flow step.
Hope this helps. Please let us know if you have questions.