Kenny_Elkington

You'll want to use two separate filters here. First using In Future After 120 days, and second, In Future 121 Days. That will capture whomever has a dates 120 days from now.

Thanks for reporting this. I'm having engineering take a look right now.

For this specific case you should just use the $TriggerObject. When you set the campaign up with Opportunity Is Updated as the Trigger, then the updated opportunity will be provided to the script in the $TriggerObject variable.

Gotcha. Makes sense now.

Is there a reason that you can't use Request Campaign for this case?

If you create your "new Comments" field on the lead, then you can just pass the content as a token into the description in your Create Task flow step, {{lead.New Comments}}. This will overwrite the field each time, but will pass the new value to the task every time that it's uploaded.

You're probably better off just using the forms API to add your values as hidden fields on submission instead of working with duplicate forms: Forms 2.0 » Marketo Developers​ You can use addHiddenFields() during the onSubmit() event to input your data into the fields.

The last release was February fifth and we release quarterly. The next release will be in Q2, likely April or May.

Marketo won't perform any matching when pushing a lead to SFDC, just on the SFDC ID if it already has one. Do you have any deduplication rules, or dupecatcher enabled in SFDC? That's not an error message I've seen before so I suspect it's from non-standard functionality.

Yep, right here: http://developers.marketo.com/blog/external-page-prefill/