What are the various Change Sources one can find under a contact's property history?

Last updated: June 27, 2017

Available For:

Product: HubSpot Marketing
Subscription: Basic, Professional, & Enterprise

Within HubSpot, you can review a contact's property history to see how its properties, and contained values, have been updated over time. Next to each dated change, you will see a Change Source: the app, process, or job that caused the change. Please find below a listing of these Change Sources accompanied by a brief description.

  • Analytics - Update to property comes from web analytics/visits/traffic information.
  • Workflows - Change caused by a workflow.
  • Social - Social Media engagement captured by our Social app.
  • API - API-related (user employed an API to get new information into HubSpot).
  • Salesforce - This was initiated by a change made to the record in Salesforce, which then synced to HubSpot.
  • Email -  These changes are caused by a contact's email activity (e.g. clicks on an email message).
  • Migration - HubSpot internal job.
  • Batch_Update - When a user employs our 'Create or update a group of contacts' API endpoint ( to update/create contacts.
  • Engagements - These updates come from changes to interaction properties on a contact record, such as Notes Last Updated or Last Contacted. In other words, Engagements update default contact record properties that rely on some interaction with the record.
  • Email address - When you see an email address of a HubSpot user under Source it means that particular user went to the contact record and manually changed a property.
  • Forms - A submission on a HubSpot form (or the HubSpot Forms API) caused a change.
  • Forward_to_CRM - This particular change is tied to an interaction with HubSpot Sales, more specifically the logging of a contact's email response to your original, externally sent email (e.g. Gmail) into your HubSpot CRM.
  • BCC_to_CRM - This particular change is tied to an interaction with HubSpot Sales, more specifically, logging an externally sent email (e.g. Gmail) into your HubSpot CRM.
  • Background Task - This is the result of a change that caused a backend task to trigger. For example, if you used a workflow to update a contact's Lifecycle Stage and the change to the contact's Lifecycle Stage then triggered Lead Scoring (because of current Lead Scoring rules that are set in place) to reprocess the contact record and give it a new HubSpot Score. Separately, the merging of two contact property's options will trigger a 'Background Task' so all related contacts are updated with the new merged-into value.
  • Sales - Completed action within the HubSpot CRM platform.
  • CRM_UI - A change automatically made by the HubSpot CRM platform. For example, if the Lifecycle Stage Sync option is turned on in the CRM and a contact's Lifeycle Stage changes when it is associated with a company as a result of the setting.
  • Deals - Change caused by HubSpot CRM's Deals object.
  • Companies - Change caused by HubSpot CRM's Companies object.
  • From via merge - Change triggered by the merging of two contacts. This change can also be triggered when an email is forwarded from one known contact to another and any related submissions occurred with a known email address, therefore the conversion is merged.
  • Calculated - This change source applies only to specific properties, such as Last Modified Date, for which HubSpot does not keep a history of incremental changes, but instead calculates a new value at the time of each update. 
  • Extension - A change to a property was made using contact profiles in Gmail

Was this article helpful?