Hey Raj, sorry to hear that the old _satellite.Logger.getHistory() method stopped working for you in Adobe Launch—let’s go through some reliable alternatives to track all triggered rules:

1. Use the Official Adobe Debugger Extension #

This is the most straightforward and supported method:

• Install the Adobe Experience Platform Debugger extension for Chrome or Firefox
• Open the extension, switch to the Launch tab
• Check the "Enable Debug Mode" checkbox. From here, you’ll see real-time logs of every triggered rule, including its name, trigger conditions, and the actions that ran—all neatly organized in the panel.

2. Add Custom Logging via a Global Rule #

If you prefer console-based logging, you can add a custom script to capture rule triggers:

• Create a new global rule in Launch, set the condition to Library Loaded (Page Top)
• Add a Custom Code action with this snippet:

// Override the rule trigger method to add logging
_satellite._ruleTriggered = function(rule) {
  console.log(`[Launch Rule Triggered] Name: ${rule.name}, ID: ${rule.id}`);
  // Keep the original functionality intact
  _satellite._originalRuleTriggered(rule);
};
// Store a reference to the original method
_satellite._originalRuleTriggered = _satellite._ruleTriggered;

• Publish this rule, and every time a rule fires, you’ll see a clear log entry in your browser’s console with the rule’s details.

3. Filter Console Logs for Launch Events #

If you just need a quick way to spot Launch-related activity:

• Open your browser’s console
• Type Launch into the filter bar. This will narrow down all logs to only those generated by Adobe Launch, including rule trigger events (make sure Launch’s debug mode is enabled first).

Just a heads-up: _satellite.Logger.getHistory() was deprecated in newer versions of Launch, so the above methods are the official recommended replacements.

内容的提问来源于stack exchange，提问作者raj