Mark_Price

Happy to hear it's solved and was a quick fix!

It would appear at some point, someone clicked 'Edit Code' on the 'Email' which then dis-associates it from the 'Template' code which is used for the layout / modules function. I would try creating a fresh email that uses the template to see if the Modules work. If the Modules do work in the new E...

Kind of hard to troubleshoot with the details provided.- If you click on the email within the Marketo UI, does it say it's connected to a template still?- Other than that, maybe scan the code and ensure: mktoName, mktoModule, are set / unique and look for missing quotes / coding errors.

What happens if you make a new email from the template? If the new email works, than it could be that new mktoModules were added to the template which can cause this error on emails that were approved with the old layout..

I would try:- removing the formal notation aside from output- double check that the custom object field is selected in the field tree where you input the script

You mentioned the url contained 'https://'. I would strip that and insert the URL like so and see what happens: Register HereMaybe check email link performance report and see if there are any links that are: 'malformed link' or your variable.

Hi Michael, As others have said there are a few ways to get this done, most using custom code. To allow the registration on-page you would need code.If you are ok confirming / denying registration via email, you can do this with just a Marketo campaign and 2 emails. Setup: - Add your 'allowed' segm...

Results of running the test script: API-based send results: Flow step-based resuls: The campaignRunId being recording in the activity log is the same that is being used at run-time

Ok, will do! Thanks for the help. I spot checked the campaigns that trigger on a data value change from the API and they also re-distribute the campaignRunId. Sort of surprised this isn't giving anyone else problems but to even notice you would need to have:1. A recurring campaign triggered via...

Ran the tests on 2 records, results are below. Results are not what I was expecting- the Flow Step Request Campaign has a similar system behavior of re-issuing the campaignRunId after it's generated. API-based Request Campaign Call #1: This is the first person in the campaign, so it created a campa...