Skip to content

Change Logs

Change logs track who changed what, when, and the measured impact of changes to ensure accountability and enable rollback.

Overview

Change logs provide a complete audit trail of all merchandising changes, including who made changes, when they were made, and their impact. All change logs are accessible through the UI in the triggers tab under each rule.

Viewing Change Logs

Change logs are available for each merchandising rule in the Triggers tab:

  1. Navigate to Merchandising → Merchandising Controls
  2. Select a rule (boost/bury, pinning, exclusion, or campaign rule)
  3. Click on the rule to view its details
  4. Open the Triggers tab (or "History" tab, depending on the UI)
  5. View the change log showing:
  6. Who made the change: User who created or modified the rule
  7. When the change was made: Timestamp of the change
  8. What changed: Details of what was modified (e.g., boost level, pin position, conditions)
  9. Impact: Measured impact of the change (if available)

Change Log Information

For each change, you can see:

  • User: Which team member made the change
  • Timestamp: When the change was made
  • Change type: What type of change (created, modified, deleted, activated, deactivated)
  • Details: Specific changes made (e.g., "Boost level changed from +10% to +20%")
  • Impact metrics: How the change affected performance (conversion rate, revenue, etc.)

Using Change Logs

Change logs help you:

  • Track accountability: See who made what changes and when
  • Understand impact: See how changes affected performance
  • Enable rollback: Identify changes to revert if needed
  • Audit compliance: Maintain records for compliance and governance
  • Collaborate: Understand what team members have been working on

Best Practices

  1. Review regularly: Check change logs regularly to stay informed
  2. Document reasons: When making changes, add notes explaining why (if the UI supports it)
  3. Monitor impact: Review impact metrics to understand which changes were effective
  4. Use for rollback: Use change logs to identify and revert problematic changes
  5. Audit trail: Keep change logs for compliance and governance purposes