Victor_Herrero

Sanford, thank you very much for your lessons I feel like these discussions are the ones that generate a deeper understanding of the tool. I appreciate it.

So you are saying that each smart list is basically a query result that gets updated every time the trigger is triggered, and until all query results have been delivered (i.e. first name is changed, so all smart lists and processes that are using that as a trigger are re-queried and the result retur...

Hi Sanford, I'm very interested in two of the answers: Are we able to append fields to existing forms using the update endpointYou add with the /fields.json endpoint.Say we have a case of "Episode II: The GDPR Strikes Back" and we need to modify ALL forms with an additional checkbox... It's possible...

Ok, so after every update / creation, first smart list qualification is determined / fixed and then all other search processes take place. When it comes to smart list memberships, I find it fascinating that there is no actual field in Marketo's own database (or each of our instances) where for each ...

I see what you mean. As long as the source form includes the filters that you are using on the filter smart list, the trigger will fire correctly, because the necessary information will exist on the record on creation. You seem to be 100% sure about the speed of dynamic Marketo lists, but are all re...

Thanks for your suggestion. Yes, working within the flow steps seems like a 100% reliable method. I will definitely bear that in mind in general. I am inclined to agree with Sanford though, wait steps are clunky and if you add enough in different places, your whole system will become vulnerable and ...

Here is another suggestion... Never use "person created" as a trigger in your instance's smart campaigns. Always use instead "added to list: "Person created" ". Create the list "Person created" via a smart campaign with the trigger "Person is created" (only this once, throughout your whole instance)...

Ok, so my takeaway from your answer is that its unreliable, same as Ronan, you are saying that if the data is already there when the trigger happens - it's relaible.Otherwise, you can't be sure if it's going to work a 100% of the time.

Hi Ronen, Thanks for you answer!So you suggest I break that into two campaigns that happen in sequence. But doing that implicates duplicating the numbers of campaigns... perhaps in terms of maintainability not the best idea