26

We are an association so much of what we want to communicate is related to a parent account, not the contact specifically. As we can only go two hops on the dynamic content it is severely restricting and renders much of the data we try and pull over via Insights Sync useless. Would be great if Account was a starting context like Contact/ContentSettings or if we could do multiple relationships. I had hoped you would support nested scope so tried to use nested for-each loops but the editor threw an error: {{#each Entity.RelationshipName }} {{#each this.SecondRelationshipName }} ... {{this.RelatedField1}} ... {{this.RelatedField2}} ... {{/each}} {{/each}}

Category: Email Marketing
STATUS DETAILS
Needs Votes

Comments

A

Have the same issue. 2 Hops is not sufficiant.
We need to be able to reach information from Contact-->leads-->Journey. or Lead -> Contact -> Journey.

Category: Email Marketing

A

Agree as well. Need more than two hops. Additionally, ability to retrieve data using REST API could help also to place data on body of email.

Category: Email Marketing

A

Agree - we need more than 2 hops. Accessing Lookup name values from the Account record aren't even possible at this point :(

Category: Email Marketing