Wyatt_Bales4

ExactTarget doesn't natively support the related relationship but you can query SFDC through its API and build a data extension of that relationship. We ended up still going with Marketo with a custom object being fed by a SFDC query. It works quite well but has some tech debt (e.g. SOQL, scheduled ...

Although frustrating there's isn't native functionality, a SFDC admin with SOQL skills combined with an API developer can build a Marketo custom object for you and push data in. We push global related restaurant relationships into a Marketo custom object every 3min. This combined with Email Scriptin...

Sorry, ExactTarget. Leveraging Data Extensions like Marketo Custom Objects, we're able to roll-up 1:N relationships with more flexibility and much less code.

We actually had to pivot to ET because of this functionality. The lack of Velocity depth we have on our team combined with the inability to see Related Account info means we can't qualify or report on any franchise Account model.

Facebook campaign data is available via the API, just not in the GUI. I agree it would be helpful to be able to store it as a token to tie to the record. "id": 131, "name": "Fill Out Facebook Lead Ads Form", "description": "User fills out and submits a Lead Ads form on a Facebook page", ...

We ended up creating a Marketo custom object which is updated via the API whenever a new 1:N relationship is added in Salesforce. It's incredibly flexible and useful but becomes an issue if you rely on Velocity Script to populate emails via (because of duplicate records).

From experience, Marketo's ability to trigger off-of Account updates isn't 100% reliable. However, batch campaigns are more accurate when qualifying records based on Account-level fields. Currently we're facing issues with Opp constraints preventing triggers from working but yet batch campaigns work...

This is a big use case for Uber. In a restaurant Franchise model, Contact1 could own 5 different locations. Thus we "related" Contact1 across 4 other Accounts. We have a Contact Account Relationship custom object which allows us to bring back some 1:many Account 2 through 5 fields but isn't feasible...

Absolutely agree. We put the subject lines within tokens or the description to help save time but the preview would dramatically speed up the search process.