Andy_Varshneya1

"Predictive" hasn't become mainstream yet. Predictive scoring/content should continue to get traction into next year and see it cross the threshold from Early Adopters to Early Majority.Additionally, account based marketing should also get a lot more focus for marketing teams as they focus on strate...

What do you know, you learn something new everyday.Is it common that mail clients don't support these aliases? I read somewhere that a large portion of them do, including Google, sendmail, and Communigate, all support the plus sign.

Exactly. At this point, email testing and deliverability testing has become so commoditized it's really all up to you in terms of what UX and secondary feature sets you prefer and how much you're willing to pay for them.

I've been able to send myself 4-5 copies of the same email in the same batch by having a few copies of my email address in Marketo differentiated by the "+" mechanism (e.g. avarshneya+test1@, avarshneya+test2@, etc), so I would think that applies to this situation as well, where you're able to send ...

My understanding is that Marketo has read-only access to the Opportunity object in SFDC, so the inconsistencies are likely related to a stale sync for the person. What happens if you force a sync to SFDC for the person? Do those data points update?

I assume a running scheduled batch based on renewal date should handle this just fine unless the two contracts also have the same renewal date in which case they'll only get that 1 email.Simple solution (though maybe not ideal depending on your perspective): modify the two emails slightly by using a...

Alternatively, you can also set up conditions in the Send Alert step checking if the User Type is inactive or not, and if they are, send an alert to a queue or an alias.

I always file a support ticket for such situations. They get a bit more attention that way. They won't necessarily get resolved though, so temper your expectations.

I agree with Josh that local program level scoring might not be a good use case as it's not scalable and applies to only a small subset of your database.Do you think you might be over-engineering this? Would program statuses do the trick?Alternatively, could you set up an engagement program and use ...

Got a couple more for you - ​