Iryna_Zhuravel4

it will pre-fill an existing value from the lead record, it can be very painful actually, as you might be losing a lot of data this way.

Deliverability management is a huge topic and can be very tricky as there are many different factors at play, just to name a few:- the health of your database - follow Josh's advice above and make sure you don't email invalid/inactive leads- the content of the actual email - spam filters will automa...

Yes, they can add attachments using this feature and they will be delivered

I ran into similar issues with our target audience (engineers), they don't like tracked links, and we had a few people making a huge deal out of forms with pre-fill enabled ("how do you know it's me? why is my data displayed publicly? why are you storing my information?")There isn't really a workaro...

There is no way to do it on the lead level, but you can do it on the level of the smart campaign or email programApply Communication Limits to Smart Campaign - Marketo Docs - Product DocsEnable/Disable Communication Limits in an Email Program - Marketo Docs - Product DocsCreate a separate test smart...

Sanford Whiteman that's a really great idea, I would love to, I am on a biz trip to China at the moment, will be back to the US on November 5th, let's jump on a call sometime after that.

RCE allows building really nice heat grids for various email marketing metrics (see open rate heat grid example below), BUT all the heat grids are in the CST time zone, which makes it incredibly annoying to run reports on other regions. This is one of my biggest Marketo pet peeves, couldn't help but...

The best practice is to keep your CRM database as the master source of your data, therefore it is usually advisable to merge records in the CRM.

We also use Ringlead, and I ran into this issue a lot. You cannot restate mrkt created date, but you can update acquisition date. I use acquisition date in most of my reports and quite often run batch updates like this:SFDC will keep the created date of the master record, and in our case, it is usua...

We localize in 8 different languages, use segmentation and dynamic content extensively, but I am currently rebuilding the whole thing. I would strongly recommend using language preference field in conjunction with country/region and not to assume that people want to receive content in certain langua...