Dan_Stevens_

Then I'll have to circle back with our legal team to find out if "email tracking" can be bundled with "opting-in to receive emails". Without including yet another type of "opt-out" checkbox (or "opt-in" checkbox), I just think it will be challenging to manage this at scale.

Hi Greg - I realize it's easy to add. The difficult part is integrating/managing this with other vendor's solutions (like OneTrust). I'll find out later this week if the OneTrust solution covers email tracking.

I should have stated this was more of an assumption until we have our next meeting with OneTrust to confirm. Based on your discussions with OneTrust, Sandy, by opting out of Marketo tracking cookies, does it also disable Marketo email tracking (at the device level, of course)?

Aaron - when using nested/child programs in an EP, a person can only qualify for this once. Even when not qualified - and just "tested" for qualification during the smart list - they won't be able to qualify for that same email/program in the future. See this idea for more information:

One other thing that's surfaced in our discussions with our legal teams - specifically consent around cookie tracking - the tracking that is contained within emails is not a "cookie". So tools like OneTrust and TrustArc don't impact this tracking. One more challenge to figure out. Would be intere...

Mariah - when importing a list directly into Marketo, Marketo will dedupe against any existing records where email address is the same (and no duplicates will be created). There is no way to "override" this. Now if you're referring to updating those records with new/updated data - then yes, the ex...

Yes it does (you also need to define which stream to add them to).

The "easiest" way to do this is to create a custom field in your database to store the filenames of each client photo. You will also upload these photos to Design Studio (preferrable they all are resized/formatted the same). You'll then insert the image as a token in your email as "

It's also worth mentioning that lead tokens (email addresses) will only work in trigger campaigns when used in a "send alert" flow step (in the "to other emails" field):Send Alert - Marketo Docs - Product Documentation For batch campaigns, it needs to be hard-coded, without using a token

Absolutely not. You do the same thing with embedded forms on non-Marketo LPs. But instead of referencing the LP, you reference the "referrer" (as a constraint) - which indicates the page that the form was submitted on. We do this on our website (over 7,000 pages).