How to use Field History Tracking

When a record is updated, knowing who made changes and what they changed is critical. 

With field history tracking, Enterprise users can review any changes that have been made to any record, including:

Tasks Events
Contacts Organizations
Leads Opportunities
Projects Phone Calls
Products Price Books
Opportunity Line Items Price Book Entries
Marketing Prospects Marketing Lists
Marketing Journeys Custom Objects


Users can review changes that are up to 18 months old, but Enterprise customers can request an extension from our sales team.

The changes to the following fields cannot be captured in the audit log:

  • Formula fields

  • Auto-number fields

  • Created by fields

  • Last modified by fields

  • Expected Revenue fields

  • Binary fields

  • Fields with values longer than 255 characters

If you delete a standard or custom object, the data will not be deleted. However, if your account is deleted, the data will be deleted.

Field History will not appear on records by default. Admins will need to add the field to their Page Layout’s related tab. Any objects that do not have a related tab will not have an audit log to review, but the number of changes can be reviewed in the Field History Report.

To review changes

  1. Open a record and select the Related tab.
  2. Scroll down to Field History. Here you will be able to see who made changes, the date the changes were made, and how many values were changed.
  3. To see what was changed, click the field under the Changed Values column.
  4. Here, you will be able to review when a change was made, what the new value is, and what the previous value had been.

    If the value is longer than 255 characters long, it will not appear in the audit log. They will, however, be marked as edited.

Administrators can also review changes in the Field History Report located in the Other Reports section in Advanced Reporting. This report will only record the number of changes that have been made to records; to review what has been changed in a record, the user will need to review the audit log.


Was this article helpful?