Tokens for Opportunity fields

[Eva_Maloney]

It would be great if you could use tokens for opportunity level fields in automated emails. For example, we have an automated email that goes out once their order has been shipped with their subscription start date, username, products ordered, and other opportunity level data. We currently have to do this via Salesforce but it would be great to be able to pull it into Marketo. Also, for opportunity nurture we need to be able to segment based of the product modules associated with that opportunity.

Is this on the product road map at all?

Thanks!

[Anonymous]

There are substantial needs for this type of functionality.  It's true, in that the way that Marketo is currently designed there isn't a simple solution. However, there are alot of use cases that can be made that allowing for a token to be generated in the body of an email from a contact that has a 1:many relationship with an Opp (OR a Custom Object) would be very useful to marketers.

I think the reason that it probably isn't allowed is because there's a difference between how a query is done (smartlist populated with just the lead/contact ID's) and the logic used to populate the token (email draft pointed to a particular list/smartlist). 

But if there was a special type of list that could be created (think cached list), that essentially created a temporary table that has a row for each relationship between a contact and it's many opportunity/custom objects - let's call this an "Opportunity List", then you could point a special Email type - let's call this "Opportunity Email" - to be populated with tokens that stem from this special list type. It's true that if a contact appeared twice in this special type of list, that would be a risk, so there might be some verbage alerting a user if this were the case, but in most cases we would want to send out two emails to this contact (because there'd be something important we'd need to communicate). So you may need to make an exception to how marketo handles sending to 1 email address (stagger by 1 hour, etc.). 

Again, it makes better sense to build out this functionality alongside custom objects, because there'd be a million ways that Marketo users could utilize this type of functionality, but it gets us close to being able to send intelligent emails instead of just emails that are  "personalized on demographic fields". 

[Anonymous]

You can use email scripting to do many of things listed above. Please see here for more details. Thanks!