Darshil_Shah1

Well, Marketo doesn't do any transitions between streams OOTB; you'd need to create trigger-based rules in the Transition Rules section of the stream you want to pull people into or manage the stream transition via the smart campaign using the Change Engagement Program Stream flow step. Also, people...

@Hayley, Before you go into the rabbit hole of determining whether this is due to a soft bounce retry, you should thoroughly check the "Used By" of the email asset(s). That's the first place I'd find any program or flow that sends emails out of my knowledge or radar. Also, when a soft bounce occurs,...

@kiruthika_s, Yes, you'd first need to request the Marketo support team to add a secondary dedupe key (BU ID or partition ID), and using the resultant composite key (which would be a unique key), you can update the exact person record you want to update amongst the duplicate (people with the same em...

Interesting, and yes, if you don't have any disconnected paths, e.g., a card just lying there without being connected to your main chat flow, then you'd see this error; however, if you don't have any cards disconnected from your main chat flow, then you shouldn't see this error! Also, did you check ...

@ayaspan, Do you by any chance have custom dedupe criteria (e.g., email address + other field/partition ID, etc.) enabled in your instance (especially for the list import as an input source)?

@kiruthika_s, the partitionName field isn't considered a co-lookup key in the POST request with the Email Address field. AFAICT, the Marketo REST API sees the entire lead database as one unit while making updates, not the virtual partitions created by creating the person partitions via Marketo > Adm...

Well, in past two days, the operator looks at the last 48 hours; if it is set as "in past 3 days," it would look at the last 72 hours, etc. Unlike the exact date operators (in between 2 dates), it doesn’t look at the last two calendar days from midnight to midnight based on the timezone specified in...

Well, yes I got your point now.If you want to restrict sending just a single alert, you’d need a webhook based solution, and probably a resource lead as well that would be updated with the channel name and flow through the send alert campaign. One easy way to get around this with a little different ...

You can use Remove from Campaign flow step for those people. Basically, if they are a member of smart list, then remove from “this campaign”.

Also, worth mentioning that clicks and opens could be from bots/email scanners, so you’d not want to consider them as coming from a human and change around a lot of stuff (take significant marketing decisions) based on those. You can filter out/mark activities that match the bot patterns by using Ma...