Grégoire_Miche2

HI Tom,Normally, tokens in text email works OK.You can use the preview by lead or the end sample features to make sure it is.-Greg

Voted, but IMHO, should be merged and dealt with together with this one : -Greg

Hi Kelly,If there is no more than 1 print piece per lead, you could just use the lead ID, which is unique. You can reference it in emails with the {{lead.ID}} token.if you have more than one, it will become complex, you will need a custom object.-Greg

Hi Christine,Yes, this does make a lot of sense. We call it the "global exclusion list" and we use it to always exclude leads from smart campaign or program target. No need to add them to your targets, since they will not be sent the emails anyway. They would just ruin your target to success rates �...

Hi JD, Indeed, it will be caught as invalid email.-Greg

Hi Nathalie,it will include the 2 limits.-Greg

Hi Runjini,If the secondary contact is a contact in SFDC, it will sync on it's own in Marketo. You can check this searching the spouse email address in Marketo.But you will not have the link between the 2 contacts in Marketo.-Greg

Hi ChristineYou can capture the value "website" in any Marketo field. You can create a field "utm source" or use the default field "lead source", if you want.To capture the data, you need to add this field to your forms, as hidden a field, then set the field value to be a URL parameter, and set the ...

Hi Amanda,On SFDC, yes it will. Will it work also on emails sent from outlook? I have never tried, to will have to try and let us know -Greg

Hi Patrick,No, Velocity scripts can only run from within an email, nowhere else.You could solve the issue in SFDC, with an account field and a workflow on the opportunity. The workflow will copy the opportunity owner data to the account each time the opportunity is created and or updated. This accou...