Alex_Stanton1

Hi Joanna,I have not had to solve this issue before, but I would look into using segmentation and snippets for this purpose - here is an article that explains how to go about it: Make Your Unsubscribe Message Dynamic for Languages - Marketo Docs - Product Docs

Nested smart lists put a lot of strain on the system. I have seem them fail and break a campaign so if you can find another way to achieve the same result, I strongly encourage you to do it. If you post more detail about your smart lists, maybe we can help you come up with another solution.

Dane, just ensure you are not blocking fields that will prevent other things in Marketo from working. If you have a lead lifecycle program, for instance, and stages which react to opportunity updates, you will want to ensure those activities are still recorded.

If you set up SFDC campaigns for the Marketo programs, you can also look at the Campaigns with Influenced Opportunities report in SFDC.

It is hard to say without seeing the program, but Josh does have a point. I have set up a number of nurtures with an initial triggered campaign that sent out the first email and then routed the lead to the engagement program. I normally put a wait step before adding to the engagement program to avoi...

It might take a bit of work, but you can run separate email performance reports by month (just adjust the date in the set up section).

A static list is probably your best bet. If you want to experiment with something else, you could try with SFDC campaigns membership, maybe a separate one for each one of your different type of customer or set up a custom field for that purpose.

Hi Mike,You can also have a look at this post from a few days back for an alternate solution to lead source using UTM paramenters: Solution to using UTM parameters & cookies to capture lead source information

Also, make sure that all triggered campaigns have actually been deactivated and assets have been unapproved.

As you are investigating, also look at the activity log of the leads that did not sync over - could it be that they are missing a field required in SFDC (such as company name). As a temporary fix, you could sync as part of a flow action. That might even provide more intel about what is going wrong.