Wake, by GTM Cloud · Prove · Early access
Salesforce field history tracking beyond 20 fields, with a way to restore a value
Wake logs changes to the fields and objects you choose, past the native limit of 20 fields per object and a fixed retention. The record shows old value, new value, who and when, beside Salesforce’s own history.
You know this one
A message arrives in Slack, forwarded from a VP: “Who changed the amount on this deal, and what was it before?”
You open the record, then the history. Nothing. The field was never one of the 20 you picked. Or it was, and the change is older than the log keeps.
Either way you’re now doing archaeology in email threads, asking three people whether they touched it. A number moved a forecast, and the honest answer is “we can’t tell.”
How to get Salesforce field history tracking beyond 20 fields
A wake is the trail a ship leaves behind it. Every change to a monitored field leaves one.
Native Field History Tracking covers 20 fields per object and keeps changes for a fixed period. Wake logs what a field was, what it became, who changed it and when, for the fields and objects you choose, and you set how long the history is kept.
On the record, Wake’s log sits beside Salesforce’s own history, marked by source, so nothing you have today is replaced. Anyone who can edit a field can restore an earlier value from a logged row.
See it first. Take it back. Keep the receipt.
| Preview | Undo | Prove |
|---|---|---|
| Native and extended history together on the record, marked by source. | Restore This Value on any logged row; the restore is logged too. | An Audit tab across every record of an object, with CSV export. |
What you get
More than 20 fields, and retention you choose
Wake stores changes in a Big Object, so you pick the fields and how long to keep them. Each entry holds the old and new value, who made the change, and when.
Native and extended history, together
The record page shows both, marked by source, with a filter for each.
Restore This Value
Users who can edit a field get Restore This Value on any logged row. The restore is logged too.
Configuration, not a trigger per object
Search for the fields to monitor, queue them, and deploy the object’s trigger from the app. There’s no hand-written trigger for each object.
An Audit tab for the whole object
See every logged change to an object’s records, newest first, with filters by field, source and date range, and export the log to CSV.
How it works
- Enable an object. On Settings, search for the object and enable it.
- Choose fields. On Monitored Fields, add the fields to log and save.
- Deploy the trigger. From Settings, deploy the object’s trigger. Logging starts.
- Show it to users. Add the Wake component to the record page.
Two readers, two reasons
If you’re the admin
Search for the fields to monitor, queue them, and deploy the object’s trigger from the app. You set how long history is kept.
If you’re the one signing off
When a number is disputed, the question is always who changed it, when, and from what. Wake answers that for the fields that matter to you, for as long as you’ve decided to keep it.
Today, and with Wake
| Today | With Wake |
|---|---|
| Field history capped at 20 fields and a fixed retention | You choose the fields and how long the history is kept |
| Who changed a value can be impossible to prove | Every change records the user and the time |
| Reversing a bad edit means finding the old value and retyping it | Restore This Value from the log |
| A new tracked object means a developer and a deployment | Pick fields in the app, deploy the trigger from Settings |
Where it’s strong, and what to know first
We’d rather you find the limits here than after you install.
Where Wake is strong
- More than the native 20 fields per object, with the retention you choose
- Old value, new value, who and when, with readable labels for picklists and lookups
- Restore This Value for anyone who may edit the field
- Shown beside native history, so nothing you have today is replaced
- Configuration only, with no hand-written trigger per object
Good to know before you install
- History is stored in Big Objects, so your org needs to be able to hold them. You read it in the app’s log and Audit tab, or in a CSV export.
- Wake records changes from the day you start monitoring a field. Earlier changes aren’t back-filled.
- In production, triggers for objects other than Account, Contact and Opportunity go out with your usual release process. The app deploys them directly only in a sandbox or developer org.
Questions people ask
Do we turn off native Field History Tracking?
No. Wake works beside it. The record shows both, marked by source, with a filter for each, and the settings tell you whether native tracking also covers a given field. Nothing you have today is replaced, so you can run both side by side.
Who can see the history?
Only people who could already read the record, the field and the object. The log and the Audit tab follow sharing and field-level security, so nothing that was closed gets opened up. A custom permission also hides the component from people who don’t need it.
How much work is a new object?
Pick the fields in the app and deploy the trigger from Settings. In production, objects beyond Account, Contact and Opportunity follow your normal release process, because the app deploys triggers directly only in a sandbox or developer org. There’s no trigger to write by hand.
Where is the data kept?
In Big Objects inside your org. Nothing leaves Salesforce, and a scheduled cleanup applies the retention you set, with start and stop controls. You read the history in the record log and the Audit tab, or export it to CSV.
How many fields can Salesforce field history track?
Native Field History Tracking covers 20 fields per object, and it keeps changes for a fixed period. Wake isn’t bound by that limit. You choose which fields to log, search for them in the app, and decide how long the history is kept.
Can you restore a previous field value in Salesforce?
With Wake, yes. Anyone who can edit the field gets Restore This Value on any logged row, and the restore is logged too. The value comes from the log, so it works for changes made after you started monitoring that field.
Works well with
- Sextant: compare a record with a data provider’s and sync a value. Wake logs changes to the fields you monitor.
- Portage: see what a bulk load will do with a preview, then keep a history of what it changed.
Wake is part of the Prove stage of the lead-to-renewal map. Want help rolling it out? See our Salesforce services. Every app installs by itself. None needs another.
Built on the platform
- Native to Salesforce. Changes are stored in Big Objects inside your org.
- Respects security. The log and Audit tab show only records, fields and objects the person could already read.
- Three permission sets, plus a custom permission to hide the component from people without access.
- In-app guides for admins and users, in English, German, Spanish, French (Canada) and Portuguese (Brazil).
Pick the field people argue about
Ask for early access and a walk-through on one of your own objects. Change a value, see who and when, and restore it.