Entity History displays the historical updates made to entities. It can be accessed via Knowledge Graph > Configuration > Entity History, or from the Entity Edit view for a single entity, or via the Logs API.
| UI | API | |
|---|---|---|
| Requires Developer App | No | Yes |
| Includes Update Metadata (Event Type, Timestamp, Value, etc.) | Yes | Yes |
| Filterable | Yes (limited) | Yes |
| Sortable by Timestamp | Yes | Yes |
| View Previous Content for a Given Update | Yes | No |
| Restore Field Values | Yes | No |
| Returns Entity UID (Yext ID) | No | Yes |
| Maximum Page Size | 100 | 1,000 |
Entity History UI
The Entity History page displays a table of past entity updates. By default, history is displayed by operation. Toggle to view by individual events.
View by Operation

Click an operation to view operation details, which include hero metrics (entities updated, created, deleted), expanded actor details, fields updated, a table of individual events, and options to undo or reapply the operation.

View by Event

Click an event to view event details in a side panel: entity, event type, actor, language, operation ID, and the previous and updated field values for "Field Updated" events (viewable in UI format or JSON).

Undo and Reapply Field Updates
From the Entity History UI, you can undo or reapply operations and events to restore field values on entities. This applies only to Field Updated event types and is only available in the UI.
Undoing an operation or event restores the affected field values to whatever they were before the operation or event took place.
Reapplying an operation or event re-adds the affected field values as they were in the original operation or event.
Both actions only apply to the entities and fields that were edited by the original operation or event. Any entities or fields not part of the original operation or event will not be changed.
Note: This is best used when you want to undo changes to specific fields on certain entities. To restore all fields on an entity profile to a previous point in time, use the Restore Entity Data from a Previous Date approach instead.
Steps
- Navigate to Knowledge Graph > Configuration > Entity History. Toggle to Group by Operation or All Events, depending on whether you want to undo an entire operation or a single event.
- Locate the operation or event you want to undo using the filter options at the top of the table:
- Date: filter by when the change took place
- Entity: filter by entity name (Event view only)
- Entity Type: filter by entity type (Event view only)
- If you are undoing or reapplying an entire operation, click on the desired operation. From the Operation Details page, click either Undo this Operation to undo the changes made in the operation, or click Reapply these Updates to reapply the changes that were made in the original operation.
-
To undo or reapply a single event: find the event in the Entity History table, click the three-dot icon on the right side of the row, and select Undo this Change or Reapply this Value.

Note: Operations can also be selected via the three-dot icon on the Operations view of the Entity History table.

Not Supported
Undo and reapply are not supported for:
- Any event type other than Field Updated (note:
FIELD_UPDATED_INHERITEDis not supported) - Multiple changes on the same field for the same entity
- Newly created entities whose ID shows "Value Pending"
- The following fields: Country Code, Coordinates (Display, Dropoff, Pickup, Routable, Walkable), Locale, any image fields
Entity History via API
Entity History can be accessed by querying the entityHistory table via the POST query endpoint of the Logs API. You will need a Developer App with Logs endpoint permissions set to read-only. See the Create an App in the Developer Console guide to get started.
For sample requests and responses, see the Logs API documentation.
Events
| Event Type | Description |
|---|---|
ENTITY_CREATED |
The entity was created. |
PROFILE_CREATED |
A language profile was created for the entity. |
FIELD_UPDATED |
A field value was updated on the entity profile. |
FIELD_UPDATED_INHERITED |
The rendered value for a field was updated due to an update to an inherited field's value. The raw value for the inheriting field was not changed. This occurs when a primary language profile field update carries over to alternate profiles, or when a source field value for an embedded field is updated. |
PROFILE_HIERARCHY_UPDATED |
The primary language profile was changed from one profile to another. |
PROFILE_DELETED |
A language profile was deleted. |
ENTITY_DELETED |
The entire entity was deleted. |
Actors
An actor is the source responsible for an event in an entity's history. Actor details provide further information about the exact source.
For example, an event could have been caused by a User (the actor) via Entity Edit (the actor details).
Most Yext System updates appear as a separate action triggered by a Yext User event. For example, updating an Address field triggers two rows in Entity History: one for the Yext User edit, and one for the Yext System geocoding that follows.
Actor Types: App, Yext System, Yext User, Yext Account Team, Connector.
Actor Details
| Actor Detail | Description |
|---|---|
| Entity Edit | Edits made to fields from the Entity Edit screen in the Yext UI. |
| Storm | Edits made directly in the Yext UI, outside of Entity Edit. |
| Entity Upload | Edits made via Knowledge Graph > Entities > Add Data > Entity Upload. |
| API | Edits made via an API endpoint. |
| EnhancedLists | Edits made via Knowledge Graph > Menus, rather than on the entity itself. |
| M4 | Edits made via Configuration as Code (the CLI or Admin Console). |
Employee [ID] on behalf of User [ID] (TemplateServer:applyTemplate)
|
An internal tool used by Yext employees to apply entity templates on a client's behalf. |
| SmartLabeler | The backend system that manages which saved filters an entity belongs to. |
| GeocodeServer | The backend system that creates a geocode based on an entity's address. Additional details may appear in formats such as: (source user id: 12345678, details: PIN_YOUR_BUSINESS) or (source user id: 1234, details: Geocode Validation Task). |
| TimezoneServer | The backend system that assigns a time zone based on an entity's address and/or geocode. |
| ListingsProfileUpdaterMessageHandler | The backend system that monitors Google Place IDs for listings. If a new Place ID is found, Yext updates the corresponding entity with the new ID. |
| match set change | The backend system that monitors Facebook listings. Indicates when a new Facebook match is pulled in for a listing. |
| profile pic fetch for partner 559 due to linkage change | Related to "match set change." When a new Facebook match is pulled in, Facebook cover photo, page URL, and profile photos may be updated on the corresponding entity. |
Bing (approved by [publisher name])
|
A user approved a suggestion from another publisher, sourced from Bing. |
| EntityTypeUpdateHandler | The backend system that handles entity type conversions. |
| EntityReferenceUpdater | The backend system that handles two-way entity relationship updates. If Entity A is updated and has a two-way relationship with Entity B, this system applies the same update to Entity B. |
| PurgeReopenDateTask | The backend system that removes holiday hours from entities once they have passed. |
| feedback | The backend system that pulls in publisher data for certain fields. For example, if an entity has no profile picture and syncs to Facebook for the first time, this system may populate the profile picture from the Facebook listing. |
| IsoRegionServer | The backend system that provides an ISO code for a given location. |
Legacy Actor Details
These actor details may appear in older history but will not appear on new events going forward.
| Actor Detail | Description |
|---|---|
| Feed Upload | Legacy name for Entity Upload, prior to 2018. |
| Publisher Suggested Edits | Legacy version of publisher suggestions, prior to 2020. |
Limitations
Global
- Entity History is limited to the last three years (1,095 days). Events older than three years are deleted.
- Newly created entities appear with an undefined entity type and an ID of "Value Pending." It may take up to one hour for these values to sync. Field values cannot be restored until they resolve.
- It may take up to five minutes for new update logs to appear.
UI
- Exporting logs is not currently supported.
-
FIELD_UPDATED_INHERITEDevents cannot be restored. - Field values cannot be restored on: Country Code, Coordinates (Display, Dropoff, Pickup, Routable, Walkable), Locale, or any image fields.
API
- Field updates cannot be undone or reapplied.