Contacts

HubSpot's change sources in property history

Last updated: February 8, 2019

Within HubSpot, you can view a property history to see how its value has been updated over time. Next to each dated change, you will see a change source. This indicates which the app, process, or job that affected the change. The change sources include:

  • 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: the property was updated because 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.
  • Bulk Edit: the property was updated by a user using the Create or update a group of contacts API endpoint to update/create contacts. This could be the result of a manual update or an integration.
  • BCC_to_CRM: the property was updated by an interaction with HubSpot Sales, more specifically, logging an externally sent email (e.g. Gmail) into your HubSpot CRM.
  • Calculated: the property was updated when HubSpot calculates a new value. This change source applies to specific properties, such as Last Modified Date, for which HubSpot does not keep a history of incremental changes.
  • Companies: the property was updated by a change to the associated company record.
  • Contacts: the property was updated by an edit through the contacts dashboard.
  • CRM_UI: the property was updated by the HubSpot CRM automatically. 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 property was updated by a change to the associated deal record.
  • Email: the property was updated 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: the property was updated manually by the user whose email address is stated here.
  • Engagements: the property was updated by an interaction with the record. This change source applies to specific properties that rely on interactions with the record, such as Notes, Last Updated, or Last Contacted
  • Extension: the property was updated using contact profiles in Gmail
  • Forms: the property was updated by a submission on a HubSpot form or through the HubSpot Forms API.
  • Forward_to_CRM: the property was updated by 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 property was updated 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.
  • Integration: the property was updated by an external integration. 
  • Migration: the property was updated by a HubSpot internal job.
  • Mobile iOS: the property was updated by a change in the iOS mobile app. 
  • Social: the property was updated by an engagement captured in the social tool.
  • Salesforce: the property was updated by a change made to the record in Salesforce, which then synced to HubSpot.
  • Sales: the property was changed by a completed action within the HubSpot CRM platform.
  • Workflows: the property was updated by an action in a contact-based workflow.
Free Inbound Marketing Training Learn inbound marketing techniques that range from creating content, using  social promotion, converting and nurturing leads, and all the way to marketing  to your customers. Start the course