Katja_Keesom

A couple of things come to mind:For the seamless user experience it is indeed a good idea to integrate into your website.Embedded forms as a standard do not offer prefill functionality though, so if you want your forms to prefill you need a Marketo LP or some good coding experience to implement a wo...

The use case for global forms is a strong one for sure and it just got stronger! 😉With all that's being said in the thread though, there is a use case for perhaps having a flag to "not auto-deactivate". My use cases often are around operational processes where niche scenarios need to be catered for...

I am not sure what your fifth filter is about, but if it is something campaign-specific I would not include it in a segmentation. As mentioned, the segmentation is something you set up for generic use. You can then combine the segmentation selection with campaign specific criteria in your campaign's...

You are absolutely right. This blog was just written about capturing utm tags by @Andy_Caron3 , capturing this and many other aspects: https://nation.marketo.com/t5/champion-program-blogs/best-practices-for-utm-processing-from-website-gt-marketo-gt-crm/bc-p/319870#M2455

You can send the alert to multiple people, by adding multiple email addresses in the To Other Emails field. If I remember correctly you simply enter them separated by a comma. It will not cc them, they will be in the to field, but that's the way I would do it.

That was indeed the general gist of how I'd set up the manual work around. Probably indeed finish your flow with if member of smart list Possible Duplicates > Request Campaign and then in the second smart campaign use the trigger Campaign is Requested combined with email was not sent. Haven't tried ...

Hi there!That is indeed a tough scenario. The default approach for Marketo is actually your scenario 2, where Marketo will only send the email once. In order to make your scenario 1 work, I think will only ever work if you do it trigger based or with a manual work around to identify records that wer...

The segmentation would be generic, for use in all programs, so member of program should never be in there.I would build the segmentation along the lines of:Email address is empto or Email Invalid is true (these records are useless)Unsubscribed (you are not allowed to email them)Terms & Conditions is...

A segmentation is pretty much a prioritized series of smart lists. So first smart list (segment 1) is checked, if someone meets those criteria they cannot be in any of the next ones. People who are not in 1, are evaluated in 2. If they meet those criteria they are in segment 2, etc. That way, each p...

IMO best practice would be to set up a segmentation defining whether a person can be emailed or not, taking into account the people you describe as your first segment, but also taking into account unsubscribes, invalid emails and opt-in status to come to an unambiguous definition of who can be email...