Nicholas_Manojl

Thanks John.I assume this is a cookie technical limitation.. in which case a hidden field of {{system.dateTime}} probably won't work either? Could I write the {{system.dateTime}} as a 'Change Data Type' step in a 'Fills out form' flow?

Hi John - it is definitely a trigger campaign.The only thing I can think of is that it started life as a batch campaign? I'll keep monitoring it.

How about..1st campaign is: Send Email First Subject,Wait 4 days,Send Email Second Subject2nd campaign is:SL: Email is OpenedFlow: Remove from flow 1st campaign.

Never mind!"Note: To access the list id through the Marketo UI, navigate to the list. The list id will be in the URL of the static list, app-****.marketo.com/#ST1001A1. In this example, 1001 is the ID for the list."

You add the script as a token (there is an email script option).Then in your email you can reference it my just putting {{my.scriptName}}.

Remove the trigger "fills out form" and replace it with "filled out form"?Or make it a trigger "fills out form" and a "data value changed" regular constraint.

Well, ideas I liked in the previous instance where they were comingled with discussions.In your second screenshot you point to Community: Feedback & Help. Is that different to "Discussions" and if so, why?

I guess you could do it quick and dirty, if you were referencing something sensitive. After the email is clicked and the page is loaded you could wipe the data being displayed. Kind of like a self-destruct function. Clicks link in email & visits web page -> wait 1 minute -> change data value = null

Hi Scott - thanks for that and excuse my crankiness. I think mostly the things that don't work for me are:- partitions between the different areas (ideas don't sit along side product discussion)- confusion about where to post questions to get community help

Ahh, good one. But would that have to be a batch run?