Delete Tracking

Delete Tracking gives users the ability to track records that have been deleted through the Salesforce UI, ETL, etc. This means that your GRAX dataset stays up to date as users or automation remove records from your Salesforce org in between replication jobs.

GRAX only tracks deletes on records which were already replicated to the GRAX data vault.

How do I enable it?

Delete Tracking is enabled by default for all customers to run once per hour.

Anomaly Detection

When an abnormal amount of deletes is detected, GRAX will send a notification for your consideration.

That is a pilot program being tested as part of GRAX Insights; you will be notified when it is available for use in your environment.

How Does it Work?

Each hour, an automated GRAX process looks for deleted records across all replicated objects. The Salesforce API provides a list of deleted records, and GRAX flags any records in the vault matching the list provided by Salesforce as Deleted.

This is the API call used to note deleted records and as such is governed by any limits placed by Salesforce.

For anomaly detection we calculate a threshold above the median absolute deviation (MAD) in order to identify deletes worth reviewing.

Content/Files

Salesforce doesn't support Content objects (ContentDocument, ContentVersion, or ContentDocumentLink) for this type of delete tracking. The Attachment object, however, is supported.

Click here to see more detailed requirements of objects that Salesforce allows to be tracked as deleted in this manner, which allows you to determine all objects in your org that can be tracked for deletions by GRAX.