Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Yup, that seems to be the general consensus on the cost vs benefit analysis of Request a Campaign.My guess is that the concern comes from those wanting to ensure that those who follow their advice don't go overboard with it and use it excessively.Thanks everyone for your input.
Yup, I completely agree on the use case, my curiosity is more regarding around the performance compared to going the Add to List route or consolidating flows route.
Thanks for sharing that Grégoire Michel! I don't understand why it's impacted by the first flow step vs second or third or etc. Is it because one a flow has started executing, every step will be executed upon regardless of resource constraints, therefore resources will be allocated to flows based o...
Over the years, I've heard a lot of information in favor of or totally against the use of the "Request Campaign" flow step. Some have said that it is the lowest priority and thus can be skipped altogether during times of heavy workload for your instance, and that in general it is also very slow. Oth...
Doesn't directly answer your question, but if you're looking to globally blacklist certain users, it probably makes sense to use a segmentation, such as a Email Status Segmentation or Lifecycle Status Segmentation.
3-5 minutes for SFDC to Marketo, and 40-45 mins for a database wide sync.
That depends on the information you collect in the form. Since Marketo is not inherently built as an ecommerce platform, the data you collect will not be secure and will be accessible by anyone with access to your instance.It sounds to me like you would be better off using a platform like Stripe, Sh...
Could you please mark my reply as Correct so that we can mark this question as answered?
Thank you!I was trying to work through the constraints as well, but wasn't able to get anything to show up in the drop down list for Reason or Source, so I didn't know if it was expecting a string or ID or something else altogether.