Change History is a historical log of entity changes made within your Project.
Change History provides a historical log of changes (creations, deletions, and updates) made to the entities in your Project. The data helps you to do the following:
- track and review changes made to a Project, for example, for security auditing.
- determine the most interacted entities by Customers and commercetools Composable Commerce users.
- identify usage patterns, for example, to figure out if additional training is required.
Change History table
You can view the logged data in the Change History table. To access Change History, from the Merchant Center main menu, go to Audit log > Change history.
By default, the Change history table displays the most recently modified record at the top. The table is generated when the page is loaded and is not updated automatically thereafter. To update the visible data, click the Refresh icon.
The Change History table has the following columns:
Depending upon your specific table settings, not all columns may be visible in the table view.
User: displays information about the user who updated the entity.
- Merchant Center user name is displayed when change was made through the Merchant Center.
- Platform is displayed when change was made through ImpEx.
- ExternalUserIDstring is displayed when change was made through an API Client and the external user ID was provided for the respective API call.
- Out of the platform is displayed when change was made through an API Client and no external User ID was provided.
Business unit: provides the key of the Business Unit associated with changes to Orders, Quotes, and Quote Requests.
The Business unit column is only available in B2B-enabled Projects. To add this column to your table, use the column manager.
Customer: provides information about the customer making the change.
- Customer email address is displayed when change was made through an API Client and the respective API call was made for an authenticated Customer.
- Anonymous session is displayed when change was made through a Customer who was not authenticated, for example, when using guest checkout.
- ----- is displayed when no information about the customer is available.
- Customer deleted is displayed when change was made through an API Client and the respective API call was made for an authenticated Customer, but for any reason the Customer was deleted after the event got logged.
Last modified: displays the date and timestamp of the modification along with the action taken, which can be Create, Remove, or Update.
Changes: lists details about the entity modifications along with the changed values.
Current entity: displays the name of the modified entity. To show the details of the current version of the modified entity, click its name. By clicking the filter icon next to the current entity, the changes of the selected entity will be displayed exclusively.
Entity type: indicates the type of the modified entity.
Source: displays the name of the application or client used to drive the change:
- Merchant Center
- API Client Name: name set during the creation of an API Client
- API Client Not Available: a valid name is not provided when using an API Client to change entities
Version update: displays the version of the entity before and after the change.
Stores: displays the Store or Stores associated with a given change.
The Table settings drop-down allows you to modify the data displayed in the screen.
To add or remove table columns, select Column manager. You can drag the columns between the Hidden and Visible columns and reorder the columns by moving the column entries up or down the stack.
To save the changes, click Save settings. To discard the changes, click Cancel.
To modify the table layout, select Layout settings and configure the following:
- Text visibility: displays full text or text preview inside cells
- Row density: expands or reduces the padding inside cells
To confirm the changes, click Save settings. To discard the changes, click Cancel.
Change History is the aggregation of all changes within your Project, and can grow to be very large. Hence, you can filter the log by the time period or column.
Filter by time
By default, the Change history table filters changes made in the last 24 hours. You can also filter changes for the following date ranges:
- Last 7 days
- Last 30 days
- Custom date range
Filter by column
To filter individually, click Filter and select any of the available filters in the Add filter drop-down. You can combine multiple filters to further refine the displayed changes.
API client: select the API Client to filter by.
Business unit: select the Business Unit to filter by. This filter displays changes made to Orders, Quotes, and Quote Requests belonging to the selected Business Unit.
- The Business unit filter is only available in B2B-enabled Projects.
- To view changes made directly to a Business Unit (instead of changes made to entities belonging to a Business Unit), do the following:
- Click Filter and select Entity Type from the Add filter drop-down.
- Select Business Unit and click Apply and close.
- In the Current entity table column, click the Entity's change log button next to a Business Unit to display a filtered list of results.
Changes: select an entity and the related change or action to filter by.
Customer ID: select the Customer ID to filter by.
Entity type: select one (is) or more (in) of the supported entity types.
Source: select one of the supported sources:
- Merchant Center
- Out of platform (API Client)
Stores: select one or more Stores to filter by using the drop-down or by searching for a Store's key.
Only users with permissions to view or manage Customers or Orders for a Project globally, or for specific Stores can view this filter. If a user has permissions to view a limited subset of Orders and/or Customers for specific Stores, the user will only be able to select those Stores.
Type of changes: Select the type of entity change:
User: Select the name of the user to filter by.
To remove all filters, click Clear all.
Exclude changes initiated by background processes
Change updates are either user-initiated or initiated by a background process. User-initiated changes are manual updates made by the user. Changes initiated by background processes are updates that cannot be triggered manually by a user. They are triggered automatically as a result of user-initiated changes. Some examples are:
- Sets application version for Discount Codes - the
applicationVersionproperty is only used internally to reserve the use of a Discount Code. Its value is managed by the API, and can change at any time due to internal and external factors. It should not be used in customer logic.
isvalidfor Product Discounts - the
isValidproperty is added as true when the
validFromdate is reached, and then removed after the
validUntildate is reached.
- Changes review rating statistics for Products - the
reviewRatingStatisticsproperty is updated when the reviews of a Product change.
- Changes variant availability for Products - the
variantAvailabilityproperty is updated when an Inventory entry related to a Product is updated.
- Changes line item name for Shopping Lists - the
lineItemNameproperty is updated in an eventually consistent manner when a Product’s name is changed and referenced in a Shopping List.
To exclude changes initiated by background processes from displaying in the Change history table, click the Display platform-initiated changes toggle.
Merchant Center provides contextual Change History views for entities. To access the contextual Change History view for an entity, click Open change history on the respective entity's details screen.
The contextual view provides a Change history table specific to the entity. The columns visible in the table depends on your specific table settings for the respective entity.
Although the Stores column is visible by default in Audit Log, when viewing Orders and Customers entities in contextual view, it must be made visible using the column manager.
Merchant Center permission
By default, all members of the Administrators Team have access to the Change History in the Merchant Center. The Administrators Team must assign the View all: Audit Log permission to the respective Project and Team.
API Client permission
To access the Audit Log APIs, you must create an API Client that includes the Audit Log scope. You cannot edit an API Client after it's saved.