1. In Real-time Journeys email personalization, it should be possible allow more than one condition hop when filtering personalization data in the Email builder. For example, we create an N:N relationship between Contact and Account with the table RelatedContact. It is possible to get personalization path of Contact → RelatedContact → Account: Account name. However, it is only possible to filter the results using fields of RelatedContact table. It is not possible to filter the results using Account fields from the Account lookup of RelatedContact table. Therefore we cannot correctly filter for the Account name, resulting in incorrect personalization fields being sent to the Contact.

2. It should be possible to allow sending to Account entity, using any email address stored on the Account record. Only allowing sending to Contact records can severely disadvantage organisations sending to end users who interact with our service via an entity (i.e., small business or sole trader).

3. In addition, the data set created by Segments should be preserved to be used with Email personalized fields. Or, please allow the importation of FetchXML or SQL to create the data set used for Journey / Emails. This would enable accurate personalisation and sending to data sets such as:

Account Name | Name | Email address

Example Business | John Smith | john@example.com