Dan_Stevens_

Yes, please tell us! Even when adopting email best practices (explicit opt-in, no purchased lists, highly targeted/personalized/relevant emails, proper setup of authentication (SPF/DKIM/DMARC/Branded Envelope), it still can be very challenging to make it into the user's inbox - especially in B2B. ...

Elizabeth - your explanation is spot-on. The reports are the same - it's just that when you create a report within a program (in MA), the report defaults to just that program. The reports in analytics can provide that same insight, it just takes a couple extra steps to define which program, email,...

Based on experience of others, like myself, they have to wait for the next cast to qualify for content. Here's another active thread where this is being discussed:

Hi Jep Castelein - appreciate your reply here. We learned a while back that the 302 message was not an actual error. But what we found was that there were certain leads that didn't get duplicated - even though they qualified for the trigger campaign that kicks off the process. Who knows - maybe i...

Hi Mike - unless this issue has resurfaced, Marketo deployed a patch on 3/27/17 which resolved this for us.

By chance, are the tokens defined outside the program (e.g., at the campaign folder level - where they're inherited)?

Wow, thanks Courtney - that was easy! Brings back memories of my ASP/vbscript days. I definitely need to do more with velocity in Marketo.

are you "cloning" or "importing" a program? When we clone across workspaces (e.g., from our CoE workspace - where all program templates reside - to a country workspace), we don't experience issues like this.

As a velocity guru, care to share what the code might look like? Basically take {{lead.Lead Owner Email Address}} (which all contain @avanade.com" as the email domain) and transform the domain to @marketing.avanade.com.

Hi Courtney - yeah, that's what our security team mentioned as well. For example, if we have a campaign where we want to include a "first.last@marketing.avanade.com", the Exchange team can add this additional email/sub-domain to the user's record (or like you said, even a rule for all users)The iss...