Katja_Keesom

I think the Person Was Created does not really achieve the goal here, as there can of course be people who already existed in your database, but were added to your program in the past 30 days. However, you can filter on Program Status was changed from "Not in Program" to any other status in the past...

Hi @Darshil_Shah1 , the DB size will not change, as the audience will be picked the moment the smart campaign is run and will not be evaluated again after the wait step. Your comment about the random samples being disconnected from eachother is totally true though, so this flow will indeed not work....

Just a silly question: If you are looking for people who unsubscribed from your communications, why don't you simply search for people with Unsubscribed = true?

In addition to Jo's considerations, I would be very careful with the Not was Sent any email selection, as these activities are typically only stored for 90 days. So it is well possible these people were actually sent emails in the last year or so, but you simply don't see it any longer.

Not sure I understand you here. Having hidden fields in Marketo is not something you want to stimulate, as hiding a field removes it from use altogether, so this is used to remove obsolete fields from the UI. Unless of course you mean hidden fields on a form. This would also correllate with the utm ...

For program success statuses, it much depends on what constitutes success and how long ago your email was sent. If the activities on clicks etc are still there, you can run fixes. But this is typically an activity type that is only stored for 90 days.

I would try sending the email to yourself as a 'real' email. If there is something wrong that generally results in a soft bounce which will be recorded on your lead record with more information about why it failed.

That would be a url that is generated on the Azure side, so there is no generic one.

If you have multiple partitions, but not multiple workspaces then indeed the automatic assignment will not work and you would need to include the partition as a hidden field on the form. That would mean though that you need a separate form for each partition.