ok... I was able to test this, but I believe that I'm not successfully assigning the incoming Marketplace LeadSource to the new field.  I tried with a trigger for the Form Filout MarketplaceLeadBackEnd, and filterer "Person Not Created in the [past 5 minutes] so as to only process the existing Leads  ... View more

OK.  Thanks.   Is there an easy way to do an API test.  Just as a caveat, I am not a programmer/developer.  Is there a way for me to test this api forms integration without soliciting them to send a sample api call?  I want to find out if I can can do this field manipulation, prior to the processing of the incoming Lead.  Ex. Lead Source to get assigned to a  Temp LeadSource field, then process the lead with the incoming api field values, which will populate the Person/Lead Source field with a VendorSpecific Value, for which I would move to some string field that accepts tokens, Here is my thinking on the steps:  Create Temp field in Marketo (only Marketo, called TempLeadSource) that would temporarily hold the HID Marketo Lead Source (IF this was an existing Lead), until after the integration.  Here are the the steps: IF Lead exists, Change Data Value of TempLeadSource field to HID Marketo Lead/Person Source to  and then null out the HID Marketo Person Source field (to allow the Marketplace Azure LeadSource value to populate this, since it's a blocked field if not empty) Then trigger Marketplace integration Smart Campaign (or call this Smart Campaign) to work and populate the Lead Source with the Marketplace Azure info (their field called LeadSource)   Move that Marketplace Azure Offer info (LeadSource) to another field (of  TYPE String… so that it can be used later as a token, for re-assignment ) Re-populate HID Marketo Person Source with the TempLeadSource value (which was the original Lead Source value prior to this integration).  This field is not blocked for Marketo Flow steps, so it will work. Please let me know if you think this is sound thinking or if there's something I'm missing here. Thanks guys, Nancy ... View more

Yes, there is a specific form dedicated to the Microsoft Leads, so the problem is that we would have to make LeadSource no longer blocked, which seems to be a bit dangerous, since we are heavily reliant on this field not changing from the original Marketo Lead Source to what Microsoft is trying to populate it with . We use this field for numerous reports.  It would obviously be quite easy to "Change Data Value" to populate say, Person Notes IS {{lead.Lead Source}},  BUT if this was an existing lead, this field would already be populated with the true value and the field is blocked.  If it were unblocked, how would I move this original value to another field X before the new value is passed along, then populate what Microsoft is passing as LeadSource to Person Notes, then move field X back to Lead Source? ... View more

Greg, this setup you have outlined here, is exactly how we have ours setup, including leveraging the scoring to reach a sales ready threshold.  The problem lies in the fact that our programs our synced with SFDC from the onset, so the leads are assigned to a Marketing Queue right away, so when the leads reach "Sales Ready", they cannot run through the assignment rules again, called from Marketo, since they already have a lead owner.  So, unfortunately, this sort of falls apart, short of either recreating the assignment rules in SFDC OR creating an SFDC api workflow to send the lead back through the Lead Assignment Rules, once they reach the threshold of being Sales Ready or MQLd.  Is this your understanding as well? ... View more

This is extremely helpful to know the limitation and understand the workaround.  This is what I was suspecting.  One more question, when a campaigns is synced with Salesforce, does this automatically assign a lead owner as soon as a new Lead becomes a member of the campaign? Or only when the call to Use Auto Assignment Rules is engaged. ... View more