5 Replies Latest reply on Jun 29, 2017 1:33 PM by Tim Cerato

    Sync to SFDC Changed Postal Code

    Nick Burton

      A lead visited our website and filled out a form where they gave us their Postal Code. After qualifying their self by visiting key web pages and downloading a pdf, they became qualified and synced to SFDC. However, in the Lead History in SFDC it shows that the Marketo Sync User changed the Postal Code from a Canadian one to 90210. Any thoughts as to why this would happen and maybe what workflows triggered this? The inferred state/region based off of the IP address closely matched that of the original Postal Code.

        • Re: Sync to SFDC Changed Postal Code
          Tim Cerato

          Hi, Nick - is the 90210 postal code the code that the user submitted via the form? It sounds like the prospect submitted a junk postal code value via the web form (90210 is the postal code for Beverly Hills). 

           

          It sounds like the prospect submitted a junk postal code value via the web form (90210 is the postal code for Beverly Hills). 

           

          I'd recommend evaluating the drawbacks and benefits that would come from blocking field update to address fields. Blocking field updates would prevent potentially bad data from overwriting existing data in the system, but it would also prevent prospects from updating their address if it was to change.

           

          Cheers,

           

          Tim