Smart Campaign Settings

[Anonymous]

It would be great to have more options in the smart campaigns to reject a smart campaign or email send, such as if segments. For example, if smart campaign audience includes X segment abort campaign. We are considering implementing lead spaces and partitions and here seems to be a feeling these are difficult to manage and implement. This could be a workaround alternative to implementing lead spaces and partitions.

[Abby_Ryan]

What type of campaign would this be for? Can you simply exclude the segment in the "choice" statements of the flow steps and remove them there?

[Justin_Cooperm2]

I agree with Abby. Can you see if using choices in your flow steps will work for you? Let me know if you're looking for something else...

[Anonymous]

Hi Abby, yes that could and should be done, but the goal would be at the admin level to have another measure to prevent people from accidentally emailing parts of the database they shouldn't be emailing. Just trying to remove the human error as much as possible.

[Justin_Cooperm2]

Tim, what is the use case for this? It will help me evaluate this as a feature.

If you want a certain group of people in the database to never get emailed, why not mark them as a "marketing suspended"?

[Anonymous]

Hi Justin

So really the use case is to be able to present someone in the European office from emailing any of the contacts in the US by accident. This seems to be what lead spaces and partitions are for, but there is also a complicated set-up with these. So in the admin area it would be good to have the functionality that person X based in Europe could not send to anyone in the US segment. If the UK person accidentally set-up the smart list to email people in the US segment the campaign would not activate. Hopefully, that is a little clearer?

Thanks

Tim

[Justin_Cooperm2]

Yes, that makes more sense. I will forward this to our PM working on some related features. It may be a bit complicated to do what you describe but will make sure it's looked at.

[Anonymous]

Thanks Justin

[Anonymous]

Hi Justin

The setting could definitely be done in the flow steps, but the goal would be to remove the human error by setting this as the admin level. Could be in the user or roles section where you can change the segmentations they are allowed to access.

Thanks

Tim