Ideas

Now that we can create custom objects, it would be very efficient to be able to create custom object flows through flow steps, exactly as we can do with tasks. For each custom object defined in the admin, we would need 3 flow steps: Create (would take all the fields as input) Update (would require the UID + the fields to be updated) Delete (would required the UID) The create/update could also be replaced with 1 upsert one. Obviously, if it's a SFDC custom objects, the fields available would have to be set through mapping. With regards to Marketo custom objects, all fields created in Marketo should be available to be set in the flow steps. All the fields of the custom objects could be set with tokens. Typical usage : I create a custom object : product interest, with a few fields (Time frame, quantities). I Create the same fields at lead level, that I use in a form. Once a lead fills out the form, I create a custom instance and populate the fields with the lead tokens. We should also be able to update them, though the same mechanism. -Greg ... View more

When an anonymous leads is crated during a visit to our website, we set values in ithe newly created record's 'Initial Online Source' field and other fields that tell us the source of their initial visit to our site.  Later, if a known record for the same lead is created by Sales, we don't set the Initial Online Source field and leave it blank.  Then when we send an email to the lead and the lead clicks the tracked link, Marketo merges the anonymous lead  record with the known lead record.  However, the resulting merged record's Initial Online Source field is empty. This is unexpected as the 'Merging Leads: Behind the Scenes' help article (community.marketo.com/MarketoArticle?id=kA050000000KyszCAC) states that, "When merging a lead with an empty field with another who has a value for that field, the merged lead will have a value in that field." Paradoxically, Marketo does clear set a standard field's value to empty when automatically merging an anonymous record with a field value and a known record that has no field value. My suggestion is that when Marketo authomatically merges an anonymous and a known lead record, any field with a value should be preserved if the other recrod's field is empty. ... View more

Having the source/reason attributes set to dynamic chat for the  updates made by dynamic chat will help us filter on the field values updated specifically by the dynamic chat in the SL/triggers. Currently the source in the field updates made by dynamicChat in activity shows Web Service API, it’d be great if we could say if the values were updated by the dynamicChat  specifically. Additionally, it'd also be great if dynamic chat is added as one of the input sources that we could check-mark to block updates in the field management section on the respective fields, if need be. There could be use-cases where we would wanna capture the data from dynamic chat for a new person but not update if there's already a non-empty value present on an existing person in the Marketo.   ... View more