Review this screenshot. What could be wrong about this sync rule?
The operator should not state “equals.” It should instead state “contains.” The rule logic is wrong — a contact can
Read moreThe operator should not state “equals.” It should instead state “contains.” The rule logic is wrong — a contact can
Read moreBy adding an action to the second and third rule that says ‘only perform updates’. By adding a filter to
Read moreWe don’t have any contacts named John nor Mary in our contacts database. It does not take into account that
Read moreContacts can only sync to either Google or Outlook, not both at the same time. The sync with Outlook is
Read moreTags have to be created beforehand in Mailchimp through its user interface, so a direct field mapping won’t work here.
Read morePieSync is cheaper when it only runs as a one-way sync. You don’t want to make any inadvertent changes to
Read moreOnly the default HubSpot properties for contacts — custom properties can be found elsewhere HubSpot properties for contacts, along with
Read moreWhen I change someone’s first name in Google Contacts, the first name in HubSpot should not change. Only changes that
Read moreSync up “First name” to “Last name”, two-way Sync up a yes/no field to a text field, one-way. Sync up
Read moreThere’s no limit to the number of actions you can add in a sync rule. If the number of filters
Read more