Rachel_Breden

Lead owner = sales owner. SFDC Sync: Lead/Account Owner Sync - Marketo Docs - Product Documentation   Contact owner I don't believe is a standard field so you'll want to check your field mapping to see how that is setup and synced.  Change Owner flow step changes the sales owner because account info sync is one way from SF to Marketo.  ... View more

That helps, thank you!  ... View more

Awesome. I was hoping it worked that way. Thanks! ... View more

I would recommend that the way the content is being displayed be re-evaluated. Here's one example.  Note that this is only an example and you can change it up how you'd like as it all comes down to strategizing your needs, what Marketo is capable of doing, and the ease of putting it all together. As of 7/13/16, this is the information we have on file for you.  Please complete the bolded (or you can color code them to red if you'd like) items: Applied for Admission OR Need to Apply for Admission Sent us transcripts OR Need to Send us Transcripts Sent us ACT/SAT scores OR Need to Send us ACT/SAT Scores Complete testing OR Need to Complete Testing Filed FAFSA OR Need to File FAFSA This way, you can have 1 segmentation with 5 segments.  Each line item would be a different section in the email that the segmentation/snippet is applied to. If a record applied for admission and sent their ACT/SAT scores, their email would then display: As of 7/13/16, this is the information we have on file for you.  Please complete the bolded (or you can color code them to red if you'd like) items: Applied for Admission Need to Send us Transcripts Sent us ACT/SAT scores Need to Complete Testing Need to File FAFSA ... View more

The article shows creating a new form, but you can in fact use any form that exists in your Marketo instance. And it doesn't need to have only a button, though that helps make it clear (to Marketo admins) that the form isn't intended to be seen by the public. Creating a dedicated form also means the form name will show up distinctly in reports. What a background form post really is, is a hidden form (no HTML <FORM> is shown to the lead) whose accompanying Marketo Forms 2.0 JavaScript object can be used to add fields and submit the form directly to Marketo. It's suitable for use by Drupal or any other CMS's forms, but your developer needs to pass the values on your Drupal form to the Marketo form object, then call submit(). Typically the Drupal form post would be cancelled, but you could commit the form data to both systems if you wanted. ... View more

We set the form to route to the raw Marketo path. It did not appear to work at first, but we realized the page was cached, so we cleared the web history on our browsers and now it works fine. Thank you all for your input! ... View more

That was my intuition, but I didn't know if it was possible. I will put in a support request as the others suggested and see if it can be fixed. Thanks! ... View more