B2C Logging
ListedB2C Logging tracks customer interactions across your Salesforce Commerce Cloud instance for deeper insights and improved personalization strategies.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add salesforcecommercecloud/b2c-developer-tooling --skill b2c-logging -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
salesforcecommercecloud
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
We could not read this skill's source, so none of the checks below were run.
About this skill
What it does
The b2c-logging skill enables AI agents to capture and analyze detailed operational data from Salesforce Commerce Cloud B2C environments. It provides visibility into system events, errors, and performance metrics essential for troubleshooting and optimization.
When to use it
- Diagnosing checkout failures or cart abandonment issues in real-time.
- Monitoring API latency and response times during high-traffic sales events.
- Auditing user interactions to identify patterns in failed transactions.
- Generating compliance reports on data access and system modifications.
Key capabilities
- Aggregates logs from various B2C Cloud components into a unified view.
- Filters specific log entries by severity, timestamp, or module type.
- Correlates application events with customer session IDs for traceability.
- Exports structured log data for integration with external analysis tools.
Example prompts
- "Summarize all error-level logs from the checkout service in the last 24 hours."
- "Identify any API timeouts occurring during the peak shopping window between 2 PM and 4 PM."
- "Show me a timeline of user session ID 'abc-123' including all system interactions and errors."
Tips & gotchas
Ensure your AI agent has appropriate read permissions on the Commerce Cloud instance before querying sensitive operational logs. Be mindful of log volume limits; if data is too extensive, request specific date ranges or filter by error type to maintain performance.