Alex_Stanton1

The only other solution I can think of would be to use a custom field, but truthfully, I would keep the two campaigns separate in SFDC, like Josh suggested.

Hi Tom, I think it is a rather useful status - we often use "queued" as the first status, but you could use "uploaded" or any other word to indicate that they are part of the program but have not started their journey yet .

You are using Rich text tokens and this is most likely what is creating the issue. Try using plain text tokens - that should solve the issue.

One way to do it is to block certain records from coming into Marketo applying the same criteria that you apply in your custom view in SFDC. You will need your SFDC Admin's help on this.What syncs depends on what the Marketo Sync User can see in SFDC. You need to adjust the permissions of the Market...

Did you try to change the name of the custom object / build a new one and give it a different name?

I am sure other members of the community can come up with other ways but the first thing that comes to mind is to set up a custom field that adds a time stamp when the trigger fires and then use that time stamp to route the lead to (A) a campaign to send the email if the time stamp is between 9-5 or...

Hi Brett, I have seen that in the past - the sync had to be on. Try to contact support and see if they have a workaround now.

Exactly - or like Stijn suggests, one main campaign that requests different campaigns with different wait steps.

Unfortunately, that is not possible. If you have move than one choice that would fall under the same amount of days, you can group them.Ex:Choice 1 = 6 daysChoice 2 = 6 daysChoice 3 = 8 daysChoice 4 = 8 daysChoice 5 = 6 daysYou could group it like this:6 daysChoice 1Choice 2Choice 58 daysChoice 3Cho...