Matt_Stone2

You should be able to use the send sample to test the tracking code, unless something has changed since I originally posted this. What is the result you're getting exactly?

If you're using the form javascript snippets, you won't be able to use prefill. It's a security restriction for transferring data off Marketo.

There's not a good way to avoid this, unfortunately. Your best bet is to have a deduping tool or process on the SFDC side.

You could use some of the options that Jamie noted, and you could also add a Data Value Changes trigger with a source for salesforce.com.Your smart campaign can have multiple triggers acting as OR operations, so any of them will cause the email to be triggered.

I believe you can abort the email program, but I don't know if it will pick back up where it left off, or if it will allow you to make changes mid-run. My guess is it won't and you'll have to rebuild the program and filter out anyone who was sent the first one.Out of curiosity, what is your use case...

Are you looking to do this in SFDC or in Marketo? What behaviors constitute a user trying to prospect/work/modify at your org? What exactly do you want to have happen when these behaviors are met?

One option is to change your smart list setup to use a "Was delivered email" trigger for the appropriate email. Then in the flow, start out with a 4 day wait step. Then have a Send Email step, but put a choice on it for "Not Opened Email" -- this will flow everyone through it once they get that emai...

Are you wanting to pull the list ID via the API? Or pull it via Marketo to use in code somewhere?If it's the latter, I think you can grab the ID by navigating to the list, then looking at the URL. You'll get something like: #ST12345A1 -- the ID would be the numbers after #ST and before A1. I'm not 1...

Hi Hiram,For your first question -- yes, replace the entire thing. For your second question -- did you use any dynamic content in the email? If you did, you will be unable to use the tracking code at the same time. It's an unfortunate limitation of Marketo.