Note: This feature is currently available in an Open Beta program.

Salesforce Commerce Cloud (SFCC) is one of the most widespread tools in the eCommerce industry, and for good reason. This all-in-one resource allows users to create seamless eCommerce experiences in both B2C and B2B contexts, fulfill sales on multiple channels, and collect insightful data on customer journeys. SFCC also has its own logs system to provide back-end context when errors occur, which pairs well with Noibu’s session recordings. To that end, we’re happy to announce a new integration to pull SFCC logs events into the Session Timeline. This creates a direct link between sessions in Noibu and log entries in SFCC, so you won’t have to switch back and forth between the two tools to collect insights on SFCC errors.

However, the integration is about more than just convenience. Integrating SFFC logs with the session timeline comes with several benefits that you won’t get by using the two tools separately:

• Extended log retention: Most SFCC instances retain logs for five days. Noibu’s session timeline, however, will retain logs for 90 days so you can access these insights for a longer period.
  • On average, there is a two minute delay between when a log is produced on SFCC and when it shows up in Noibu, so you can access insights with immediacy.
• Structured fields: Logs in SFCC appear as a raw message that can be hard to parse. In Noibu’s session timeline, the logs display in a digestible table of fields and values, which helps you quickly find relevant information.
• Relevant log types: SFCC records several log types, but the Noibu session timeline only collects four of them: error, customerror, warn, and customerwarn. These are the most relevant log types for issue resolution.

SFCC Logs in the Session Timeline

[sfcc-logs-collapsed]

When enabled, SFFC logs will appear as event entries in the session timeline. By default, the logs are collapsed, but you can click the arrow next to an entry to expand an SFCC error log. Each log entry lists the SFCC session ID, Noibu session ID, and any of four blocks of data:

• Request Information
• Stacktrace
  • This block includes a button to copy the Stacktrace.
• System Information
• Log Source

[sfcc-logs-expanded]

Each block can be collapsed or expanded as necessary. Please note that lines of data in each block, and the blocks themselves, will only appear if the information is available.

[sfcc-logs-gif]

The SFCC logs integration is an opt-in feature. Review our guide to Enabling SFCC Logs.