6 Replies Latest reply on Jul 14, 2015 4:01 PM by Sanford Whiteman

    Inferred fields in forms

      We're setting up new Marketo forms.  We'd like to populate key fields, such as Country and State with the inferred data, IF its known.  We've been able to pull this in for the Inferred Country, but some of the other inferred fields aren't showing as options:

      - Inferred City

      - Inferred State

      - Inferred Postal Code

      - Inferred State Region

      Does anyone know why, or how to enable these fields as options?

        • Re: Inferred fields in forms

          Hey Jenny!

           

          Is the data simply not populating at all on the lead records, despite them coming in on a Marketo landing page / form combination? You don't need to add the inferred fields to the form, they should populate automatically once the lead fills out the form - since it's making some assumptions based on IP address.


          From there, you can use tokens to overwrite your country/state fields if you'd like.  So, you'd have a triggered or recurring batch campaign that would look like:

           

          If (STATE) is (Empty) then change (STATE) to {{lead.Inferred State Region}}... or something like that.  Just a head's up if you go that route, make sure that if you are syncing w/ a CRM that the fields match up and that the countries/states are in the CRM pick-lists.  (E.g. don't automatically use full state names if the CRM is expecting only abbreviations)

          1 of 1 people found this helpful
          • Re: Inferred fields in forms

            Hi Jenny,

            Just for your reference, I have seen cases where the inferred fields do not match the lead's actual values.  This inferred information is coming from the IP address.  This could cause a problem, for example, when employees VPN in to a main server but are located somewhere else in the country.  Their main server may be in California, so you get that inferred information, regardless of if they actually are in California, New York, or any where else.

             

            Thank you,

            Courtney

            1 of 1 people found this helpful
              • Re: Inferred fields in forms

                Definitely true, but if you use the state/country field as the designator for your lead assignment, it's still probably better to copy the value over as opposed to keeping the blank value and doing the manual research.  I wouldn't use the inferred values for stuff like entitlements or directing people to regionally-specific events, but probably good enough for internal use.

                 

                • Re: Inferred fields in forms
                  Sanford Whiteman

                  ... yep, and not only the VPN/proxy situation, but anybody on mobile can look like they're in state X when they're actually on their way to or from their work state Y, or vice versa.  I live in one of the US's many "tri-state areas" and you'd encounter a huge variance if you assumed someone's smartphone was always left at work.

                   

                  I think Rob's suggestion of using the inferred values in the absence of better values works provided you also flip a boolean field like Tentative Address = true or similar.  Otherwise Sales won't know which leads demand manual research.

                • Re: Inferred fields in forms

                  Hi everyone, thank you so much for the feedback!

                   

                  I understand that inferred data is not always correct.  In this case, we're attempting to pull the Inferred Country, Inferred State & Inferred City into the form as pre-populated data for the actual Country, State, City fields.  This way, the consumer can view and edit the values if they're incorrect -- but they have less fields to complete if it is accurate.

                   

                  Right now, the Inferred Country is an option for us to pull into the form (as a hidden field) so that field is working to populate country.  However, the Inferred State and Inferred City aren't field options for us to pull into our form.  Do you know why?

                    • Re: Inferred fields in forms
                      Sanford Whiteman

                      Some fields just aren't allowed in forms, and the reasons aren't fully documented (we know Person Notes isn't allowed because it might leak nasty notes from Sales, but not every field has such a clear justification).

                       

                      But another problem you need to be aware of is Inferred * fields will not exist on a browser's first hit to the LP.  They will exist on the second hit because the anonymous lead has been created and its fields fetched into the page.  Make sure you're accurately testing this.

                      1 of 1 people found this helpful