Become a HubSpot power user — join us for HubSpot Training Day 2017.

Contacts

What does the change source in my contact's property history mean?

Last updated: September 11, 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, which is the app, process, or job that caused the change.

  • Analytics - the property was updated based on web analytics/visits/traffic information.
  • API - the property was updated because a user employed an API to send new information to HubSpot.
  • 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 an update to the contact's HubSpot Score based on lead scoring rules you've set up. The merging of two contact property's options will also trigger a background task so all related contacts are updated with the new merged-into value.
  • Batch_Update - the change was the result of a user using the Create or update a group of contacts API endpoint to update/create contacts.
  • BCC_to_CRM - the change was caused by an interaction with HubSpot Sales, more specifically, logging an externally sent email (e.g. Gmail) into your HubSpot CRM.
  • 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. 
  • Companies - the change was caused by a change to the associated company record.
  • CRM_UI - the change was automatically made by the HubSpot CRM; for example, if the lifecycle stage sync setting is turned on and a contact's Lifeycle Stage changes when it is associated with a company.
  • Deals the change was caused by a change to the associated deal record.
  • Email -  the change was caused by a contact's email activity (e.g. clicks on an email message). Also, when a contact's email address changes, their other email information properties will be changed as well with the change source of Email. More information on these changes can be found here
  • Email address (e.g. user@mydomain.com) - when you see the email address of a HubSpot user under Source it indicates that that user manually changed the property.
  • Engagements - this change source appears when a default contact record property that relies on some interaction with the record is updated, such as Notes, Last Updated, or Last Contacted
  • Extension - the property was updated using contact profiles in Gmail
  • Forms - the change was caused by a submission on a HubSpot form or through the HubSpot Forms API.
  • Forward_to_CRM - the change was 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.
  • From via merge - the change was 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.
  • Integration - the change was initiated by an external integration. 
  • Migration - the change was initiated by a HubSpot internal job.
  • Social - the change was caused by an engagement captured in the social tool.
  • Salesforce - the change was initiated by a change made to the record in Salesforce, which then synced to HubSpot.
  • Sales - the change was initiated by a completed action within the HubSpot CRM platform.
  • Workflows - the change was initiated by an action in a workflow.

Was this article helpful?