TOMMY LAURITZEN AITC

We just upgraded to Service Pack 1 on premise, and today discovered that all activities with regards to their direction is now treated as incoming/recieved.
We tested it online, and the same happens there.

Segments can take up to 6 hours to update, which in turn means more than a 6 hours wait time for actions to occur in a Customer journey based on this segment. It is totally understandable that the heaviest of segments require some time to update, where the segments are building on several other segments, which in turn builds queries interaction data etc. But this limits the scenarios where Segments and Customer Journeys will cover business needs. Suggestion: Add support for creation of light segments, or transactional triggers, where updates allow for immediate triggering of actions and/or content in the Customer journey.

It would great to be able to map in custom data to emails and other activities in the Customer Journey. Allow for Customer journey to be triggered on contact related entity, where you can bring the data from this related entity into the customer journey and use this in your communication. This would let you trigger an email send based off of a customer purchase (order) and then bring order information into the email. Ideally this would be supported both for Entities and triggers in CRM, but also be supported through API