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...

I had the same hunch so I broke it out like so to test:Focused Account: $focusedObject.accountID
{Focused Account}: ${focusedObject.accountID}
Focused Account URL: www.whatisthis.com/$focusedObject.accountID/stuff
{Focused Account URL}: www.whatisthis.com/${focusedObject.accountID}/stuff
{AccountCaseSaf...

To clarify, the url sometimes loads correctly. When I run a separate test batch campaign, the token works. When the trigger fires multiple times within an hour, sometimes it's populated with the ID, other times is $focusedObject.accountID.

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.

Thanks, Sanford Whiteman​. I was able to get it to work great. You can ignore my response on your forum. If the user has cookies disabled on that site, responses don't play nice because you have to login. #if( $context.contains("TriggerObject") )#set( $focusedObject = $TriggerObject )$focusedObject....

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.